Error Codes and Exceptions

RXOP v3.8.9 has resolved the issue reported below.

Description of Symptoms

There are reports of a previously working RXOP application throwing a java.lang.SecurityException (wrapped inside a ricoh.rxop.rxcommon.RxopException) and failing to connect to a remote device.

The stacktrace will look something like this:

What types of logs are shown of Ricoh Log Analyzing tool?

The debug messages shown by Log Analyzer Tool are info, warning, and error. For debugging purposes, we suggest using information messages.

Log.i(String, String) – Information

Please adjust your application log messages accordingly when debugging and using Log Analyzer Tool.

From Android guidelines:

Why my development signatures are not working with G2.5 devices?

The initial firmware release for G2.5 devices did not include support for Development signatures when installed via RXOP or WIM. This issue has been corrected in the latest versions of device’s firmware. Note that Demo and production signatures were not affected by this limitation.

If using RXOP for deployment. A common error message seen when encountering this issue with Development signatures is the following:

An Error-71 can occur when you try to uninstall a pre-installed application (e.g. "Copy", "Scanner", "Fax", ... ).  On the G2.5, the Ricoh ScanGUI Service is also considered a native application, so attempting to uninstall this would result in an Error-71.

Error Name:

Operation panel Flair communication error (Smart Operation Panel)

Error Condition:

This SC is issued only for the machine that has the Smart Operation Panel installed
-> Communication between Smart Operation Panel and main machine (this is called "Flair communication") is not sent to Smart Operation Panel.
-> SP setting (SP5-748-201) for Smart Operation Panel is not activated.

Major Cause:

The SC error is caused by the tracking that is set on the device:
 

Although the resource CD states that a J204 error is free space deficiency in SD card, File copy failed.  Please refer to sdkj_userguide_e208.pdf page 28.  A J204 can mean that during start up the application goes into its first life cycle and cannot process it in the allocated amount of time that the platform allows. 

From RXOP 3.3+ the device looking feature was introduced and an operation may fail if RXOP is not able to lock the device to perform the remote operation.

One reason for failure can be due to SSL being turned on on the device. The locking feature was implemented because of the need for locking a device when updating an application during times when customers are accessing the devices.

So if this doesn't really pertain to your customers environment you can disable this feature with a call to: --lock-off In the code.

e.g.:

According to the documentation a J801 error means "try uninstallation later".  

One known method to resolve this error is to set the application to not auto-start and reboot the device.  Once the device is rebooted, the application will be in a stopped state and you will be able to proceed with the uninstallation. 

According to our documentation (sdkj_userguide_eRxxx.pdf, around page 16), a J522 error is an extended feature startup failed problem. In this case, most of the time, a problem is in the life cycle method initXlet().  Some things to keep in mind are the execution time of the life cycle methods.  If the application takes longer than specified by the specification to execute errors like J522 may occur.