July 25, 2006 at 7:06 am
I support an application that runs on SQL Server 2000 (8.00.818) on 2-Node Clusters on Windows 2003 Advanced Server. The 3rd Party app has 2 services that are configured to connect to the database when the services start. About a week ago on Node 1, the services quit starting correctly. I ran profiler to determine the errors and found a SQL 911 error. I had the apps team examine the configuration file to see why it was passing invalid data to the database (the database was refusing connections). When we try to start the service, at the windows layer it gives a 1067. In the event log, it says that the service enters a running state and immediately aborts (because of the SQL 911 error).
When we fail the database an app to the other node, everything runs perfectly. Has anyone seen anything like this on a cluster? If so how did you resolve. I've check all the SQL Binaries and libraries and they all check out as valid. We're scratching our heads over this one and hope we don't have to rebuild this node.
Ideas?
July 25, 2006 at 9:27 am
Do your apps connect to the sql cluster via NT Auth?
July 25, 2006 at 9:27 am
Do your apps connect to the sql cluster via NT Auth?
July 25, 2006 at 9:30 am
Nope, they authenticate with SQL Server Authentication passed by an app module.
July 25, 2006 at 9:52 am
Could not locate entry in sysdatabases for database '%.*ls'. No entry found with that name. Make sure that the name is entered correctly.
Is that the error you are receiving? If it is so then I think you should review the user permissions on both servers. I have faced this situation for a couple of times. The account that runs sql service may not have necessery rights on the failing node of cluster.
July 28, 2006 at 12:15 pm
We've verified the permissions are solid.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply