Skip to Content
0
Apr 13, 2007 at 07:40 AM

Replication doesn't work after resetting the client

15 Views

Hi again,

I found these messages in the trace log and no data is replicated. Anyone able to help?

Regards,

Florian

Trace log:

[20070413 07:25:40:312] E [AppLog/MI/Sync ] Skip container with ID DF76537B7C2F684EA4ECFFB0C4A7822B because container has wrong sequence number 661 (expected 533)

[20070413 07:25:40:328] E [AppLog/MI/Sync ] Skip container with ID 7A2C916A7C0DE24F9F1790B185CFC02B because container has wrong sequence number 662 (expected 533)

[20070413 07:25:40:515] E [AppLog/MI/Sync ] Skip container with ID 8C16DEBB203F1C49AA34D0E427E9C21E because container has wrong sequence number 663 (expected 533)

[20070413 07:25:40:609] E [AppLog/MI/Sync ] Skip container with ID 89D71FF98757A248932B3B2278A45A2C because container has wrong sequence number 664 (expected 533)

[20070413 07:25:40:703] E [AppLog/MI/Sync ] Skip container with ID 5008794F783B1348A9DD394A7E580F7F because container has wrong sequence number 665 (expected 533)

[20070413 07:25:40:796] E [AppLog/MI/Sync ] Skip container with ID DA6F3A18A0469142ADF7E542100D8192 because container has wrong sequence number 666 (expected 533)

[20070413 07:25:40:890] E [AppLog/MI/Sync ] Skip container with ID D3002CD11E6CFA41A11A0C1D129D644C because container has wrong sequence number 667 (expected 533)

.......

[20070413 07:29:37:312] E [Unknown ]

[20070413 07:29:37:312] E [Unknown ]

.....