"could not open error log file" on incorrect SQL cluster node

  • Hi. We have 2-node SQL 2012 cluster running as VMs in Hyper-V. The cluster hosts 4 SQL instances, running in active-active mode (2 instances per node).

    For reference, let's call instances Instance1-4 and nodes Node1-2.

    The problem: Instance3 is currently running on Node2 and there are no errors related to this instance in eventlog on Node2. However on Node1, the application eventlog is repeatedly spammed by events with ID 17058 with the MSSQL$Instance3 name as the source. The error is "initerrlog: Could not open error log file 'K:\MSSQL11.Instance3\MSSQL\Log\ERRORLOG'. Operating system error = 3(The system cannot find the path specified.)."

    That error makes sense, since the instance is running on Node2 and therefore the disk K: is currently accessible/mapped to Node2 and not Node1.

    The question is, why does this error appear on Node1 and where is it coming from??

    Thanks in advance

  • Are you using SCCM?

    Could be the same issue as here http://social.msdn.microsoft.com/Forums/officeapps/en-US/4dee5138-4726-4c5b-a7e5-a79ab3a6286c/sql-passive-node-could-not-open-error-log-file ?

    [font="Verdana"]Markus Bohse[/font]

  • Actually yes, this is a SCCM's SQL instance. Thanks for the pointer, however it seems there's no solution to the problem. Guess I'll have to configure our monitoring system to ignore this message :/

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply