RXOP

Dear RIDP Team,

This is a follow-up regarding the issue reported at the following link:
https://ricoh-ridp.com/ridp/support-system/incident/ricoh-sdc-canada/1743448107/378611250/5452

Summary:
Our Unified Client (UC) software has encountered a critical issue: after a period of usage, it becomes unable to update or create folders/files in the application directory until the device is rebooted.  A large number of error messages are observed, typically in the following format:

System.out: java.io.FileNotFoundException: /mnt/hdd/com.nuance.ndi.neuf.ricohsmartsdk/9254P104007/workflowFolderList.cache: open failed: EROFS (Read-only file system) 

Details:

• So far, this issue appears limited to the IM370 model. Among multiple IM370 devices, only some are affected while others operate without any such issue.

• We’ve added additional logging to investigate the root cause and have also attempted to write to an alternative directory, such as:
  /mnt/hdd/com.nuance.ndi.neuf.ricohsmartsdk/FallBackScanFiles/
  However, during the fault state, even operations like creating folders consistently fail, indicating that the file system is entirely locked against write access.

• Based on our research, the error EROFS (Read-only file system) typically occurs when the system temporarily enters a read-only state, preventing any write operations to the disk.

We are attaching device logs from the affected devices for your review.

Request:
Could the Core Team please investigate the root cause and provide any available workaround or corrective actions?
 

Hi RiDP support,

We got error reboot -- STATE_REBOOT_ERROR Failed to reboot device when using RXOP to reboot device.

ip: TEE1001

Device IM C5510

FW = 1.08.1

We attached machine log.

Please advise.

Thanks.

Hi RiDP support,

We would like to get or set this SP value:

USER_AUTHENTICATION__BROWSER (value 1)

and get this error:

ERROR - POST ERROR, detail Information : ResponseEntityProxy{[Content-Type: text/html;charset=iso-8859-1,Content-Length: 467,Chunked: false]}

We think our acl file have not  USER_AUTHENTICATION__BROWSER permission.

I attached machine logs and rxsp log.

Please help to check this.

I yes, please see our acl request in this incident Request document that explain details about User and Administrator settings | Ricoh Developer Program (RiDP) https://ricoh-ridp.com/ridp/support-system/incident/ricoh-sdc-canada/1640105134/174677702/4400 and add new USER_AUTHENTICATION__BROWSER permission to exist acl file in that acl request.

Thanks.

Hi RiDP support,

We would like to know which device model support these SP settings:

ServiceProgram.OPTIONAL_COUNTER_TYPE__DEFAULT_OPTIONAL_COUNTER_TYPE - ".5113.1",
ServiceProgram.OPTIONAL_COUNTER_TYPE__EXTERNAL_OPTIONAL_COUNTER_TYPE - ".5113.2"

We cannot set those SP settings on IM C 320 device.

Please advise.

Thanks.

Hi RiDP support,

We got this error:

"The exception when call https://192.168.37.130:443/rws/sop/dsdk/InstallServlet, java.net.SocketException: Connection reset by peer: socket write error"

when using RXOP to install application.

Device IM C320

rxinst log and machine log are attached.

Please advise.

Thanks.

Hi RiDP support.

We would like to use RXOP to set that the application do not open at start up  (the application will not be started until the user press the application icon) and display native apps on the screen without login.

Please advise.

Thanks.

On the Ricoh 320 series of MFDs (That come with the internal eMMC memory), they have found out that if they enable encryption on the internal eMMC memory without a SSD installed, then the following symptoms occur.

Use RXOP to install application to the device, get application info got this error:

ricoh.rxop.rxcommon.RxopException: -- init -- Device not reachable.
    at ricoh.rxop.rxinst.RicohJavaDevice.i(RicohJavaDevice.java)
    at ricoh.rxop.rxinst.RicohJavaDevice.f(RicohJavaDevice.java)
    at ricoh.rxop.rxinst.RicohJavaDevice.access$000(RicohJavaDevice.java)
    at ricoh.rxop.rxinst.am.run(am.java)
    at ricoh.rxop.rxinst.bC.run(bC.java)
    at java.lang.Thread.run(Thread.java:750)
Caused by: ricoh.rxop.rxinst.f: HTTP Exception, status 404 404
    at ricoh.rxop.rxinst.RicohJavaDevice.e(RicohJavaDevice.java)
    at ricoh.rxop.rxinst.RicohJavaDevice.j(RicohJavaDevice.java)

If they install a external SSD to the device, then encrypt that drive, this does not happen.

Machine log is attached.

Please advise.

We are encountering an issue with the Reboot API call on our G3 Device (IM C2510), as highlighted in the attached code snippet. Our application utilizes only one instance of RicohJavaDevice, and we would like to understand the possible reasons for this API call failure.

Used RXOP Version : v3.8.8

For further analysis, we have attached the following:

• Machine logs (ZIP file)
• Application-side logs
• Sample code snippet from our application

We appreciate your support in identifying the root cause and potential resolution. Please let us know if you require any additional details.

        public Boolean call() {
            try {
                listener.listenLogs("Rebooting Device, this may take a few minutes...");
                RicohJavaDevice ricohJavaDevice = RicohJavaDevice.CreateDevice(deviceProperties.getIPAddress(), null, deviceProperties.getUserName(), deviceProperties.getPassword(), null, null);
                ricohJavaDevice.setRebootBoth(true);
                ricohJavaDevice.reboot();
                listener.listenLogs("Reboot completed successfully.");
            } catch (RxopException e) {
                listener.listenLogs("Failed to Reboot the MFP \n" + e.getMessage());
                return false;
            }
            return true;
        }

Summary of Issue:

Our client, Ricoh Belgium, is using Capture and Send with PCC5.3 on a large deployment (over 600 devices) at FOD SPF Finances Services.

Issue:
IM 370 devices crash upon scan completion (please refer to the attached clip). Once this happens, no scans are possible until the device is rebooted.

• Only IM 370 is affected, while IMC4500 is not.

Our Analysis:

1. We tested the IM2500, and it is not affected. It seems that only the IM 370 is experiencing this issue.
2. The root cause is still unclear. The ScanGUI screen shows 97% remaining memory before the scan fails, whereas successful scans typically show 100%.
3. The customer's SmartScanEx software on the affected devices is running version 3.0, while the RicohUC package is compatible with versions 1.0 and 1.06.
   • This may cause compatibility issues, as referenced in a previous ticket:
     Ticket Reference.

Could you please help analyze the device logs to determine the root cause of the SmartScanEx issue?
The affected devices are running SmartScanEx v3.0.

Notes for attachments: I scanned on device Ricoh-370-9253PA01174 (IP 10.103.90.64) at 11:57:31 and at 11:58:47.