Jump to content

Recommended Posts

Posted

I don't think the Updater-B issue causes the console to do anything other than report false positives. I may be wrong.

 

Did this message occur after performing the console "fix"? Have you carried this out at all?

 

Have you checked the services to see if they are running - i've had this message when one of them has stopped

Posted
I don't think the Updater-B issue causes the console to do anything other than report false positives. I may be wrong.

 

Did this message occur after performing the console "fix"? Have you carried this out at all?

 

Have you checked the services to see if they are running - i've had this message when one of them has stopped

 

Indeed , seen this before after something took over its port , Check services and if a service is not running try and start . If it does not start check using cmd prompt what service is occupying the port

Posted

is this sophos 4.5/4.7 i used to see this all the time it with it

 

went through all sorts of trouble shooting it was easier to remove and reinstall (p.s. installing 5 over it when its broke iirc results in broken v5)

Posted

Funnily enough, I have this problem on EVERY server where I setup Sophos EM. After a time, it appears to break itself for no reason!

 

To fix this problem, simply repair Sophos EM by re-running setup. I'm running 4.5.1.0 supplied by the LA for your reference.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...