Mobile device setup

Table 9-7 identifies common mobile configuration problems and provides useful troubleshooting information.

**Table 9-7: Troubleshooting mobile device setup problems**
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: `Your submission has been recorded and will be sent during the next Synchronization`	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”.
Mobile application does not appear on the mobile device	Verify that: The M-Business Anywhere user name/password and server properties are set correctly in M-Business Client. M-Business Clients use M-Business users, not Mobile Web Studio users. See “Configuring M-Business Anywhere” and “M-Business Anywhere accounts”. For BlackBerry devices, make sure the “Make available for disconnected mobile devices” option is selected for the application, and that the application is in a grid format.
JVM error when attempting to load UA client on the BlackBerry device	This problem is typically seen on small memory devices (like the 7230) that only have 16MB of memory, especially when the device is loaded for Chinese language (or multiple European languages) support. To correct the problem: Check the device memory to see whether less than 1.5MB of memory is available. To do so, select Options \| Status. If less than 1.5MB of memory is available, remove some components to free up some memory. Some of the components you can remove are unused Input Methods for Chinese (for devices running Chinese support), or unused European language support (for devices running support for multiple European languages).
The UA client 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.
`Sync has failed Response code returned 0 This UA application cannot be used with server version version.`	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 8.0. See Chapter 10, “Configuring Global Properties” for information.
On the device simulator, too many applications display after using Refresh All to obtain the list of applications (even some that do not have “Make available for disconnected mobile devices” 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 Refresh All again. If the problem persists, run the clean.bat script: Navigate to RIM\BlackBerry JDE 4.x.x\bin. Double-click clean.bat. Navigate to RIM\BlackBerry JDE 4.x.x\simulator. Delete Uaclient.* , Uaframework., and Ualistener.. Copy new Uaclient., Uaframework., and Ualistener.* files into the simulator directory again as described in “Installing the UA offline client”.
Cannot push sync e-mail to BlackBerry device	This could indicate your BES configuration has become corrupt. Check to see how many CMIME service books you have: On the trackwheel menu, select Options \| Service Books. Look for the number of “Desktop [CMME]” entries you see. If there are more than one, use the Delete option on the trackwheel menu to delete all entries. Then sync with your BES again to get the proper CMIME service book back. You can sync by connecting to Database Manager, or running enterprise activation.
Sync activities keep interrupting what you are doing on the BlackBerry or Symbian/J2ME device	If you selected the option to “Sync immediately” when you configured push synchronization, focus changes from what you are doing to the sync process during synchronization. You can choose to ignore the sync request, and retrieve them from the Sync log when it is more convenient. If you are interrupted a lot, you can select one of the other options as described in “Setting up push sync” procedure in “Symbian/J2ME client accounts” or “BlackBerry accounts”.
After pushing an application from the UA server, mobile devices do not receive the mobile application at the same time	Push-sync behavior is influenced by UA server settings, and user settings on their mobile devices. If the user subscribes to the application, settings on the mobile device may require the user to Refresh All to get the updated mobile application. If the user does not subscribe to the application, the Administrator may have to create a version of the application that can be pushed to the user.
Push sync does not appear to update personalized applications for different users at the same time	This is typically due to one of the following: The user who does not receive notification of a push-sync, probably has not performed a sync since the subscription was set to “Y.” Consequently, UA does not have the correct watchers for that user’s version of the application. The user adapter may not be push-enabled, so a user’s version of the application not getting executed. Consequently, change detection never occurs to start the push process.
Message keeps popping up on the Symbian/J2ME device: `HTTPMIDlet wants to send information. This will require the use of airtime which may cost you money. Is this OK? (//wireless.java.sun.com)`	This indicates the mobile device is protected by a security domain, that protects users and software from malicious software. This security requires airtime for which you will be billed. Make your choice from those offered, typically: Yes, always. Don’t ask again. This time. Ask me next time. Not this time. Ask me next time. No. Shut off HTTPMIDlet. See “Symbian/J2ME client security” for more information, and to learn more about MIDP 2.0 security architecture, see Sun Developer Network (SDN).