46d0b4ce   
   From: esquel@sommarskog.se   
      
   Joe Cool (joecool1969@live.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\Control\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@sommarskog.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   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)