0

I've recently stumble across this problem but cannot fins a reason for this and a workaround.

I've logged on with my domain admin account on a server (Windows Server 2008 R2) and started a service that were set to start manually. After wards when another user with a domain account logged on and had a look at the service as were experiencing problems it showed that the service were in the stopped state although in my session which were still open it showed that it started.

He started the service and everything work after that.

Can anyone shed some light on this for me? And on what to do rectify this or have a workaround for this?

Appreciate you comments and suggestions.

koosvn069
  • 1
  • 2
  • I'm guessing the service stopped for some reason between when you checked it and when the other user logged in. The management console was just showing you out-of-date information, because you didn't press refresh. – Harry Johnston Dec 02 '14 at 01:33

1 Answers1

-1

Your service does not to answer correctly to the SCM with SERVICE_CONTROL_INTERROGATE and it span another process with the StartServiceCtrlDispatcher(DispatchTable).

We can't do anything there unless you patch your application or contact your software vendor.

yagmoth555
  • 193
  • 3
  • 11