PEGA0066 alert: Mobile App Data-Sync Failure
The PEGA0066 alert is generated when an offline-enabled mobile app that originates from the Pega 7 Platform fails to synchronize its data after reconnecting to the server.
The alert includes several fields that contain detailed information about the failure, the application, and the device:
- Line – A human-readable explanation of the problem, for example: "Client store synchronization failed due to an SQL exception."
- Device Manufacturer – The name of the device's manufacturer, for example "Samsung".
- Device Name – The name of the device, for example "Galaxy S II".
- Device OS Name – The device's operating system: "Android" or "iOS".
- Device OS Version – The operating system version, for example: "6.0".
- Mobile App Container Version – The Hybrid Container version used to build the application.
- Installation ID – A unique Hybrid Container installation identifier.
- Synchronization ID – A synchronization identifier that identifies it on a particular installation.
- Synchronization Timestamp – Additional failed synchronization identifier.
- FailureTimestamp – A time stamp of the moment when all processing related to the synchronization finished.
- Error Code – An information about the possible cause of the error. Possible error codes are listed in the Next steps section of this article.
Default prconfig.xml setting
Use the following setting to define the level of error type filtering.
<env name = “alerts/mobile/PRPCClientStore/synchronizationErrorTypeFilteringMode" value="NONE" />
The setting accepts one of the following values:
- NONE – No issues are logged by the system. This is the default setting.
- ALL_BUT_NETWORK_FAILURES – The system logs all failures reported by the device, except for the ones that relate to network connectivity.
- ALL_FAILURES – The system logs all failures reported by the device.
Stop and restart the server after you change the setting.
Review the information reported in the alert. Compare it with other alerts of the same type to find common characteristics, for example, the operating system version of the device.
Use the contents of the Error Code field to narrow the list of possible causes of a failure. The following table lists error codes and their descriptions.
|1||INTERNAL||The reason could not be identified.|
|2||NETWORK_FAILURE||A device cannot reach the server, for example, the server might be offline, or a network connection might have dropped during the synchronization attempt.|
|3||SERVER_FAILURE||A server failed to process the synchronization request from the device.|
|4||CLIENT_DB_FAILURE||Your data violates a unique key constraint, is too big, or is an incorrect type. Review your large data pages configuration, device logs, and the SQL exception.|
|5||CLIENT_PARSING_FAILURE||The device failed to parse the server response.|
|6||ALREADY_STARTED||A data synchronization process was already running when another attempt was made. If a custom code initiates synchronization, it must check the state of the process before starting a new one.|
|7||NOT_CONFIGURED||An attempt to start or stop synchronization was made before the synchronization was correctly configured. You must configure the synchronization before any custom code initiates the synchronization process.|
|8||AUTHENTICATION_FAILURE||The server did not accept the credentials provided by the device.|
|9||ILLEGAL_ARGUMENTS||The data access method is incorrect.|
|10||SESSION_EXPIRED||The session has expired.|
To find corresponding system logs entries:
- Click to access the Log Files tool.
- Use the entry number from the alert's Correlation ID field to find the system log entry that contains the device log dump files.