November 5, 2007 at 3:57 am
We have a sql2000 clustered server running on a windows 2003 cluster, today we noticed that the
SQL resources where in a Online Pending state and do not came up anymore.
I have searched the net and found some info about the sqlstate = 08001 Native error 11 , witch indicated that the SQL Network name could have been renamed , however this is not the case here , .
i also found that there might be Resolve issue but The Cluster Name and the SQL Network name can be resolved by both Cluster nodes ..
does anyone here got experience with this kind of problem ? Pls Help
Here is a part of the cluster.log with the errors :
ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed
ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed
ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 2; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed
ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed
ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 2; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
INFO [CP] CppRegNotifyThread checkpointing key SOFTWARE\Microsoft\Microsoft SQL Server\DBHSB\MSSQLSERVER to id 4 due to timer
INFO [Qfs] QfsGetTempFileName C:\DOCUME~1\SRVCCL~1\LOCALS~1\Temp\, CLS, 13 => C:\DOCUME~1\SRVCCL~1\LOCALS~1\Temp\CLSD.tmp, status 0
According to the SQL server log the server is started and all databases are brought on-line then a stop request from Service Control Manager terminates SQL Server see log below:
2007-11-05 14:04:02.89 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )
2007-11-05 14:04:02.89 server Copyright (C) 1988-2002 Microsoft Corporation.
2007-11-05 14:04:02.89 server All rights reserved.
2007-11-05 14:04:02.89 server Server Process ID is 3264.
2007-11-05 14:04:02.89 server Logging SQL Server messages in file 'P:\mssql\MSSQL$DBHSB\log\ERRORLOG'.
2007-11-05 14:04:02.89 server SQL Server is starting at priority class 'high'(2 CPUs detected).
2007-11-05 14:04:03.61 server initdata: Warning: Could not set working set size to 823168 KB.
2007-11-05 14:04:03.66 server SQL Server configured for thread mode processing.
2007-11-05 14:04:03.72 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2007-11-05 14:04:03.77 server Attempting to initialize Distributed Transaction Coordinator.
2007-11-05 14:04:06.32 spid2 Starting up database 'master'.
2007-11-05 14:04:06.52 spid2 Server name is 'HSBSQL01\DBHSB'.
2007-11-05 14:04:06.52 spid5 Starting up database 'msdb'.
2007-11-05 14:04:06.52 spid6 Starting up database 'model'.
2007-11-05 14:04:06.52 spid8 Starting up database 'dbHSB'.
2007-11-05 14:04:06.52 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-11-05 14:04:06.56 server SQL server listening on 10.122.131.103: 1433.
2007-11-05 14:04:06.62 spid8 Analysis of database 'dbHSB' (7) is 100% complete (approximately 0 more seconds)
2007-11-05 14:04:06.63 server SQL server listening on TCP, Shared Memory, Named Pipes.
2007-11-05 14:04:06.63 server SQL Server is ready for client connections
2007-11-05 14:04:06.66 spid6 Clearing tempdb database.
2007-11-05 14:04:07.10 spid6 Starting up database 'tempdb'.
2007-11-05 14:04:07.20 spid2 Recovery complete.
2007-11-05 14:04:07.20 spid2 SQL global counter collection task is created.
2007-11-05 14:04:16.41 spid1 Warning: unable to allocate 'min server memory' of 1658MB.
2007-11-05 14:10:45.18 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
November 6, 2007 at 6:43 am
I believe the errors you are seeing are the "access denied" part of "server does not exist or access denied".
Did you remove the builtin\Administrators group from the SQL server logins or modify this group's permissions?
November 7, 2007 at 1:32 am
Hello Jeff,
no the builtin\Administrators group has not been removed from the SQL server logins nor did we change any this group's permissions.
we run some security updates last weekend , and one of these updates did not install correctly after this failed installation the problems began . ( this update failed on both servers in the cluster )
it looks like some proces is causing the SQL server to stop on the cluster, it fails over and cant start on the second node and fails back ..
i have read somewhere a security update might cause this behavior , but i am unable to pinpoint what proces is causing this problem.
September 28, 2008 at 4:01 am
Hi There,
Was anyone able to solve this problem? I'm having the same problem now and its doing my head in!
Any help woud be great!
Cheers
Sam
September 28, 2008 at 5:42 am
What does the SQL error log say?
What's you cluster config (how many nodes, how many are active?)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 28, 2008 at 5:58 am
Managed to sort the problem. I have 2 nodes A and B. I shifted all resources to A (which again failed with the error above - the sql error log was the same as the guy above minus the 'Warning: unable to allocate 'min server memory' of 1658MB' line.) rebooted node B and shifted the SQL Server Group to node B once it was back up. The services started once moved back to node B after the restart.
I am baffled to why this had happened though. All i did was manually shift the SQL Server Group initially from B to A. Is there something that needs to be checked before doing manually failovers?
September 28, 2008 at 6:29 am
What's running on Node A?
The error indicates that there's not enough memory to bring SQL online, which indicated that something else is running and is consuming the memory.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply