Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 4355 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

Message relay generating CORBA errors in logs after OS rebuild - IDL:omg.org/CORBA/NO_PERMISSION:1.0'

geoff morgan

Hi,

One of our Message relays had to be rebuilt overnight and it now works in a fashion but is generating the following in the Router logs

c:\ProgramData\Sophos\Remote Management System\3\Router\Logs

11:02:10 0968 I Getting parent router IOR from mr.domain.com:8192
21.08.2018 11:02:10 0968 I Received parent router's IOR:
IOR:010000002600000049444c3a536f70686f734d6573736167696e672f4d657373616765526f757465723a3e300000000100000000000000a4000000010102650d00000031302e3234392e302e313531003901204100000014010f004e55500000002100000001000000526f6f74504f41006f7574657250657273697374656e740003000000010000004d657373616765526f757465726f70650300000000000000080000000100a600004f415401000000180000000100a600010001000100000001000105090101000000000014000000080000000100a60086000220
21.08.2018 11:02:10 0968 I Successfully validated parent router's IOR
21.08.2018 11:02:10 0968 I Accessing parent
21.08.2018 11:02:10 0968 E ParentLogon::RegisterParent: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/NO_PERMISSION:1.0'
Unknown vendor minor code id (0), minor code = 0, completed = NO

 

Can anyone point me in the right direction to resolve this issue?

 

Geoff



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to QC

    Hi Christian,

    it works in that it is relaying messages for other endpoints but it is itself showing as disconnected in the SEC.

    The Debug level was one of the first things i did. 

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\Messaging System\Router

    "LogLevel"=dword:00000002

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sophos Message Router

    "C:\Program Files (x86)\Sophos\Remote Management System\RouterNT.exe" -service -name Router -ORBDottedDecimalAddresses 0 -ORBListenEndpoints iiop://:8193/ssl_port=8194&hostname_in_ior='MR FQDN' -ORBDebug -ORBVerboseLogging 2 -ORBDebugLevel 10

     

    I have removed any company specific details from the post.

  • 0 in reply to geoff morgan

    Hello Geoff,

    did you post the verbose log, I can't find it? The snippet in the original post seems to be normal logging.

    it is relaying messages for other endpoints but it is itself showing as disconnected
    this would be strange. I think it would have to register with the parent in order to be able to communicate - though it might be possible that it appears as disconnected but can relay messages.  Does the log show that it is relaying messages?

    Christian

  • 0 in reply to QC

    Hi Christian,

    I am embarrassed to say i have resolved the issue. I stood back and checked each registry and application setting one by one.  I had somehow got the MR using itself as its parent!

    Our SEC and this MR have the same name with the MR having an additional 'R' in its hostname.  Any other MR it would have been obvious from the start..

     

    The machines updating in the console were a red herring regarding this issue and simply confused me. ALL messages are meant to be ultimately go through this MR as its the last in the chain before the SEC so i clearly have another issue with some machines going direct to the SEC,  Harrumph! More work figuring out my predecessors configuration.

     

     

    Thank you for your time and patience.

     

     

    geoff

     

     

     

Unfiltered HTML