Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 9 replies
  • Subscribers 1 subscriber
  • Views 296273 views
  • Users 0 members are here
Options
Suggested
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

SEC v5.0.0.8 and Sophos Web Intelligence Update Service

toddh

Hey,

I had to do a reboot on our Sophos server over the weekend. Upon coming back up the system was complaining that there was a service that had failed to start. The service was the Sophos Web Intelligence Update Service.

Currently the "Startup Type" is set to "Automatic"

If I attempt to start the service manually, it starts and stops immediately and I get the Windows message stating this.

I am assuming that since the "Startup Type" is "Automatic" that this service should be in the "running" state.

I have checked the Windows Event Viewer and there is nothing logged there about the service.

I have also gone through the logs for Sophos and I haven't been able to find anything that might explain

why this service isn't starting.

Is there anything I can do to try and troubleshoot what the issue is? Or are there logs that perhaps I am missing that might reveal the issue?

Thank you

:21957


This thread was automatically locked due to age.
Parents
  • 0

    "C:\ProgramData\Sophos\Web Intelligence\swi_update_64.exe" /help   - This command yielded some interesting results.

    LSP = Layered Service Provider ?

    If so, I am assuming it is required to start so early because if the Web Intelligence portion of the software does have an update it would need to be updated before the swi service itself is started. Otherwise updates would not take effect until next reboot or the service is restarted?

    I was wondering what the purpose of the options "/enableLsp", "/disableLsp", and "forceDisableLsp"?

    In what instance would you want to use these options. 

    For the option "disableLsp" would this prevent the ability to SWI to be able to monitor the traffic coming through the web browser into the PC? This would effectively disable SWI without shutting off the service? But since this is for the update exe.. Are these options required depending upon whether or not the service decides it needs to update?

    Perhaps it disables LSP long enough for SWI to update, and then it is re-enabled?

    :21969
Reply
  • 0

    "C:\ProgramData\Sophos\Web Intelligence\swi_update_64.exe" /help   - This command yielded some interesting results.

    LSP = Layered Service Provider ?

    If so, I am assuming it is required to start so early because if the Web Intelligence portion of the software does have an update it would need to be updated before the swi service itself is started. Otherwise updates would not take effect until next reboot or the service is restarted?

    I was wondering what the purpose of the options "/enableLsp", "/disableLsp", and "forceDisableLsp"?

    In what instance would you want to use these options. 

    For the option "disableLsp" would this prevent the ability to SWI to be able to monitor the traffic coming through the web browser into the PC? This would effectively disable SWI without shutting off the service? But since this is for the update exe.. Are these options required depending upon whether or not the service decides it needs to update?

    Perhaps it disables LSP long enough for SWI to update, and then it is re-enabled?

    :21969
Children
No Data