MSSQLServer Service Terminated with error 17058

#1

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks

#2

You'll want to set the SQL Server Service to Manual instead of
Automatic on both servers. The SQL Server Service is started by the
cluster service, not by using the automatic setting on Cluster
servers.

By setting the services to Manual startup this error message will go
away.

Denny

On Thu, 17 Jul 2008 11:40:02 -0700, Tony
<nospam4tony (AT) nospam (DOT) postalias> wrote:

Quote:

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks

#3

You'll want to set the SQL Server Service to Manual instead of
Automatic on both servers. The SQL Server Service is started by the
cluster service, not by using the automatic setting on Cluster
servers.

By setting the services to Manual startup this error message will go
away.

Denny

On Thu, 17 Jul 2008 11:40:02 -0700, Tony
<nospam4tony (AT) nospam (DOT) postalias> wrote:

Quote:

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks

#4

You'll want to set the SQL Server Service to Manual instead of
Automatic on both servers. The SQL Server Service is started by the
cluster service, not by using the automatic setting on Cluster
servers.

By setting the services to Manual startup this error message will go
away.

Denny

On Thu, 17 Jul 2008 11:40:02 -0700, Tony
<nospam4tony (AT) nospam (DOT) postalias> wrote:

Quote:

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks

#5

You'll want to set the SQL Server Service to Manual instead of
Automatic on both servers. The SQL Server Service is started by the
cluster service, not by using the automatic setting on Cluster
servers.

By setting the services to Manual startup this error message will go
away.

Denny

On Thu, 17 Jul 2008 11:40:02 -0700, Tony
<nospam4tony (AT) nospam (DOT) postalias> wrote:

Quote:

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks

#6

You'll want to set the SQL Server Service to Manual instead of
Automatic on both servers. The SQL Server Service is started by the
cluster service, not by using the automatic setting on Cluster
servers.

By setting the services to Manual startup this error message will go
away.

Denny

On Thu, 17 Jul 2008 11:40:02 -0700, Tony
<nospam4tony (AT) nospam (DOT) postalias> wrote:

Quote:

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks

#7

You'll want to set the SQL Server Service to Manual instead of
Automatic on both servers. The SQL Server Service is started by the
cluster service, not by using the automatic setting on Cluster
servers.

By setting the services to Manual startup this error message will go
away.

Denny

On Thu, 17 Jul 2008 11:40:02 -0700, Tony
<nospam4tony (AT) nospam (DOT) postalias> wrote:

Quote:

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks

#8

You'll want to set the SQL Server Service to Manual instead of
Automatic on both servers. The SQL Server Service is started by the
cluster service, not by using the automatic setting on Cluster
servers.

By setting the services to Manual startup this error message will go
away.

Denny

On Thu, 17 Jul 2008 11:40:02 -0700, Tony
<nospam4tony (AT) nospam (DOT) postalias> wrote:

Quote:

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks

#9

You'll want to set the SQL Server Service to Manual instead of
Automatic on both servers. The SQL Server Service is started by the
cluster service, not by using the automatic setting on Cluster
servers.

By setting the services to Manual startup this error message will go
away.

Denny

On Thu, 17 Jul 2008 11:40:02 -0700, Tony
<nospam4tony (AT) nospam (DOT) postalias> wrote:

Quote:

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks

#10

You'll want to set the SQL Server Service to Manual instead of
Automatic on both servers. The SQL Server Service is started by the
cluster service, not by using the automatic setting on Cluster
servers.

By setting the services to Manual startup this error message will go
away.

Denny

On Thu, 17 Jul 2008 11:40:02 -0700, Tony
<nospam4tony (AT) nospam (DOT) postalias> wrote:

Quote:

I have a SQL 2005 SP2 cluster. I recently applied some patches to the stand
by node and noticed an error on reboot.

The error in the system log is:

Event ID 7024

The SQL Server (MSSQLSERVER) service terminated with service-specific error
17058 (0x42A2).

There are also errors in the application log. They are:

Event ID 17058

initerrlog: Could not open error log file 'R:\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG'. Operating system error = 3(The system
cannot find the path specified.).

In looking through the log, these have happened on a previous reboot. I
just missed them at the time.

The primary node continued to run fine and when I fail over to the stand by,
it does so successfully and the mssqlserver service starts successfully then.

Is this a problem or is it normal for the node that does not have access to
the shared resource?

Thanks