October 29, 2009 at 1:02 am
Hi,
We have a/a/p cluster setup for SQL Server 2005 EE x64 with SP3. For planned maintenance on Node3, we have moved resources to Node2(Passive) and after maintenance, moved the resources to Node3(Active)
While Moving SQL groups from Active node to Passive node & vice verse, I'm getting the below errors:
Event Type:Warning
Event Source:SQLBrowser
Event Category:None
Event ID:3
Date:10/28/2009
Time:6:34:20 PM
User:N/A
Computer:NODE3
Description:
The configuration of the AdminConnection\TCP protocol in the SQL instance INS4is not valid.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type:Error
Event Source:SQLBrowser
Event Category:None
Event ID:8
Date:10/28/2009
Time:6:34:20 PM
User:N/A
Computer:NODE3
Description:
The SQLBrowser service was unable to process a client request.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type:Error
Event Source:MSSQL$INS2
Event Category:(2)
Event ID:17058
Date:10/28/2009
Time:6:34:18 PM
User:N/A
Computer:NODE3VS2
Description:
initerrlog: Could not open error log file 'I:\Microsoft SQL Server\MSSQL.3\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system cannot find the path specified.).
Are the above errors normal while moving resources or something I need fix it?
Thanks
October 29, 2009 at 2:13 am
The last error looks as though the new node doesn't have access to the folder configured for the SQL Error logs ('I:\Microsoft SQL Server\MSSQL.3\MSSQL\LOG\ERRORLOG').
Can you verify that the disk with the error log is available when the group is failed over?
Is the I: drive part of the same group as the SQL Instance?
Are you sure you have the same LUN mapped to the same drive letter on all the nodes?
October 29, 2009 at 10:47 am
The last error looks as though the new node doesn't have access to the folder configured for the SQL Error logs ('I:\Microsoft SQL Server\MSSQL.3\MSSQL\LOG\ERRORLOG').
Can you verify that the disk with the error log is available when the group is failed over?
Is the I: drive part of the same group as the SQL Instance?
Are you sure you have the same LUN mapped to the same drive letter on all the nodes?
Everything fine before & After the failover. But I'm getting the below error only during failover process.
The last error looks as though the new node doesn't have access to the folder configured for the SQL Error logs ('I:\Microsoft SQL Server\MSSQL.3\MSSQL\LOG\ERRORLOG').
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply