This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot start HitmanPro.Alert service on Intercept X

mh3000 over 3 years ago

Hello everyone,

I have two Windows Servers that report the HitmanPro.Alert service as Stopped.

Once I open windows services and try to manually start it I get this message:

"Windows coul not start the HitmanPro.Alert service service on Local Computer.

Error 32: The process cannot access the file because it is being used by another process"

I cant see any related process running into the task manager windows.

Also, before trying to start the HitmanPro.Alert service I stop the Sophos AutoUpdate Service.

Something that catches my attention is that eventhough I stop the Sophos AutoUpdate Service, the Update Status hangs in a permanent "loading" indicator.

Is this permanent updating status related to why I cannot start de HitmanPro.Alert service?

Please advise.

Thanks in advance.

This thread was automatically locked due to age.

0 FormerMember over 3 years ago

Hi,

What listed in the autoupdate log? If the update failed and the file is in a perpetual lock or corrupted - that would prevent service start.

Have you done a restart of the machine? Not a shutdown - but a restart to see if that clears the action?
Cancel
Vote Up 0 Vote Down

Cancel