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

Additional SUM as message relay and 10.3.13

QC

Anyone else having an issue with RMS on the additional SUM? Our Endpoint subscription was upgraded to 10.3.13 on the evening of April 16th. Today I noticed that the additional SUM hadn't reported since around noon on 17th. Closer inspection showed that the server hadn't sent a message since then and that it hadn't relayed any endpoint messages.

Found that the relay somehow had reverted to an endpoint while at the same time it listed itself as its parent in the registry (ParentAddress). No obvious error in the few logs from around the time of the upgrade, nothing from the time communication apparently stopped, and no indication what and when it had actually messed up the information.    

I've submitted the logs to Support. Anyway I've tried the obvious and set the registry values to those appropriate for a message relay. RMS on the SUM/relay was able to connect, messages started flowing and the backlog has been cleared.

Christian

:56754


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

    Hi Sandy,

    what Support say

    well, the technician and I agreed that the available logs looked normal. No logs from around the communication loss, no indication when the registry keys were "reset" endpoint. As I had it "re-promoted" we decided not to pursue it.

    While I was about to write this reply I did a check on the facts and found a ClientMRInit log in \Windows\SysWOW64 (sic!) from the time of the RMS 3.4 uninstall and this doesn't look correct (and I think the ClientMRInit should have refused to execute anyway). I've followed up on the case with this information ... we'll see.

    Christian 

    :56837
Reply
  • 0

    Hi Sandy,

    what Support say

    well, the technician and I agreed that the available logs looked normal. No logs from around the communication loss, no indication when the registry keys were "reset" endpoint. As I had it "re-promoted" we decided not to pursue it.

    While I was about to write this reply I did a check on the facts and found a ClientMRInit log in \Windows\SysWOW64 (sic!) from the time of the RMS 3.4 uninstall and this doesn't look correct (and I think the ClientMRInit should have refused to execute anyway). I've followed up on the case with this information ... we'll see.

    Christian 

    :56837
Children
No Data