asked on

sql server 2005 error 65535 when connecting with sql agent

I'm trying to get SQL server agent running on my sql server 2005. It appears to start up fine, but when I try to run a job, I get the following errors:
[298] SQLServer Error: 65535, SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]

[165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]

[298] SQLServer Error: 65535, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]

[382] Logon to server 'COMPUTERNAME' failed (ConnAttemptCachableOp)

I've looked at the server and it does appear to allow remote connections. I'm wondering why I'd get this message though since sql agent is on the local server.

I've tried changing the account that SQL Server Agent uses and it doesn't seem to matter. Does anyone has any suggestions?

QPR

who is the owner of the "job"?
does that owner have sysadmin rights on the server?

ASKER CERTIFIED SOLUTION

QPR

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

leos_

ASKER

the owner of the job does have sysadmin rights on the server

leos_

ASKER

the article http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx did pose some interesting questions. I'm not sure whether or not things are connecting right. So I went into ODBC connections and tried to make a System DNS connection. I noticed there that one of the connections to the server had "/sql2005" appended to it. Since this server only runs sql2005 we don't need this, so I removed it. Now I'm getting a whole new set of errors:

[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]

[382] Logon to server 'COMPUTERNAME' failed (ConnAttemptCachableOp)

Suggestions?

leos_

ASKER

OK, so I solved the issue. Somehow in the SQL server Configuration Manager, an alias got made pointing our machine name to the DNS we used to connect remotely to the machine. Once this was removed, everything worked fine. I'm not sure how this was added since I wasn't the one who installed and initially configured the database. Thanks for your help.

leos_

ASKER

Thanks for your help. The website you directed me to eventually led me the the answer.

GemOss

What did it for me was deleting/renaming the 'SQLAGENT.OUT' file and then restarting the SQL Server Agent service. After the succesfull restart, a new file was created.