J
Jon Espen Carlsen
Guest
I've got a bit of a headache. Im trying to control the startup order of a few
services, but I cant get to actually work. Platform, Windows 2003 SP2 R2
I started with using the "dependency" method, but adding the
"DependOnService" for the services in question.
The service "lanmanserver" (shares) depends on a SAN-disk and it's service,
"Z-SANService".
So I added the key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver]
"DependOnService"=hex(7):5a,00,2d,00,53,00,41,00,4e,00,53,00,65,00,72,00,76,00,\
69,00,63,00,65,00,00,00,4e,00,6c,00,61,00,00,00,00,00
No joy - the shares are not created in timely manner enough after the
volumes are available.
I tested with 3 other services that depends on the availability of shares -
I set them to be depended on "lanmanserver".
Looking at the services in the service-console shows the dependency correctly.
Rebooting the server - still no joy. The services that are told to depend on
lanmanserver starts up too soon, according to the even-log. "Failed to start
service, path not found". (Yes, they are stored on the SAN disk - the whole
solution is stored there.
So I researched some more. It seems you can change the "ServiceGroupOrder"
too in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder
I tried to find if lanmanserver was part of a group, obviously it was not.
So I added all of them there, just to see if it worked.
At the end I appended:
Z-SANService
lanmanserver
MEngine
MTask
MTrigger
Still no joy - the MEngine (stored on the SAN disk) is still not found.
Any ideas? Do I have a bug here? Or are there other things I can try?
services, but I cant get to actually work. Platform, Windows 2003 SP2 R2
I started with using the "dependency" method, but adding the
"DependOnService" for the services in question.
The service "lanmanserver" (shares) depends on a SAN-disk and it's service,
"Z-SANService".
So I added the key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver]
"DependOnService"=hex(7):5a,00,2d,00,53,00,41,00,4e,00,53,00,65,00,72,00,76,00,\
69,00,63,00,65,00,00,00,4e,00,6c,00,61,00,00,00,00,00
No joy - the shares are not created in timely manner enough after the
volumes are available.
I tested with 3 other services that depends on the availability of shares -
I set them to be depended on "lanmanserver".
Looking at the services in the service-console shows the dependency correctly.
Rebooting the server - still no joy. The services that are told to depend on
lanmanserver starts up too soon, according to the even-log. "Failed to start
service, path not found". (Yes, they are stored on the SAN disk - the whole
solution is stored there.
So I researched some more. It seems you can change the "ServiceGroupOrder"
too in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder
I tried to find if lanmanserver was part of a group, obviously it was not.
So I added all of them there, just to see if it worked.
At the end I appended:
Z-SANService
lanmanserver
MEngine
MTask
MTrigger
Still no joy - the MEngine (stored on the SAN disk) is still not found.
Any ideas? Do I have a bug here? Or are there other things I can try?