I am getting this error from SQL 20

[imstillatwork]

I am getting this error from SQL 200 enterprise manager...
we are using windows authentication, my name and password are correct, the server is running properly. no one else is having this problem but me. running win2000pro..I get this error:


logon failed for user '(null)'. Reason: Not associated with a trusted SQL server connection.

 

[SQLBill]

Have you gone back to Enterprise Manager, drilled down to Security > Logins and checked that your login hasn't been changed/erased? Or if you are using ROLES, have you double-checked to make sure you are part of the ROLE?

-SQLBill

 

[imstillatwork]

yes, we've checked that. I am going to reinstall enterprise manager...

I'll let you know how it goes.

 

[imstillatwork]

no changes, still can't get in.... starting to bother me....alot...

 

[imstillatwork]

any other ideas?

 

[MeanGreen]

Here is a long shot. Try to log into SQL Analyzer using windows Authenication and see what error you are getting back. You might also try running SQL Profiler and capture NT and SQL login while logging into SQL Analyzer to see what the server thinks you are when you use Windows Login.

Hope this helps.

 

[imstillatwork]

sql query analyzer gives msg 18452 level 16 state 1

logon failed for user ('null'). Reason: Not associated with a trusted SQL server connection.

 

[MeanGreen]

In your security group for the user you are signing on as, what does it show for "TYPE" of security. Basically, under the security tab, choose logins and see what your login is set up for. For your login it should be Windows User or Windows Group and the name will usually have the DOMAIN/USERNAME in the "Name" column. You might try to reconfigure the MSSQL Service for global versus LOCAL access. I am no expert, just making some suggestions. I hope one of these will help.

Good Luck!

 

[imstillatwork]

well, leave it to windows to not accept your password. No one had touched the server, and for some reason or another, my password needed to be reset...I haven't changed my password or anytihng. no changes where ever made to the server.

owell. thanks bill g.

 

[janettx]

I was getting the same error. I then made sure that the sql 2000 eval version on my desktop had the same log in and permissions that the server had ie both servers having user.name/domain on both servers both being owners.
I was then able to use the export wizard to transfer data, however the transfered failed and all that transfered to the server was the tables and the data from the tables the stored procs didn't transfer. I feel this is a permissions issue and if anyone has any input into this I'd sure appreciate it. Thanks