mWO - Must gather to throubleshoot synchronization errors

Hi

This is the main troubleshooting guide for synchronization issues.

https://wit.ifsworld.com/f1docs/apps10/Foundation1/040_administration/415_touch_apps/010_administration/070_trouble_shooting/default.htm

However some screens or logs may be important depends on where is the issue you are experiencing.

First place you can always check is the mobile device logs in EE. Also you can enable Sync traces for your device to get device Synchronization  traces when you want to get the SQLs behind the entity synchronization.

Hi

We do have troubleshooting guide under F1 Documentation /Administration guide / Tocuh Apps./ Administration.  There is also a synchronization guide placed under Touch Apps as well. 

Regards

Johan 

I know the guide, but in the guide doesn’t explain how to dig in the errors.
For example, i f you have a list of errors like this one:
 

That appears in the transaction log, of course you can see the detail of each one, as for example:

ORA-20110: JtTaskClocking.ISCLOCKEDIN: Ya se ha fichado en la asignación de trabajo 3 de la operación 11154. (There is a time report already for the Work Assigment 3 in Work Task 11154)

ORA-06512: en "IFSAPP.ERROR_SYS", línea 140

ORA-06512: en "IFSAPP.ERROR_SYS", línea 356

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 3472

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 3482

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 3184

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 3189

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 2200

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 2205

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 3651

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 3657

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 2813

ORA-06512: en "IFSAPP.JT_TASK_CLOCKING_API", línea 2829

ORA-06512: en "IFSAPP.MAINT_ENG_APP_SVC", línea 72939

ORA-06512: en "IFSAPP.MAINT_ENG_APP_SVC", línea 72980

ORA-06512: en "IFSAPP.MAINT_ENG_APP_SVC", línea 20396

ORA-06512: en "IFSAPP.MAINT_ENG_APP_SVC", línea 20413

ORA-06512: en línea 2

ERRINV: ORA-20110: JtTaskTransaction.REMOVEWHENNOTREPORTED: Removal of Task Transaction is not allowed in status Transferred.

ORA-06512: at "IFSAPP.ERROR_SYS", line 140

ORA-06512: at "IFSAPP.ERROR_SYS", line 356

ORA-06512: at "IFSAPP.JT_TASK_TRANSACTION_API", line 7098

ORA-06512: at "IFSAPP.JT_TASK_TRANSACTION_API", line 7104

ORA-06512: at "IFSAPP.JT_TASK_TRANSACTION_API", line 6095

ORA-06512: at "IFSAPP.JT_TASK_TRANSACTION_API", line 6102

ORA-06512: at "IFSAPP.JT_TASK_TRANSACTION_A

Then what I am looking for is a must gather procedure or guide to be able to dig on that, something that permits to understand this info, in order to be able to reproduce the problem, that it is the first step to solve it or to open a LCS Case.

Please, have you continue the troubleshooting from Failed transaction detail info?

Ok so you want to troubleshoot Failed Transactions specifically. I provided that page which mainly addressing synchronization issues and troubleshooting in all areas.  

But Failed Transaction is a sub category and need to address based on the error group (below). I think first step is to identify the group of the error. Most of the error in your list look to me as System Data / Transaction Data errors. There is no specific defined way to troubleshoot such business errors as far as I can say. But may be you need to digging to the functional area case by case with the details you have in the FT screen. If it’s a Software error then you need to report it to the relevant product group via LCS. But in other cases it need to be analyzed with it’s own domain area and you may need a LCS case to get support from product experts in relevant area. Hope this clarify the issue.   

Failed Transactions down into four main categories which are:

• System Data Errors
• Transaction Data Errors
• Process Errors
• Software Errors
• Consequential Errors