Table 8-6 identifies common mobile configuration problems and provides useful troubleshooting information.
Problem |
Try this |
---|---|
Cannot create a personal channel |
Check the global.properties.xml file to make sure the alwaysValidateSession parameter is set to false. See “Global property group”. |
Cannot access mobile application:
|
If you see this message when trying to access an application on a mobile device, check the alwaysValidateSession parameter in the global.properties.xml file. The parameter is probably set to true, but should be set to false to enable personal channels to work. See “Global property group”. |
Cannot use mobile application:
|
This message indicates the M-Business Anywhere client requires one or more database PODs to authenticate mobile applications. See the Unwired Accelerator Installation Guide for POD information. |
Mobile application does not appear on the mobile device |
Verify that:
|
The UA logo does not appear on the BlackBerry device |
Verify that you installed the offline client on the BlackBerry device (or BlackBerry simulator), as described in “Installing the UA offline client”. |
Large applications hang the BlackBerry device |
If applications exceed 128K, they are parsed and sent to the BlackBerry in chunks. If the BlackBerry device does not have enough memory, it cannot handle the reparsing. Check the available and used memory on the BlackBerry device. |
|
Somehow the Unwired Accelerator server and BlackBerry version strings are out of sync. Search the global.properties.xml file for the portal.version property, and make sure it is set to 7.0. See Chapter 9, “Configuring Global Properties” for information. |
On the device simulator, too many applications display after using Sync All to obtain the list of applications (even some that do not have Offline BlackBerry set). |
The BlackBerry device simulator is useful for testing applications during development, but it does need maintenance. On the BlackBerry device, try selecting Delete All from the trackwheel menu, and then use Sync All again. If the problem persists, run the clean.bat script:
|
Copyright © 2005. Sybase Inc. All rights reserved. |