Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 error: 18452

Author  Topic 

sqldbapree
Starting Member

4 Posts

Posted - 2005-10-19 : 20:30:55
We have 2 failover servers and one client in our test environment. We have all the three configured in mixed mode authentication(windows + sql server authentication). But when we are failing over from 1st server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16, State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'null'. Reason: Not associated with a trusted SQL server connection.'
If any one please help me in this regard, that would be great.
Thanks,
Preethi.

chiragkhabaria
Master Smack Fu Yak Hacker

1907 Posts

Posted - 2005-10-20 : 03:06:39
try out the followings things if its work for u ..

1) Open The SQL Server Enterprise Manager
2) Start menu > Programs > Microsoft SQL Server > Enterprise Manager)
3) Expand the tree-control until you can your server
4) Right click on the server name and "SQL Server Properties (Configure)" window will open
5) Select the Security tab
6) For "Authentication", select "SQL Server and Windows"


Complicated things can be done by simple thinking
Go to Top of Page

sqldbapree
Starting Member

4 Posts

Posted - 2005-10-20 : 11:20:22
I have done it already, then also I was getting the error.
Go to Top of Page

TG
Master Smack Fu Yak Hacker

6065 Posts

Posted - 2005-10-20 : 13:01:07
Also make sure the nt user account has access to the failover server box. Are the 2 sql servers directly communicating with each other? If so I think their sql service account names and passwords have to be the same.

Be One with the Optimizer
TG
Go to Top of Page

sqldbapree
Starting Member

4 Posts

Posted - 2005-10-20 : 18:52:52
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in the client's EM. Now what I did was, I made ser1 to run and stopped sql service in ser2 (active/passive) through failover. Now in the client's EM I'm able to open ser1 and I cannot access ser2. Now what I did was, I failed over to ser2 ( so sql service in ser1 is stopped). But now I can still be able to access ser1 and also I can access ser2, even I'm able to open query analyzer in ser1 through EM.But when I try to open query analyzer directly, it is giving the same error message. ser1 is the virtual name given to both ser1 and ser2. So I think when connecting through EM, failover is occuring fine.I'm just wondering why is this happening only with dsn. Can anybody help me?
Go to Top of Page
   

- Advertisement -