Identify and resolve server-side issues while debugging the application.
Problems on the Unwired Server side may cause device client problems:
- The domain or package does not exist. If you create a new domain, with a default status of disabled, it is unavailable until enabled.
- Authentication failed for the application user credentials.
- The operation role check failed for the synchronizing user.
- Back-end authentication failed.
- An operation failed on the remote, replication database back end, for example, a table or foreign key does not exist.
- An operation failed on the Web Service, REST, or SAP® back end.
To find out more information on the Unwired Server side:
-
Check the Unwired Server log files.
- For message-based synchronization mode, you can set the log level to DEBUG to obtain detailed information in the log files:
- Set the log level using Sybase Control Center. See Sybase Control Center for Unwired Platform > Administer > Server Log > Configuring Server Log Setting.
Note: Return to INFO mode as soon as possible, since DEBUG mode can affect system performance.
- Obtain DEBUG information for a specific device:
- In the SCC administration console:
- Set the DEBUG level to a higher value for a specified device:
- In SCC, select Application Connections, then select .
- Set the Debug Trace Level value.
- Set the TRACE file size to be greater than 50KB.
- View the trace file through SCC.
- Check the <server_install_folder>\UnwiredPlatform\Servers
\MessagingServer\Data\ClientTrace directory to see the mobile device client log files for information about a specific device.
Note: Return to INFO mode as soon as possible, since DEBUG mode can affect system performance.