November 28, 2012 at 10:49 am
I have 2 Instances installed in a 2 Node Cluster. Windows 2008R2 and SQL Server 2008 R2.
currently, all Cluster resources (The Quorum and both sets of Cluster Resources - 1 set for each Instance) reside on Node 1 of the Cluster.
What is puzzling is on the passive node of the Cluster I see the following errors in the Application Event Log for the Server:
initerrlog: Could not open error log file 'F:\MSSQLxx_xx.MSSQLSERVER\MSSQL\Log\ERRORLOG'. Operating system error = 3(The system cannot find the path specified.).
MSSQLSERVER is my Default Instance and the F: drive is a cluster resource associated with the default Instance.
Since no Cluster resources are currently owned by the passive node, I checked the Server's Services Applet on the passive node and see the following Services running:
SQL Server Browser
SQL Server Integration Services 10.0
SQL Server VSS Writer
I am trying to figure out why these services are running on the passive node and if they are the cause of the errors I am seeing in the event log.
Can anyone help me out?
November 28, 2012 at 12:07 pm
Jpotucek (11/28/2012)
I have 2 Instances installed in a 2 Node Cluster. Windows 2008R2 and SQL Server 2008 R2.currently, all Cluster resources (The Quorum and both sets of Cluster Resources - 1 set for each Instance) reside on Node 1 of the Cluster.
What is puzzling is on the passive node of the Cluster I see the following errors in the Application Event Log for the Server:
initerrlog: Could not open error log file 'F:\MSSQL10_50.MSSQLSERVERDDI\MSSQL\Log\ERRORLOG'. Operating system error = 3(The system cannot find the path specified.).
MSSQLSERVERDDI is my Default Instance and the F: drive is a cluster resource associated with the default Instance.
Since no Cluster resources are currently owned by the passive node, I checked the Server's Services Applet on the passive node and see the following Services running:
SQL Server Browser
SQL Server Integration Services 10.0
SQL Server VSS Writer
I am trying to figure out why these services are running on the passive node and if they are the cause of the errors I am seeing in the event log.
Can anyone help me out?
Those services are not cluster aware and will be running.
What is the startup set for the sql server services on the passive node?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 28, 2012 at 12:15 pm
Startup set on the passive node.
Path to executable
C:\Program Files\Microsoft SQL Server\MSSQLxx_xx.MSSQLSERVER\MSSQL\Binn\sqlservr.exe" -sMSSQLSERVER
Service is set to Manual and is stopped
November 29, 2012 at 11:35 am
does anyone know where this is set??
C:\Program Files\Microsoft SQL Server\MSSQLxx_xx.MSSQLSERVER\MSSQL\Binn\sqlservr.exe" -sMSSQLSERVER
I can't figure out why I am getting these errors on the passive node..
November 29, 2012 at 1:35 pm
That's correct, the service should be set to manual.
What other info do you have in the event logs.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 29, 2012 at 1:55 pm
Nothing else in the application event log on the passive node. just this error scrolling:
initerrlog: Could not open error log file 'F:\MSSQLxx_xx.MSSQLSERVER\MSSQL\Log\ERRORLOG'. Operating system error = 3(The system cannot find the path specified.).
in the system event log on the passive node, I also see these errors periodically:
The SQL Server (MSSQLSERVER) service terminated with service-specific error %%17058.
The SQL Server (MSSQLSERVER) service entered the stopped state.
The SQL Server Services for the MSSQLSERVER instance are stopped and set to manual as they should be when the resources are all active on the other (active) node.
September 25, 2013 at 2:04 am
I had the same issue with the passive node complaining that it could not open the SQL Error log file which was placed on a cluster disk. I moved it to the C: drive making sure that exactly the same path existed on both nodes. After restarting, the error message stopped. But the problem is that each node now has part of the log history, so I seem to have solved one problem but created another.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply