SQL 2000 Problems on One Node Only
- From: "Jerry" <digjrice@xxxxxx>
- Date: 9 Oct 2005 17:41:35 -0700
We cannot seem to figure out why our new SQL 2000 installation will
only seem to operate correctly on one of the nodes. When running on
Node2, it works fine, but will not start completely when failed over to
Node1. Both nodes have been upgraded to SP4, but Node1 has never run
correctly. The ERRORLOG looks fine. The Event log looks like:
Last good message:
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 10/9/2005
Time: 4:53:27 PM
User: N/A
Computer: VIRTUALNAME
Description:
17126 :
SQL Server is ready for client connections
First bad message:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (3)
Event ID: 17052
Date: 10/9/2005
Time: 4:53:27 PM
User: N/A
Computer: NODE1
Description:
[sqsrvres] ODBC sqldriverconnect failed
Second bad message:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (3)
Event ID: 17052
Date: 10/9/2005
Time: 4:53:27 PM
User: N/A
Computer: NODE1
Description:
[sqsrvres] checkODBCConnectError: sqlstate = 28000; native error =
4814; message = [Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Those two message then repeat a lot of times before clustering finally
gives up and fails SQL. I can ping the virtual fine from both nodes,
as well as each of the nodes' names themselves. The MSDTC service is
set up in clustering and running fine. Everything else in the cluster
fails over without issue. Anyone have any ideas? Thanks!
(for good measure, here is the SQL ERRORLOG):
SQL ERRORLOG:
2005-10-09 17:09:02.82 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: Service Pack 1)
2005-10-09 17:09:02.82 server Copyright (C) 1988-2002 Microsoft
Corporation.
2005-10-09 17:09:02.82 server All rights reserved.
2005-10-09 17:09:02.82 server Server Process ID is 2212.
2005-10-09 17:09:02.82 server Logging SQL Server messages in file
'E:\Data\SQL\DB\MSSQL\log\ERRORLOG'.
2005-10-09 17:09:02.82 server SQL Server is starting at priority
class 'normal'(2 CPUs detected).
2005-10-09 17:09:02.90 server SQL Server configured for thread mode
processing.
2005-10-09 17:09:02.91 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000] Lock Owner Blocks.
2005-10-09 17:09:02.94 server Attempting to initialize Distributed
Transaction Coordinator.
2005-10-09 17:09:04.18 spid4 Starting up database 'master'.
2005-10-09 17:09:04.30 spid4 Server name is 'VIRTUALNAME'.
2005-10-09 17:09:04.30 spid4 Starting up database 'msdb'.
2005-10-09 17:09:04.30 server Using 'SSNETLIB.DLL' version
'8.0.2039'.
2005-10-09 17:09:04.30 spid5 Starting up database 'model'.
2005-10-09 17:09:04.30 server SQL server listening on
correct.virtual.ip.address: 1433.
2005-10-09 17:09:04.33 server SQL server listening on TCP, Shared
Memory.
2005-10-09 17:09:04.33 server SQL Server is ready for client
connections
2005-10-09 17:09:04.37 spid5 Clearing tempdb database.
2005-10-09 17:09:04.93 spid5 Starting up database 'tempdb'.
2005-10-09 17:09:05.02 spid4 Recovery complete.
2005-10-09 17:09:05.02 spid4 SQL global counter collection task is
created.
.
- Follow-Ups:
- Re: SQL 2000 Problems on One Node Only
- From: Mike Epprecht \(SQL MVP\)
- Re: SQL 2000 Problems on One Node Only
- Prev by Date: Re: Time out settings in SQL cluster
- Next by Date: Re: SQL 2000 Problems on One Node Only
- Previous by thread: Re: Time out settings in SQL cluster
- Next by thread: Re: SQL 2000 Problems on One Node Only
- Index(es):
Relevant Pages
|
Loading
