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

Some Clients "Out-Of-Date"

Hi All,

We are using Sophos Enterprise Console Version 5.1.0.1839 deploying Sophos Endpoint Security & Control (version 10.0.8) to client PC's (Windows 7) and servers (2003 & 2008).

However, SEC is stating that some clients are out-of-date despite the fact that the client logs state that they have successfully updated. Could someone enlighten me as to what may be going on here and how to resolve it.

Many thanks,

JP

:33759


This thread was automatically locked due to age.
Parents
  • Hi Christian,

    Thank you for posting on this. I checked out the RMS Logs (as per your suggestion) on the affected computers and indeed I am seeing some error entries in the Router logs. An extract is shown below:

    09.10.2012 08:30:20 0070 E Failed to get messages, logging Router$SERVERNAME off
    09.10.2012 08:30:20 06B8 E Failed to send message (id=00659510) because of unknown exception, adding message back to queue
    09.10.2012 08:30:20 06B8 E Failed to send messages, logging Router$SERVERNAME off
    09.10.2012 08:30:20 06B8 E SenderWorker: Caught CORBA user exception, ID 'IDL:SophosMessaging/NotLoggedOn:1.0' during logoff
    09.10.2012 08:30:20 06B8 E SenderWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/OBJECT_NOT_EXIST:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO
     
    09.10.2012 08:30:50 06C0 I RouterTableEntry::LogonToParentRouter() - logging on as active consumer
    09.10.2012 08:30:50 06C0 I RouterTableEntry state (router, logging on): Router$SERVERNAME is passive consumer, passive supplier
    09.10.2012 08:30:50 06C0 I Logged on to parent router as Router$CLIENTPCNAME:45046
    09.10.2012 08:30:50 06C0 I This computer is part of the domain DOMAINNAME
    09.10.2012 08:32:29 07F8 E GetterWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/OBJECT_NOT_EXIST:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO
     
    09.10.2012 08:32:29 07F8 E Failed to get messages, logging Router$SERVERNAME off

    SEC is stating (as you suspected) that the client PCs have a 'Last Message Time' similar to one another (in this case 28/09/2012).

    What do you think should be my next step in resolving this issue?

    Many thanks for your kind assistance,

    JP

    :33809
Reply
  • Hi Christian,

    Thank you for posting on this. I checked out the RMS Logs (as per your suggestion) on the affected computers and indeed I am seeing some error entries in the Router logs. An extract is shown below:

    09.10.2012 08:30:20 0070 E Failed to get messages, logging Router$SERVERNAME off
    09.10.2012 08:30:20 06B8 E Failed to send message (id=00659510) because of unknown exception, adding message back to queue
    09.10.2012 08:30:20 06B8 E Failed to send messages, logging Router$SERVERNAME off
    09.10.2012 08:30:20 06B8 E SenderWorker: Caught CORBA user exception, ID 'IDL:SophosMessaging/NotLoggedOn:1.0' during logoff
    09.10.2012 08:30:20 06B8 E SenderWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/OBJECT_NOT_EXIST:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO
     
    09.10.2012 08:30:50 06C0 I RouterTableEntry::LogonToParentRouter() - logging on as active consumer
    09.10.2012 08:30:50 06C0 I RouterTableEntry state (router, logging on): Router$SERVERNAME is passive consumer, passive supplier
    09.10.2012 08:30:50 06C0 I Logged on to parent router as Router$CLIENTPCNAME:45046
    09.10.2012 08:30:50 06C0 I This computer is part of the domain DOMAINNAME
    09.10.2012 08:32:29 07F8 E GetterWorker: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/OBJECT_NOT_EXIST:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO
     
    09.10.2012 08:32:29 07F8 E Failed to get messages, logging Router$SERVERNAME off

    SEC is stating (as you suspected) that the client PCs have a 'Last Message Time' similar to one another (in this case 28/09/2012).

    What do you think should be my next step in resolving this issue?

    Many thanks for your kind assistance,

    JP

    :33809
Children
No Data