Error messages: BlackBerry Java Application tasks
- BlackBerry Policy Service log files from the day the issue was reported (log level 4 recommended)
- BlackBerry Dispatcher log files from the day the issue was reported (log level 4 recommended)
- BlackBerry Administration Service log files from the day the issue was reported (log level 4 recommended)
- BlackBerry device information (for example, the BlackBerry device model, BlackBerry Device Software version, wireless service provider, IT policy assigned to the BlackBerry device, service books on the BlackBerry device, and so on)
- event log of the BlackBerry device from the day the issue was reported
- BlackBerry Policy Service log files from the day the issue was reported (log level 6 recommended)
- system event logs
- copy of the BlackBerry Configuration Database
- SQL trace of the BlackBerry Policy Service that communicates with the BlackBerry Configuration Database
For information about changing the log level for a BlackBerry Enterprise Server component, visit www.blackberry.com/support to read article KB04342. For information about obtaining the event log for a BlackBerry device, visit www.blackberry.com/support to read article KB05349.
If the recommended administrative action for an error message does not resolve the issue, contact RIM Technical Support.
- Sequence Processing Stopped due to error processing SEND_APC_APP command
- The BlackBerry Policy Service
sends application data to a BlackBerry device as a group of application modules. If the BlackBerry Policy Service
does not deliver one of the application modules to the BlackBerry device, the remaining application modules are not delivered to the BlackBerry device.
You can try to resend the BlackBerry Java Application to the BlackBerry device.
- SendApp failed due to error getting application data, processing stopped
- An error occurred when the BlackBerry Policy Service
tried to retrieve the data that it required to install the BlackBerry Java Application.
You can verify that the BlackBerry Policy Service can access the network share that you use to store the application files.
- QueueModule failed, processing stopped
- An error occurred when the BlackBerry Policy Service
tried to process the application modules and send the application modules to the BlackBerry device.
You can verify that the BlackBerry Policy Service can access the network share that stores the application files.
- Device timed out waiting for module
- The BlackBerry device reported a timeout failure while waiting for the application modules.
You can resend the BlackBerry Java Application to the BlackBerry device. If the second attempt to install the BlackBerry Java Application is not successful, in the log files that you collected, locate the user account that experienced the issue. Trace the installation activity.
- Device reported insufficient memory to install module
- The BlackBerry device does not have enough application memory available to install the application modules.
You can instruct the user to make more application memory available on the BlackBerry device. Resend the BlackBerry Java Application.
- Device reported insufficient privileges to install module
- The BlackBerry device does not have the necessary permissions to install the BlackBerry Java Application.
You can verify that the BlackBerry device is configured with the necessary permissions to install a BlackBerry Java Application. Resend the BlackBerry Java Application.
- Device reported invalid version in packet, supported version is %s
- The BlackBerry Java Application is not compatible with the BlackBerry Device Software
version that is running on the BlackBerry device.
You can verify that the BlackBerry Java Application is compatible with the BlackBerry Device Software version that is running on the BlackBerry device.
- Device reported Data Format Error in packet while installing module
- An error occurred in the BlackBerry Policy Service
that prevented the BlackBerry device from installing the BlackBerry Java Application.
In the log files that you collected, locate the user account that experienced the issue. Trace the installation activity.
- Device reported a %s error while installing module
- Device reported a general failure installing the module
- Device reported a security violation while installing the application
- Device reported insufficient app data while installing module
- Device reported insufficient body data while installing module
- Device reported invalid app data length while installing module
- Device reported invalid command while installing module
- Device reported invalid module hash while installing module
- Device reported that the module save failed
- Device reported that there was an incomplete module
- The BlackBerry device identified a formatting error in the application data before or during the installation process.
You can verify that the application files are formatted properly and try to send the BlackBerry Java Application to the BlackBerry device again. If your second try at the installation is not successful, in the log files that you collected, locate the user account that experienced the issue. Trace the installation activity.
- Incomplete ACK data for APPD request
- The BlackBerry Policy Service did not receive an acknowledgment
message from a BlackBerry device that indicates that the BlackBerry Java Application was installed.
You can verify that the BlackBerry device is turned on and is located in a wireless coverage area. Resend the BlackBerry Java Application.
- For the command: %s Device reported a general failure
- For the command: %s Device reported non command handler for request
- For the command: %s Device reported security violation
- For the command: %s Device reported unable to decrypt
- For the command: %s Device reported key mismatch
- For the command: %s Device reported unsupported command version
- For the command: %s Device reported code base error
- For the command: %s Device reported a general failure installing the module
- The BlackBerry device cannot execute the command to install or update the BlackBerry Java Application.
In the log files that you collected, locate the user account that experienced the issue. Trace the installation activity.