Error 18456 Severity: 14 State 11 problem

I am installing diskeeper administrator on one server with at database on our sql2005 server. When I am trying to connect to the database the diskeeper software says verify username and password. I try to connect using windows authentication .And in the serverlog this error occurs

2006-11-27 15:04:56.01 Logon Login failed for user 'NB\Servername$'. [CLIENT: "Ipadress"]

2006-11-27 15:04:56.01 Logon Error: 18456, Severity: 14, State: 11.

When i try to connect with Sql server authentication, this error occurs in the log:

2006-11-27 15:48:35.46 Logon Login failed for user 'NB\SERVERNAME$'. [CLIENT: ipadress

]2006-11-27 16:04:22.94 Logon Error: 18456, Severity: 14, State: 16.

I have tried to disable filesharing, and run installation of diskeepper as the domain administrator. But the same error occurs.

Can anyone help me with this

Regards Oyvind

State 11 indicates an error determining the database to be used after authentication. This could happen if the database cannot be accessed for some reason. You could try to connect to the master database initially, to see if that works, then change context to the database that you normally use and see what error you encounter, if any.

However, I am not familiar with the diskeeper software and I don't understand its relation with SQL Server, so I'm not sure how to help you further.

Thanks
Laurentiu

|||

Diskeeper do not have any link with SQL Server in this case, and also it is no use in running for linked server related error.

What is the privilege for the account used on the linked server?

Refer to KBA http://support.microsoft.com/kb/889646 fyi.

|||

The privilege for the account is sysadmin.

The default database is master.

I also tried to connect with odbc, but the same error occurs

Regards

Oyvind

|||have you contacted the vendor in this case?|||

Correction to my previous post: the state discussion applies to state 16, not to state 11.

State 11 indicates a different problem.

What is strange is that, while you mention using Windows and SQL authentication, both connections appear to be attempted via Windows authentication, using the machine account credentials.

Best thing would be to check with the diskeeper customer support.