06-14-2016 12:01 PM
After we upgraded to 2.1 we are now seeing a Replication Failed error. We tried to SYNC the node in question and that did not fix the problem, so we did a un-register the second node and re-register which was successful, but we are now starting to see this error again. Not sure what is actually triggering it.
Replication Failed : Server=ise2; Message=Error synchronizing object: Alarm[null]; Operation: Update
The details box has no other information available.
Thanks,
Sam
Solved! Go to Solution.
09-07-2016 03:31 AM
Chris,
Yes, we opened a TAC case and the error appeared from what TAC found that when clearing our ERS log messages that it increased the replication error counter. They basically stated that even though we saw the replication error that all was being replicated and that it was cosmetic in nature. We basically only see the error when we try to clear other error’s on the main panel.
TAC Case: 680472101
Thanks,
Sam
09-07-2016 12:44 AM
Did you find a solution for your issue ? We have the same behaviour after having upgraded to 2.1. Did you open a TAC case ? If yes, what they told you to do ?
Thanks,
Chris
09-07-2016 03:31 AM
Chris,
Yes, we opened a TAC case and the error appeared from what TAC found that when clearing our ERS log messages that it increased the replication error counter. They basically stated that even though we saw the replication error that all was being replicated and that it was cosmetic in nature. We basically only see the error when we try to clear other error’s on the main panel.
TAC Case: 680472101
Thanks,
Sam
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide