Skip container with ID XXX because container has wrong sequence number YYY

[Former Member]

Hi guys,

Do you have some idea how this can be fixed without reinstalling the MI client (something in the fashion of deleting/editing /MI/sync/<user>/in|out):

[20071030 16:08:38:589] E [AppLog/MI/Sync ] Skip container with ID 4723BCBBF1943862E10000000AC8702A because container has wrong sequence number 3698 (expected 2468)

[20071030 16:08:38:610] E [AppLog/MI/Sync ] Skip container with ID 472395EAF205386EE10000000AC8702A because container has wrong sequence number 3699 (expected 2468)

[20071030 16:08:38:630] E [AppLog/MI/Sync ] Skip container with ID 4726B96DD92A385AE10000000AC8702A because container has wrong sequence number 3700 (expected 2468)

[20071030 16:08:39:126] E [AppLog/MI/Sync ] Skip container with ID 4723A299F205386BE10000000AC8702A because container has wrong sequence number 3701 (expected 2468)

[20071030 16:08:39:148] E [AppLog/MI/Sync ] Skip container with ID 4723A29AF205386BE10000000AC8702A because container has wrong sequence number 3702 (expected 2468)

[20071030 16:08:39:173] E [AppLog/MI/Sync ] Skip container with ID 4726BF52D92A385AE10000000AC8702A because container has wrong sequence number 3703 (expected 2468)

[20071030 16:10:50:926] E [Unknown ]

[20071030 16:11:01:616] E [Unknown ]

[20071030 16:11:01:626] E [Unknown ]

Thanks in advance!

Best Regards,

Lalo

[Former Member]

Hi Sivakumar,

Actually, we are on SP12, but this SAP Note have been applied as referred by our administrator. And what I've asked our end user was to reset the client and retry again.. And the problem appears again.. What I can see on middleware was that the O-waiting queue have significant number of items, and O-sent stays the same length during synchronisation.. What we adviced was to reinstall MI plus all the stuff.. Anyway, this appears to be an issue for OSS, right..?

Best Regards,

Lalo

[Former Member]

Hi Lalo,

could it be, that you had an item a while ago that was with status ERROR and you set it to ignore? In that case this error you explain happens sometimes. I found out that the only way to easily get rid of that problem is to reinstall the device form scratch.

If you have an item in ERROR state, it is better to change the values and reprocess it so it goes through. Ignore unfortunately does not send the information to the client, that changes the syncstate of the original item on the client from S to G or delets the item there. So this item stays mostly in S state and can not be changed again. There a data reset would help - but a data reset just because of an error on the middleware - well, even this makes no sence. So changing the values on the middleware for an item in state error helps a lot.

Hope this helps to avoid this error in the future and hopefully the developers will find a good way to fix that siieu in the future.

Regards,

Oliver

[Former Member]

The SAP Note was applied, but despite of this the problem described in the thread appears..

[Former Member]

Hi Sivakumar,

We are currently on SP12, so will apply the newest SP13 and if needed will reset the client as well. Appreciate your help!

Best Regards,

Lalo

[Former Member]

Hi Sivakumar,

Thanks for your timely response. Actually, what we did was to reset the client and afterwards on synchronization (initial) these errors were triggered. Resetting the client does it means only the client DB is fully cleaned..? Anyway, I'll take a look over the note, if you have any other ideas they are most than welcome

Best Regards,

Lalo

[Former Member]

Hi,

Yes Reset client means that the contents of DB will be flushed from the client and a fresh download of data will be triggered automatically. What I suggest is first implement the note, and then may be if required perform a client reset (only after the note is implemented on server). Apart from this method, I dont see any other way of solving this issue.

Best Regards

Sivakumar

[Former Member]

Hello Lalo

Kindly implement note 1045612 on the MI Server. If the problem occurs even after implementing this note or if the note has already been implemented in your server, just perform a Client Data Reset using the Reset button available in the Settings page of MI Client. This should solve your problem.

Best Regards

Sivakumar