Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 0 subscribers
  • Views 29269 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

RMS issue - clients update just fine but do not report to SEC

asester

All,

It appears that after a recent update on 4/21/15 for the Sophos Update Manager on our message relay server, external clients are no longer reporting in SEC.  They are able to update as usual, but nothing reports to SEC.

After doing some digging, looking at the MRInit.conf files, policies, tearing my hair out, etc.....I think I see the issue - just not sure how to resolve it.

In the SEC application, I can see the primary server and the message relay both have the latest Update Manager version > 1.5.6.13.

However, looking at the Programs installed on the message relay server through control panel, it is not showing the proper version installed.  It shows 1.5.2.1060, whereas the primary server shows the proper 1.5.6.13 version.

I tried to run a repair on the Sophos Update Manager application on the message relay server via control panel, but that didn't change the version.  When I force an update through SEC, it downloads the binaries and appears like it's still at the latest version...

Also, using 5.2.2 on server 2008 R2.

Any help is appreciated.

:57312


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

    Well, after scratching my head enough, and seeing the error: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0.........I knew it sounded all too familiar!!!

    I went through my old posts and found this gem:  /search?q= 41705

    Viola !!!!!  My own post to the rescue!!!!! LOL!  It appears as though for some reason after getting a major update, the versions not matching, and re-installing the SUM, the registry keys for ServiceArg and ImagePath were reset to their default values.

    https://www.sophos.com/en-us/support/knowledgebase/50832.aspx

    >>

    • Replace all example values, with values that reflect your organization.
    1. To immediately affect the service:
      1. Modify the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sophos Message Router\ImagePath
        to the following (all one line):

        "C:\Program Files\Sophos\Remote Management System\RouterNT.exe" -service -name Router -ORBDottedDecimalAddresses 0 -ORBListenEndpoints iiop://:8193/ssl_port=8194&hostname_in_ior=MR.domain.com
      2. Restart the Message Router service on the message relay.

    2. To make the change persistent when an RMS update/reinstall occurs:
      • Modify the key HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Messaging System\Router\ServiceArgs to the following (all one line):
        -ORBDottedDecimalAddresses 0 -ORBListenEndpoints iiop://:8193/ssl_port=8194&hostname_in_ior=MR.domain.com

    I made the change to both registry keys, but it appears those changes reset when you have to re-install from the primary server's SUM share.

    Either way - clients are updating again.  The world is right again.

    Thanks Christian (and Jak, from my old post!)

    -Adam

    :57333
Reply
  • 0

    Well, after scratching my head enough, and seeing the error: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0.........I knew it sounded all too familiar!!!

    I went through my old posts and found this gem:  /search?q= 41705

    Viola !!!!!  My own post to the rescue!!!!! LOL!  It appears as though for some reason after getting a major update, the versions not matching, and re-installing the SUM, the registry keys for ServiceArg and ImagePath were reset to their default values.

    https://www.sophos.com/en-us/support/knowledgebase/50832.aspx

    >>

    • Replace all example values, with values that reflect your organization.
    1. To immediately affect the service:
      1. Modify the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sophos Message Router\ImagePath
        to the following (all one line):

        "C:\Program Files\Sophos\Remote Management System\RouterNT.exe" -service -name Router -ORBDottedDecimalAddresses 0 -ORBListenEndpoints iiop://:8193/ssl_port=8194&hostname_in_ior=MR.domain.com
      2. Restart the Message Router service on the message relay.

    2. To make the change persistent when an RMS update/reinstall occurs:
      • Modify the key HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Messaging System\Router\ServiceArgs to the following (all one line):
        -ORBDottedDecimalAddresses 0 -ORBListenEndpoints iiop://:8193/ssl_port=8194&hostname_in_ior=MR.domain.com

    I made the change to both registry keys, but it appears those changes reset when you have to re-install from the primary server's SUM share.

    Either way - clients are updating again.  The world is right again.

    Thanks Christian (and Jak, from my old post!)

    -Adam

    :57333
Children
No Data
Unfiltered HTML