No really. See this exerpt from my daily morning time involving fixing a screwed up network connectivity under Virtual Server 2005.
C:\> net start "Virtual Server"
The Virtual Server service is starting..............
The Virtual Server service could not be started.
More help is available by typing NET HELPMSG 3523
Okay… Now my first question is why are they not simply calling the help message and displaying it directly? Because they like to make me type? Mmkay, so I indulge this and decide to try their useful command.
C:\> net HELPMSG 3523
The *** service could not be started.
C:\>
WOW. Geez thanks for the info! I don’t know what I would have done without that. The event log reveals “The service did not respond in a timely fashion” — which means that it got tired of waiting for Virtual Server and the virtual machines to start. Sad thing is, they’re all running. Sometimes, I think I make Bill Gates cry by using the command line…
Now time to go put my dirty hands in the registry to increase the timeout value…
Hey-
Did you ever get the VC service to start through command line? I’m having the same issue and stumpled upon this. Perhaps you can shed some light…thanx.
Hi!
The problem was that the service will not return that it finished successfully until a large part of the Virtual Server guest machine has started up — which apparently takes too long, so the message will appear on the console, and when starting the service through cmd.exe.
The thing is, the service works great, it started successfully — Windows just got tired of waiting for it.
A solution could be to edit the registry, at
HKEY LOCAL MACHINESystemCurrentControlSetServicesServiceNameParameters
Create a new dword value with the name “WaitHintStart”. The parameter is the amount of time to wait in miliseconds. Enter a large value at first, like 24 hours (86400000 milliseconds). Then launch the service and see how long it takes to start, then adapt the value to match this more closely.
You can also use “WaitHintStop” to accomplish the same, but at shutdown.
I hope this helps.
Since you were kind in enough to respond so quickly I just wanted to let you know what the results were. Unfortunately I was never able to get the vpxd service to start via the command line so I ended up using a VB script to start and stop the service and it’s working great. Thanks again!