Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 11 replies
  • Subscribers 1 subscriber
  • Views 21044 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

Client not getting certificate via RMS "Caught CORBA system exception"

asester

Hey all,

I've got multiple clients that are getting this error in the router log.....and I used the same install package that some of my other clients are using and ARE reporting to the SEC via the message relay.  I am able to telnet to the message relay from the client using 8192 (which returns the IOR with a sequence of numbers) and 8194 (returns a blank screen with a cursor).  I am aware that the Auto Update and RMS services run separate, but I thought I should mention that all of the clients update just fine from the message relay.

I have been reading multiple cases but haven't really seen any concrete resolutions to this issue...and since my problem is sporatic I'm making a new thread.  The 'netstat -n' command I ran on the message relay shows the 8192 ports with the client IP's that I'm having issues with in TIME_WAIT status.

Here is an insert from the router log on the client I'm having issues with.

16.07.2013 15:29:13 050C I Successfully validated parent router's IOR
16.07.2013 15:29:13 050C I Accessing parent
16.07.2013 15:29:18 09A4 I Logged on Agent for certification
16.07.2013 15:29:18 0A30 I Routing to parent: id=03E5AD1E, origin=Router$rv20009056:27138.Agent, dest=CM, type=Certification.CertRequest
16.07.2013 15:30:58 050C E ParentLogon::RegisterParent: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
OMG minor code (2), described as '*unknown description*', completed = NO
 
16.07.2013 15:31:28 050C I Getting parent router IOR from 165.201.22.33:8192
16.07.2013 15:31:28 050C I Received parent router's IOR: (number way too long to paste...and shouldn't matter since it matches)

16.07.2013 15:31:28 050C I Successfully validated parent router's IOR
16.07.2013 15:31:28 050C I Accessing parent
16.07.2013 15:31:50 050C E ParentLogon::RegisterParent: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
OMG minor code (2), described as '*unknown description*', completed = NO

etc etc....The log repeats those steps and never obtains the certification request.

Any suggestions?

Thanks,

Adam

:41705


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

    Heh, well I resolved my own issue.  All in all - I had to uninstall the SUM on the RMS and re-install it to get the version to match.  Once I did that the end points still were not communicating to the SEC.  I then went through and changed the ServiceArgs and ImagePath registry entries which was the solution. 

    It appears that if you run the ClientMRInit.exe file on the RMS server it changes the ServiceArgs registry entry back to the default value and dropped the -ORBDottedDecimalAddresses 0 and the &hostname_in_ior=xyz.com additions...and I ran that test on my RMS on the 16th when I was initially having communication issues.  Apparently the update for the SUM software didn't like the default values and decided to stop talking to the SEC.  Anywho - hope this helps anyone else in the future.

    :42111
Reply
  • 0

    Heh, well I resolved my own issue.  All in all - I had to uninstall the SUM on the RMS and re-install it to get the version to match.  Once I did that the end points still were not communicating to the SEC.  I then went through and changed the ServiceArgs and ImagePath registry entries which was the solution. 

    It appears that if you run the ClientMRInit.exe file on the RMS server it changes the ServiceArgs registry entry back to the default value and dropped the -ORBDottedDecimalAddresses 0 and the &hostname_in_ior=xyz.com additions...and I ran that test on my RMS on the 16th when I was initially having communication issues.  Apparently the update for the SUM software didn't like the default values and decided to stop talking to the SEC.  Anywho - hope this helps anyone else in the future.

    :42111
Children
No Data