Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 5278 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

SIPSManager in failure state

Marco_COGC

We recently had a power cut which seems to have killed our Sophos Enterprise Server 4.5. At first we where having a problem with the database which fortunately has now (we think) been sorted.

Although everything seems to be running now, the server is actually doing nothing, not updating computers, now contacting computers, and still reporting the same amount of computers connected to the server.

We have managed to solve most of the problems within the event manager but still seem to have one that I can not find any information about.

"The requested compnent 'SIPSManager' is in a failure state. The component will not be returned."

Any advise how to sort this problem would be greatly appreciated.

:41679


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

    Hello Marco_COGC,

    SIPSManager is a client (i.e. SAV) component and I don't think it (or its failure) interferes with SEC operation.

    not updating computers

    SEC (or rather SUM) just downloads the updates, it's the endpoints fetching updates from the CID. How did you determine not updating? The Update Managers view should tell you the status of SUM, particularly the Download status column will tell you the time of the last download attempt.

    now (guess it should be not) contacting computers ... same amount of computers connected

    Again, the endpoints have to make contact. SEC remembers (from the database) the last state for a certain period but should eventually show them as disconnected. No change indicates some internal error.

    So I assume your problem is somewhere else. Are all the Sophos services on the server running? Is there a large number of envelopes? Is SUM updating (the information in the console might not be correct if there is an internal communication error) - please check if the SUM logs are written and to the same for RMS.

    Christian

    :41685
Reply
  • 0

    Hello Marco_COGC,

    SIPSManager is a client (i.e. SAV) component and I don't think it (or its failure) interferes with SEC operation.

    not updating computers

    SEC (or rather SUM) just downloads the updates, it's the endpoints fetching updates from the CID. How did you determine not updating? The Update Managers view should tell you the status of SUM, particularly the Download status column will tell you the time of the last download attempt.

    now (guess it should be not) contacting computers ... same amount of computers connected

    Again, the endpoints have to make contact. SEC remembers (from the database) the last state for a certain period but should eventually show them as disconnected. No change indicates some internal error.

    So I assume your problem is somewhere else. Are all the Sophos services on the server running? Is there a large number of envelopes? Is SUM updating (the information in the console might not be correct if there is an internal communication error) - please check if the SUM logs are written and to the same for RMS.

    Christian

    :41685
Children
No Data