JP10 (7/9/2013)
yes I believe it's on a SAN (IT guy is on vacation). This happens when we restart the service only and not the server.So what was your fix on this?
Thanks.
my issues not the same as yours; in my case i had to set a service dependency, so SQL would start after the SAN service was already started.
as i remember it, you can VIEW the dependencies in Services.msc, but cannot set it there ;
to set them it was a command line argument named "sc"?, and we had to point it to a service that exists that represents the SAN, i don't have it in front of me, or i'd screenshot it.
sorry.
Lowell