Device Clients

Provides troubleshooting information for device application clients. Some topics may apply to device application clients in general, while others may be specific to platform types.

• No Workflow Message is Sent
  Problem: After a new hybrid web container has been installed on a device, attempts to connect the device to Unwired Server or to send a data change notification (DCN) result in an error: No workflow message is sent because no device is found to send the notification.
• Synchronization Fails in a Remote Server Environment
  Problem: Synchronization fails due to an error on the server.
• Synchronization Fails With OutOfMemory Error
  Problem: The device application seems to hang for 15 or 20 minutes, then synchronization fails with a java.lang.OutOfMemoryError or OutOfMemoryError message.
• Timeout Errors During Client Synchronization
  Problem: Various timeout errors are reported during client synchronization, especially in a cluster configuration.
• Device Operation Fails With SQLE_NOT_IMPLEMENTED Error
  Problem: A Windows Mobile or BlackBerry device throws an Exception with the message SQLE_NOT_IMPLEMENTED.
• No Data Displays on Device Client
  Problem: No data displays on an iOS or Windows Mobile device, and no error message displays.
• Synchronizing the Device Application Returns Only One Row of Data
  Problem: If the enterprise back-end database table has no primary key and contains multiple rows of identical information in every column, a device application user can synchronize only one row.
• Packet Dropped State
  Problem: User stops receiving packets for a package subscription and "Packet Dropped" displays as the subscription status for the user and device ID.
• Pattern is Too Long Exception
  Problem: An exception—The pattern is too long—is reported while trying to update an existing value on a back-end database, via mobile device.
• Feature Not Implemented Exception
  Problem: An INSERT operation on the client device results in an exception similar to: Feature 'n/a' not implemented.
• Synchronization Key Rows Must be Unique
  Problem: For device clients connecting to DOE, duplicate usage of synchronization keys on inbound create, read, update, or delete (CRUD) messages from device clients can cause unexpected behavior on the DOE side.
• BlackBerry
  Provides troubleshooting information specifically for BlackBerry device application clients.
• iOS
  Provides troubleshooting information specifically for iOS device application clients.
• Windows Mobile and Windows
  Provides troubleshooting information specifically for Windows Mobile and Windows device application clients.