Synchronization problems after ignoring some seq. nos in worklist monitor

[Former Member]

Hi everybody,

some of the work sequence nos. were ending up in error because the batch job was getting terminated because of some other ABAP error. So I tried to ignore these sequence numbers and tried synchronizing again. And I am getting the following error.

******************************************************************************************

Home

Synchronization Log

• Synchronization started

• Connection set up (without proxy) to: http://<server>:<port>/meSync/servlet/meSync?~sysid=xxx&;

• Successfully connected with server.

• Processing of inbound data began.

• Skip container with ID ________________________________ because container has wrong sequence number XY1 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XY2 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XY3 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XY4 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XY5 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XY6 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XY7 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XY8 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XY9 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XZ0 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XZ1 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XZ2 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XZ3 (expected XY0); contact your administrator

• Skip container with ID ________________________________ because container has wrong sequence number XZ4 (expected XY0); contact your administrator

****************************************************************************************************

thanks

Bala

[AjithC]

Hi Bala,

The root cause is that you ignored some outbound worklists which has not been sent to the device.. Its always risky to ignore outbound worklists and its should be done only in special cases. But you can ignore inbound worklists if required.

Now there is no easy way to come up from this problem. If you are using SP20 client, a client data reset will solve the problem. Oterwise its better to have a fresh client installation. ( I hope you are not in a productive mode so that there is no need of device recovery. There is a way to recover, but quite cumbersome)

Regards

Ajith