Synchronization failed

Unanswered Question
Nov 2nd, 2008
User Badges:

"Synchronization failed because the LastUpdateKey on sideB is not present in the sideA Config Message Log.

The sideB Logger cannot come online duplexed because its database is out of date."

Please help we are not getting any reports and still logger is not writting

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
david.macias Sun, 11/02/2008 - 05:51
User Badges:
  • Blue, 1500 points or more

You've lost synchronization between both sides. Assuming you just didn't upgrade one side and forgot to upgrade the other, just do a database backup and restore the other side and you should be good to go.


Riccardo Bua Tue, 01/20/2009 - 08:41
User Badges:
  • Cisco Employee,

Hola Claudio,

you need to use ICMDBA select the working logger as a source and the failing as the receiver and do a synch.



Hi Riccardo!

Thank you, your suggestions are the solution to the issue i was on. I think this is a time issue where time zones or clocks of both sides are not syncronized, and if you change the system timezone or clock causes the database from the loggers to be desyncronized.

Again thank you and regards.,


blackz88mobile Tue, 01/20/2009 - 08:19
User Badges:

Having not far from same problem - logger says that dbnextrow failed :-( any suggestions?

(Distributor process configlogger) -

connecting to database is okay then

Logger waiting for AW init to initialize the AW database... then

dbnextrow failed 5 times


db init procedure also failed if manual operation selected...

Riccardo Bua Tue, 01/20/2009 - 08:42
User Badges:
  • Cisco Employee,


this is most likely a DB corruption, select the AWDB in ICMDBA, do a recreate, once the recreate is completed do a manual AW init, this should fix it.




This Discussion