February 12, 2009 at 8:35 am
Hello,
I am having problems bringing up SQL server in one of my cluster nodes. Both servers are using the same service account for SQL server and they are added to the Administrators group in both nodes.
Below are the logs in the event viewer:
[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Login timeout expired
Below is the trace in ERRORLOG:
2009-02-12 03:44:04.48 Server Microsoft SQL Server 2005 - 9.00.3257.00 (X64)
Jun 12 2008 16:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2009-02-12 03:44:04.48 Server (c) 2005 Microsoft Corporation.
2009-02-12 03:44:04.48 Server All rights reserved.
2009-02-12 03:44:04.48 Server Server process ID is 7208.
2009-02-12 03:44:04.48 Server Authentication mode is MIXED.
2009-02-12 03:44:04.48 Server Logging SQL Server messages in file 'S:\MSSQL\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-02-12 03:44:04.48 Server This instance of SQL Server last reported using a process ID of 4552 at 2/12/2009 3:42:34 AM (local) 2/12/2009 3:42:34 AM (UTC). This is an informational message only; no user action is required.
2009-02-12 03:44:04.48 Server Registry startup parameters:
2009-02-12 03:44:04.48 Server -d S:\MSSQL\MSSQL.1\MSSQL\DATA\master.mdf
2009-02-12 03:44:04.48 Server -e S:\MSSQL\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-02-12 03:44:04.48 Server -l S:\MSSQL\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-02-12 03:44:04.48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-02-12 03:44:04.48 Server Detected 4 CPUs. This is an informational message; no user action is required.
2009-02-12 03:44:04.49 Server Cannot use Large Page Extensions: lock memory privilege was not granted.
2009-02-12 03:44:04.62 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-02-12 03:44:04.63 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-02-12 03:44:04.65 Server The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
2009-02-12 03:44:04.65 Server Database mirroring has been enabled on this instance of SQL Server.
2009-02-12 03:44:04.66 spid5s Starting up database 'master'.
2009-02-12 03:44:04.68 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-02-12 03:44:04.70 spid5s SQL Trace ID 1 was started by login "sa".
2009-02-12 03:44:04.70 spid5s Starting up database 'mssqlsystemresource'.
2009-02-12 03:44:04.70 spid5s The resource database build version is 9.00.3257. This is an informational message only. No user action is required.
2009-02-12 03:44:04.76 spid5s Server name is 'USGDC-VBWDBP\BP1'. This is an informational message only. No user action is required.
2009-02-12 03:44:04.76 spid5s The NETBIOS name of the local node that is running the server is 'USGDC-SBW02P'. This is an informational message only. No user action is required.
2009-02-12 03:44:04.76 spid9s Starting up database 'model'.
2009-02-12 03:44:04.79 spid9s Clearing tempdb database.
2009-02-12 03:44:04.85 spid9s Starting up database 'tempdb'.
2009-02-12 03:44:04.87 spid9s Analysis of database 'tempdb' (2) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2009-02-12 03:44:04.88 spid12s The Service Broker protocol transport is disabled or not configured.
2009-02-12 03:44:04.88 spid12s The Database Mirroring protocol transport is disabled or not configured.
2009-02-12 03:44:04.90 spid12s Service Broker manager has started.
2009-02-12 03:44:04.99 Server A self-generated certificate was successfully loaded for encryption.
2009-02-12 03:44:05.01 Server Server is listening on [ 192.168.4.115 4052].
2009-02-12 03:44:05.01 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\BP1 ].
2009-02-12 03:44:05.01 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\USGDC-VBWDBP\MSSQL$BP1\sql\query ].
2009-02-12 03:44:05.02 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2009-02-12 03:44:05.02 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-02-12 03:44:05.04 spid18s Starting up database 'BP1'.
2009-02-12 03:44:05.04 spid19s Starting up database 'msdb'.
2009-02-12 03:44:05.09 spid18s Analysis of database 'BP1' (5) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2009-02-12 03:44:05.29 spid18s CHECKDB for database 'BP1' finished without errors on 2009-02-01 01:00:21.997 (local time). This is an informational message only; no user action is required.
2009-02-12 03:44:05.31 spid5s Recovery is complete. This is an informational message only. No user action is required.
2009-02-12 03:47:35.29 spid12s Service Broker manager has shut down.
2009-02-12 03:47:35.31 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2009-02-12 03:47:35.31 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Comparing it with log for the cluster node where SQL server starts successfully, I only see that it had no entry: Cannot use Large Page Extensions: lock memory privilege was not granted. However, I also checked on the local policy for user rights and it shows that no user is granted with lock memory pages on both nodes.
Does someone have an idea on how to resolved this or where else I can look at to help me solve this?
Thanks,
Regina
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply