We had a DTS package that was working fine until yesterday and since
today it does not work and we get the following error message:


[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'(null)'. Reason not associated with a trusted SQL Server connection.


Please clarify how do we fix this problem.

Thanks
Karen

Hi
Did you change Authentication mode of SQL Server?



<karenmiddleol (AT) yahoo (DOT) com> wrote

Hey Karen!

Generally when you see the "login failed for user NULL" it's a kerberos issue.
I know that sounds far fetched, but it's true.
If you get "login failed for user BOB" that's a different story. But the
fact that we are passing a NULL value to SQL instead of a user token means
that Kerberos is failing.
Sometimes this is called a double hop scenario, but you can get that error
even when there is only a single hop.

Follow this article to resolve that error:
How to troubleshoot the "Cannot generate SSPI context" error message
This step-by-step article describes how to troubleshoot the most typical
sources of the "Cannot generate SSPI context" error message. You may receive
this error message under the following conditions: You are connecting to SQL
Server.You are using...
http://support.microsoft.com/default...b;en-us;811889

Basically you will be getting the utility setspn, dropping the old spn and
recreating a new SPN (rebooting might be necessary).

Donna Lambert

"karenmiddleol (AT) yahoo (DOT) com" wrote:

You may also want to check that the account logging in hasn't been
locked out because of invalid password entries exceeding the limit set.

Usually this scenario takes place when you are forced to change your
password, but services are running using old passwords and try to login
multiple times. If the account is locked out because of this, you will
see this error message.

Simon Worth

Donna Lambert wrote: