May 21, 2008 at 5:12 am
We have 3 Windows 2003 Enterprise Edition SP2 running 2 instances of SQL 2005 SP2 (INST01 and INST02). There are two resource groups running on one node and one running on another leaving the third for failover.
INST01 failed over from ELESQLN1 to ELESQLN3 last night and all SQL logins failed with the below error;
Error: 18452, Severity: 14, State: 1.
Login failed for user 'SQL User Name Is Here'. The user is not associated with a trusted SQL Server connection.
All windows logins were still able to connect to INST01. All SQL logins were available with permission to connect granted, login enabled and correct user mappings and permissions on the relevant databases.
Failing INST01 back from ELESQLN3 to ELESQLN1 resolved the issue but i have been unable to find out what happened. At the moment i am trawling through the cluster.log file comparing last nights failover to a failover that didnt have any problems.
Could anyone please help?
Regards
Chris
May 21, 2008 at 5:22 am
itm sounds like security had been set to only allow windows authentication and this only took effect when instance restarted on failover. Not sure why reverted back going back to original node though. Can you check instance is set to mixed mode and do a test failover?
The value for authentication mode is held in the registry, so worth a check registry entries on both nodes are the same. Sorry cannort remember exactly where in registry and not in a position to check
---------------------------------------------------------------------
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply