Friday, February 10, 2012

Can't get SQL 2000 agent to run

Need urgent help. The sql 2000 agent service never runs. Tried to run under
a
domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
the sqlagent with -c -v switches from command line and got foll. 2 errors:
[298] sql server error 170, line 47: incorrect syntax near 'collate'.
[sqlstate 42000] (connisloginsysadmin)
[000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
but '(Unknown)' is not a member of the SysAdmin role
Tried the microsoft kb solns and still not running. Need this resolved
urgently. Pls help. Thks. We use sql 2000, sp4.Hi
How about using Service Control Manager.
EXEC master..xp_servicecontrol 'QUERYSTATE', 'SQLSERVERAGENT'
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:588DF7E4-D96A-4BAD-A1A5-44636138EE54@.microsoft.com...
> Need urgent help. The sql 2000 agent service never runs. Tried to run
> under a
> domain admin acct which belongs to SysAdmins role and still doesn't run.
> Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi
I don't see collate in any of the statements issued when SQL Agent is
stopped or started. You may want to profile the agent starting (including
errors and exception events) to see what is being processed.
Is there any other messages in the SQL Server logs?
Have you tried running this as the system account?
John
John
"duchov" wrote:

> Need urgent help. The sql 2000 agent service never runs. Tried to run unde
r a
> domain admin acct which belongs to SysAdmins role and still doesn't run. R
an
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
>|||Hi John/Uri
setting the agent acct from either EM or service ctrl mngr has same result.
Only other errors in the sql logs are:
1) Operating system error = 31(A device attached to the system is not
functioning.).
This error is in multiple logs though not the current log. Any ideas on this
?
2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
will see that 15457 error
popup if you pull up your SQL Server properties.)
3) Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement
to install..
Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
server properties
Initially agent was under local sys acct n it never ran which is y tried a
domain admin acct but still no success
How do I profile the agent startup/shutdown? I ran a trace via sql profiler
(included errors/exceptions) and manually tried to start agent. the trace
showed 2 records under an application name of sqlAgent - initial boot probe
with no info really. is this what u meant?
Reason this is important is b/c I scheduled some nightly sql backups to disk
n they never run b/c the agent service never starts. Hope u can help.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
>|||Hi
An Operating System Errors seems like the problem is external to SQL server,
is there anything in the System Event logs?
John
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:885311AD-1FAC-4745-9430-D1F1A573796E@.microsoft.com...[vbcol=seagreen]
> Hi John/Uri
> setting the agent acct from either EM or service ctrl mngr has same
> result.
> Only other errors in the sql logs are:
> 1) Operating system error = 31(A device attached to the system is not
> functioning.).
> This error is in multiple logs though not the current log. Any ideas on
> this?
> 2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
> will see that 15457 error
> popup if you pull up your SQL Server properties.)
> 3) Configuration option 'show advanced options' changed from 1 to 1. Run
> the
> RECONFIGURE statement
> to install..
> Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
> server properties
> Initially agent was under local sys acct n it never ran which is y tried a
> domain admin acct but still no success
> How do I profile the agent startup/shutdown? I ran a trace via sql
> profiler
> (included errors/exceptions) and manually tried to start agent. the trace
> showed 2 records under an application name of sqlAgent - initial boot
> probe
> with no info really. is this what u meant?
> Reason this is important is b/c I scheduled some nightly sql backups to
> disk
> n they never run b/c the agent service never starts. Hope u can help.
> "John Bell" wrote:
>

No comments:

Post a Comment