C Troubleshooting

C.1 Recovering from an mSync Failure

To recover from an mSync failure:

1. Delete the Oracle folder within the Device Memory folder and from the media card.

2. Restart Mobile Server

3. Re-assign, or re-simulate a new SD card.

4. Restart the device and then re-start Mobile Server.

For issues at runtime, such as unable to login or invalid login credentials, perform the following:

1. Verify that the IDE connection with the mobileadmin user exists in JDeveloper and is a valid connection.

   Note:

   The Mobile Server user name and credentials are specified in the Application Data Publication page of the deployment profile.

2. Verify that the database exists on the device's SD card.

3. Verify that the SD card is connected and mounted on the device or simulator.

C.2 Errors When Testing Value Binding Queries

Issue

JDeveloper generates the following error when you test a value binding query:

SQL Query Error Message: Missing IN or OUT parameter at index:: 1

Solution

This error occurred because you used the incorrect binding style. You can only use the JDBC Positional binding style, which substitutes question mark symbols (?) for the bind parameters names. See also Section 5.3.11, "Adding Bind Variables to View Objects."

C.3 Receiving ActiveSync Connection Error Message on Deployment Log

Issue

The following message is written to the JDeveloper deployment log when:

• The ActiveSync process was killed manually through the Windows Task Manager and then restarted and reconnected.

• ActiveSync crashes, hangs, or encounters other problems.

Connection with ActiveSync could not be established. Ensure that PC-to-device/ emulator connectivity is working correctly. Restarting JDeveloper may restore communications. See the ADF Mobile client documentation on Troubleshooting if problem persists.

Solution

Try the following to address this issue:

1. Restart the Windows Mobile emulator, Device Emulator Manager, and ActiveSync.

2. If you are deploying to a Windows Mobile device, disconnect the device and then reconnect it.

3. If the problem persists, restart JDeveloper.

4. Stop and restart ActiveSync using the asreboot.exe utility.

5. If the problem continues after you restart JDeveloper, then restart the system.

C.4 Windows Mobile 6.0 Limitations

Because of a limit on the amount of memory available to all dynamic link libraries (DLLs) on Windows Mobile 6.0, some components of ADF Mobile client or Oracle Database Lite may fail to load when other DLLs have consumed that memory. If an application fails to start, or a sync action fails with an error message pertaining to a plugin library, it could indicate that this situation has occurred. You can determine whether this has occurred by looking for the following messages in the application logfile:

• oseException(-12044): Could not find plugin library "ospsqlite".

• oracle.adfnmc.java.sql.SQLException: java.sql.SQLException:no SQLite library found

• java.lang.UnsatisfiedLinkError: no eswt-converged.dll in java.library.path

If one of these errors has occurred, first verify that the ADF Mobile client runtime is installed and that Oracle Lite is installed (if you are using it). This situation is indistinguishable from a missing DLL, and these error messages reflect that.

Once the installation is verified, try to free up the memory available to DLLs by stopping other running applications. Use the Running Programs List to stop them (accessed through Settings > System tab > Memory > Running Programs tab) then try the application again.

If the application continues to fail with one of these errors, restart the device and try the application again. If it continues to fail, check the Running Programs list to stop any applications that may have been launched at start-up, and try again.

If it continues to fail, it is possible that applications or utilities are being launched at start-up that do not show themselves in the Running Programs list, and these programs are consuming the memory available to DLLs.

Check the contents of the \Windows\StartUp directory. Nearly all Windows Mobile devices will have a shortcut named poutlook which is used by the built-in Inbox application. Others may be applications installed by cell phone carriers, or utilities that make use of the features of industrial devices. Do not move or delete any of the files here, but if you recognize the application that any of them belong to, and the application is not necessary, you can try uninstalling the application using Settings > System tab > Remove Programs. The device will restart (or you may restart it manually). Then try running the ADF Mobile client application.

If the failure continues to occur, the remaining work-around requires careful attention. You can move items in the StartUp folder to other directories to prevent their execution at start-up, which could adversely affect applications or device functionality that depends on those programs running, but it may free enough memory for the ADF Mobile client application to run.

You can also upgrade the operating system of the device if an upgrade has been made available by the device manufacturer. Windows Mobile 6.1 and later releases do not have this problem, thanks to a large increase in the amount of memory made available to DLLs.

For more information, see the Microsoft Knowledge Base article at: http://support.microsoft.com/kb/326163

C.5 Sync Agent Issues

If you face issues with the sync agent, a hard reset of the device may be required.

C.6 Windows 7 Workarounds

Some workarounds may be required when Developing ADF Mobile client applications in a Windows 7 development environment may require some workarounds:

• '\Program Files (x86)'—On 64-bit editions of Windows 7, 32-bit programs are installed to \Program Files (x86) by default rather than the \Program Files directory. Most components required for ADF Mobile client application development are 32-bit applications, so ensure you use the correct folder when specifying settings and searching for programs to run.

• Run as Administrator— Most common problems can be solved by right-clicking the executable, selecting the Compatibility tab (shown in Figure C-1), and checking Run this program as an administrator.

  Figure C-1 Compatibility Tab

  
  

  This may be necessary for many development components, including JDeveloper. If the executable is a batch file, it may be necessary to open a command prompt as an administrator and run the batch file directly from the command line.

• BlackBerry Remote Debug Server—On 64-bit editions of Windows 7, this application may display an error dialog as shown in Figure C-2 about missing components.

  Figure C-2 Missing Components Error

  
  

  This error occurs when the wrong javaw executable appears earlier in your PATH than the javaw executable from your installed JDK. You can fix this by adjusting your PATH so that the bin subdirectory of your JDK installation appears first in your PATH. Another solution is to install BlackBerry JDE 6 to a non-standard location, outside of Program Files (x86).

• BlackBerry Simulator Not Rendering Correctly—On some configurations, the BlackBerry simulator may not display correctly. Ensure the you are using the latest drivers for your video card. If this does not address the problem, disable or reduce the level of graphics acceleration in the simulator. To do this, from the BlackBerry simulator menu, select View then Graphics Acceleration, and choose a different level than the default as shown in Figure C-3.

  Figure C-3 Adjusting the Graphics Acceleration Level

  
  

• Installing Oracle Lite Mobile Development Kit—It may be necessary to set the environment variable OPATCH_PLATFORM_ID=912 before running the installer.

C.7 SQLite Limitations

SQLite does not allow you to publish an application's data if the application's entity objects have different primary keys but belong to the same table. All entity objects belonging to the same table must have the same primary key (or virtual primary key) structure.

To enable the publication with SQLite:

1. In the Mobile Workbench, remove the existing publication items based on the table in question.

2. In JDeveloper, republish the data.

3. On the device, navigate to the location of the client database (such as \OraCE\sqlite_db\<name>\<name>.db) and then delete this client database file.

4. Re-synchronize.

C.8 Font Usage Limitations

When defining properties for ADF Mobile client UI components, consider the following limitations of font usage:

• If the fontStyle attribute of a component is set to italic, the last character in a text will not be visible. This limitation is present in both Windows Mobile and BlackBerry platforms, and affects all components that display text (for example, Command Button and Output Text).

  Setting the fontFamily attribute to one of the following fonts enhances readability of the italicized text:

  • Verdana

  • Century

  • Times New Roman