Traveler Error 12

HCL Domino Domino Forum
1

I have a user who is getting the following error: “Error(12): Sync completed with errors. Device is up-to-date as of 8/16/2008 at 5:29 PM.”

Does anyone know what this means? This is what is in the NTSErrors.log:

[08/26 10:32:40.235] SEVERE DS-234[/6Ur7AAA] CN=Norman Clark/OU=Corporate/O=JBHunt TSSSync.receiveMap#4909 Exception Thrown: java.lang.NumberFormatException: For input string: “800001eb-0”

java.lang.NumberFormatException: For input string: “800001eb-0”

at java.lang.NumberFormatException.forInputString(NumberFormatException.java:63)

at java.lang.Long.parseLong(Long.java:427)

at java.lang.Long.parseLong(Long.java:476)

at com.lotus.sync.TSS.TSSDataTypes.RecordID.<init>(RecordID.java:50)

at com.lotus.sync.TSS.SyncMLServer.tss.TSSSync.uriToGUDRecordID(TSSSync.java:4768)

at com.lotus.sync.TSS.SyncMLServer.tss.TSSSync.receiveMap(TSSSync.java:4829)

at com.lotus.sync.TSS.SyncMLServer.protocol.syncml.ds.server.RequestHandler.handleMap(RequestHandler.java:91)

at com.lotus.sync.TSS.SyncMLServer.protocol.syncml.ds.RequestHandlerDS.handleBodyCmd(RequestHandlerDS.java:259)

at com.lotus.sync.TSS.SyncMLServer.protocol.syncml.RequestHandlerCommon.handleBody(RequestHandlerCommon.java:1213)

at com.lotus.sync.TSS.SyncMLServer.protocol.syncml.RequestHandlerCommon.handleRequest(RequestHandlerCommon.java:119)

at com.lotus.sync.TSS.SyncMLServer.protocol.syncml.SyncServletCommon.handleRequestBody(SyncServletCommon.java:597)

at com.lotus.sync.TSS.SyncMLServer.tss.TSSServlet.handleRequestBody(TSSServlet.java:241)

at com.lotus.sync.TSS.SyncMLServer.protocol.syncml.SyncServletCommon.handleRequest(SyncServletCommon.java:575)

at com.lotus.sync.TSS.SyncMLServer.tss.TSSServlet.handleRequest(TSSServlet.java:190)

at com.lotus.sync.TSS.SyncMLServer.protocol.syncml.SyncServletCommon$1.run(SyncServletCommon.java:190)

at com.lotus.sync.util.ThreadPoolThread.run(ThreadPoolThread.java:266)
2

Subject: RE: Traveler Error 12

The error 12 is being caused by some general failure in the sync.

In this case, you can see the error on the server which would cause the error code to be sent to the device which will report the error (code 12).

What is odd is that the server is trying to parse the 800001eb-0 as a number instead of a string. There is a function to determine whether or not it is a number, and it must be returning true in this case when in fact this is not a number (because of the ‘-’). I wrote a simple test program to test that, but the test program does not fail.

What this means to the user (the device) is that some item on the device is not properly known to the server and therefore cannot be updated by the server. And, the device will probably continue to try and send this to the server which will continue to get the error. To possibly get around this, you could do a Tools - Replace Data for the application that is having the problem (I can’t tell from the log snippet which application it is, but the SyncML logs or other entries in the Activity log should give you a hint). Doing this will remove all the data for that application on the device and send a new copy from the Domino server to the device. By doing this, the client might change that number/string to something that doesn’t cause the error.

If that doesn’t work and to get it fixed for real, you will need to open a PMR. To do that, you will need to set the logging to FINEST (at least for that use) on the server and create a problem report on the device.

3

Subject: Bad Task

Thanks, the Replace Data fixed the problem. It appears that he had a Task that was causing the issues.