![]() Be aware there are limits to this, 120000 (decimal) is the maximum value I’ve seen consistently work across the different Windows OS’. ![]() You can do this yourself by using Registry Editor and changing the following: HKLM\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeoutĬhange this DWORD from 30000 (decimal) to whatever value you want, it’s measured in milliseconds. Recently I’d added more VMs to my hypervisor, which is where my VBR virtual machine was also residing, it’s on a single 7.2k RPM disk so the IO is not anything to brag about.īy default Windows will allow 30 seconds for a service to start, so maybe I was just delivering too little IO to the service/VM? To test this, I changed the service timeout from 30 seconds to 120 seconds. The service runs as a local service though, that wouldn’t do it surely? After checking through my notes and confirming that wasn’t the problem, I pushed on. But this time I could remember, I’d changed the VBR server to be domain joined. I’m one of those people that doesn’t lab every day, maybe twice a week, so there are periods of amnesia (not really, just sleeping) between sessions and I can’t quite remember what I was in the middle of. Puzzled? I was! Now lets troubleshoot this! Hour 2: What did I change? Removing 'Initial Catalog' property from connection string Connecting to SQL Server (CurrentUser=, ServerInstance=, Options=) This was my log, if you don’t load/can’t read images, the final three lines contained the following: Minimal supported database server version is. ![]() I fired up my Veeam Backup
0 Comments
Leave a Reply. |