Increase Service Startup Timeout Value?

#1

I do all of my development work in a 64bit Windows 7 Virtual Machine
using VMWare. In order to test software in multiple versions of SQL
Server I have four instances running in it, a SQl Express and SQL
Server instance for both 2005 and 2008.

Mmost of the time one or more instances will fail to start at boot
time. The event log indicates that it failed to start in the alloted
time, 30000 milliseconds.

I looked through all of the instances properties but could not find
anywhere that I could boost that value up any. I tried checking the
boost priority checkbox on the processor page but that didn't help.

Any suggestions?

#2

Joe Cool (joecool1969 (AT) live (DOT) com) writes:

Quote:

I do all of my development work in a 64bit Windows 7 Virtual Machine
using VMWare. In order to test software in multiple versions of SQL
Server I have four instances running in it, a SQl Express and SQL
Server instance for both 2005 and 2008.

Mmost of the time one or more instances will fail to start at boot
time. The event log indicates that it failed to start in the alloted
time, 30000 milliseconds.

I looked through all of the instances properties but could not find
anywhere that I could boost that value up any. I tried checking the
boost priority checkbox on the processor page but that didn't help.

This timeout is not SQL Server-specifc, but a general Windows parameter.
You can control it through the registy. The key name is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\SerivcesPipeTimeout. It
should be a DWORD, and the value is in milliseconds.

Beware that the name has "Services" in plural. I had it spelt in singular
on my machine, and it was driving me crazy why it did not work, when
it worked on another machine.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

#3

On Feb 1, 4:42*pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:

Quote:

Joe Cool (joecool1... (AT) live (DOT) com) writes:
I do all of my development work in a 64bit Windows 7 Virtual Machine
using VMWare. In order to test software in multiple versions of SQL
Server I have four instances running in it, a SQl Express and SQL
Server instance for both 2005 and 2008.

Mmost of the time one or more instances will fail to start at boot
time. The event log indicates that it failed to start in the alloted
time, 30000 milliseconds.

I looked through all of the instances properties but could not find
anywhere that I could boost that value up any. I tried checking the
boost priority checkbox on the processor page but that didn't help.

This timeout is not SQL Server-specifc, but a general Windows parameter.
You can control it through the registy. The key name is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\SerivcesPipeTimeout. It
should be a DWORD, and the value is in milliseconds.

Beware that the name has "Services" in plural. I had it spelt in singular
on my machine, and it was driving me crazy why it did not work, when
it worked on another machine.

That key does not exist in my computer. Does that mean 30000 ms is the
default and in order to override that I need to create one with the
overriding value I want to specify?

#4

On Feb 1, 5:20*pm, Joe Cool <joecool1... (AT) live (DOT) com> wrote:

Quote:

On Feb 1, 4:42*pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:

Joe Cool (joecool1... (AT) live (DOT) com) writes:
I do all of my development work in a 64bit Windows 7 Virtual Machine
using VMWare. In order to test software in multiple versions of SQL
Server I have four instances running in it, a SQl Express and SQL
Server instance for both 2005 and 2008.

Mmost of the time one or more instances will fail to start at boot
time. The event log indicates that it failed to start in the alloted
time, 30000 milliseconds.

I looked through all of the instances properties but could not find
anywhere that I could boost that value up any. I tried checking the
boost priority checkbox on the processor page but that didn't help.

This timeout is not SQL Server-specifc, but a general Windows parameter..
You can control it through the registy. The key name is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\SerivcesPipeTimeout.. It
should be a DWORD, and the value is in milliseconds.

Beware that the name has "Services" in plural. I had it spelt in singular
on my machine, and it was driving me crazy why it did not work, when
it worked on another machine.

That key does not exist in my computer. Does that mean 30000 ms is the
default and in order to override that I need to create one with the
overriding value I want to specify?

I assumed this to be the case and created a new key with a DWORD value
of 60000.

I rebooted and all instances started up fine, so based on that one
reboot, this appears to have solved this problem.

Thanks for your help.

#5

Joe Cool (joecool1969 (AT) live (DOT) com) writes:

Quote:

That key does not exist in my computer. Does that mean 30000 ms is the
default and in order to override that I need to create one with the
overriding value I want to specify?

Yes, that is correct. Sorry, if I wasn't clear.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Increase Service Startup Timeout Value?

comp.databases.ms-sqlserver comp.databases.ms-sqlserver

Increase Service Startup Timeout Value? - 02-01-2011 , 01:08 PM

Re: Increase Service Startup Timeout Value? - 02-01-2011 , 03:42 PM

Re: Increase Service Startup Timeout Value? - 02-01-2011 , 04:20 PM

Re: Increase Service Startup Timeout Value? - 02-01-2011 , 05:33 PM

Re: Increase Service Startup Timeout Value? - 02-02-2011 , 02:13 AM