Siebel Store-and-Forward Messaging Guide for Handheld > Installation and Configuration of Siebel Store-and-Forward Messaging > Troubleshooting Store-and-Forward Messaging Setup and Configuration >

Siebel Store-and-Forward Messaging Client-Side Common Error Messages


Some common client-side error messages, and their solutions, are described in Table 10.

Table 10. Client-Side Common Error Messages
Symptom/Error Message
Diagnostic Steps/Cause
Solution

Unable to initialize Wireless Messaging. Cannot connect to the server. Please ensure that you have an active connection and try again.

Verify that the device has an active network connection.

  • Start a Pocket Internet Explorer on the device.
  • Check whether the Pocket Internet Explorer can access a server URL, such as the following:

    http://[hostname]/service_enu/s.swe

Also, a network connection by way of an ActiveSync session may have domain name resolution issues.

To resolve a network connection domain name, use a name that is resolvable from the ActiveSync host computer.

If the MQeServerAddr contains points (for example, 10.11.12.13 or sfm.mycomp.com), then add an exception to the PDA connection settings. For more information, see Adding an Exception to the PDA Connection Settings.

Wireless Messaging registration is pending. Would you like to continue to wait for server confirmation.

The device can send the first registration message to the server queue manager. However, the Siebel server cannot receive the message from the inbound queues, generate a response message, and send the response message back to the Siebel Handheld application.

Review the server-side troubleshooting check list to see whether an error is recorded in the log files. See Siebel Store-and-Forward Messaging Server-Side Troubleshooting Checklist.

Unable to Initialize Wireless Messaging Timed Out while waiting for registration response from the server. Please try again or contact your system administrator.

If SFM device registration fails, the application will prompt for a retry.

Retry the synchronization, then wait 10 seconds for the acknowledgement message.

If no acknowledgement arrives, the application asks whether to wait. Do one of the following:

  • Tap Yes.

    The system waits another 10 seconds and prompts again. The maximum wait time is 10 minutes.

  • Tap No.

    The system displays an error message and completes the synchronization.

Siebel Store-and-Forward Messaging Guide for Handheld Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.