SQLServerAgent Error 1060

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

RD - 21 Oct 2005 22:22 GMT

Have a Windows Server 2003 Standard system (Build 3790 SP1) with SQL Server
2000 Standard SP4 (8.00.2039) installed. Two SQL Server 2000 SP4 instances
are installed on this node in a single OS instance. Both instances of SQL
Server start and run fine, but the SQL Server Agent on one instance fails to
start with an error 1060. Both instances are running on non-standard TCP/IP
ports, both instances are running the instance and the agent under user
accounts with all necessary filesystem and registry ACLs. The instance that
has the 1060 error on SQLServerAgent was the first installed instance, and
its TCP/IP port is set to Hide Server; the second installed instance does not
have its TCP/IP port set to Hide Server. Have done file compares on the
sqlagent.dll and sqlagent.exe files in both installation \binn directories,
and no differences are found. Have run MDAC CompChecker and no errors are
found. sqlagent -i {instance} -c -v returns the following (sanitized for
node/instance data):

2005-10-21 15:02:14 - ! [298] SQLServer Error: 17, SQL Server does not exist
or access denied. [SQLSTATE 08001]
2005-10-21 15:02:14 - ! [298] SQLServer Error: 53, ConnectionOpen
(Connect()). [SQLSTATE 01000]
2005-10-21 15:02:14 - ! [000] Unable to connect to server
'{node}\{instance}'; SQLServerAgent cannot start
2005-10-21 15:02:14 - ? [098] SQLServerAgent terminated (normally)

Short of reinstalling SQL Server for the first installed instance, any ideas?

Reply to this Message

Sue Hoegemeier - 28 Oct 2005 15:41 GMT

And what happens if you set it to start up under Local
System? If that's works, then it is the permissions, rights
of the account you are using to run Agent. Did you remember
to add the account as a login in SQL Server?

-Sue

>Have a Windows Server 2003 Standard system (Build 3790 SP1) with SQL Server
>2000 Standard SP4 (8.00.2039) installed. Two SQL Server 2000 SP4 instances
[quoted text clipped - 20 lines]
>
>Short of reinstalling SQL Server for the first installed instance, any ideas?

Reply to this Message

RD - 28 Oct 2005 16:55 GMT

Thanks for your reply . The 1060 error also occurs with Local System account
for SQLServerAgent. The other account already had System Administrator
privileges with public and dbo for all databases.

> And what happens if you set it to start up under Local
> System? If that's works, then it is the permissions, rights
[quoted text clipped - 27 lines]
> >
> >Short of reinstalling SQL Server for the first installed instance, any ideas?

Reply to this Message

Sue Hoegemeier - 28 Oct 2005 19:36 GMT

As long as the SQL Server service is started, going in using
Enterprise Manager. Go to Agent, properties. On the General
tab, enter in the service account name and password - the
same one used by the SQL Server service.
Make sure this account is a sysadmin in SQL Server, remove
any mail profiles for Agent and try restarting the service.

-Sue

>Thanks for your reply . The 1060 error also occurs with Local System account
>for SQLServerAgent. The other account already had System Administrator
[quoted text clipped - 31 lines]
>> >
>> >Short of reinstalling SQL Server for the first installed instance, any ideas?

Reply to this Message