SDK/J

Hello,

Customer has reported scan hanging issue on a Ricoh MP 7503 that was moved to a new location, replacing a Ricoh device that had fallen off lease. They rebooted and power-cycled the device, still with no success. They also had Ricoh come out to update firmware, but they are seeing the same thing.

When the scan is started on the device, a spinning icon can be seen and the device has to be power cycled to resolve the hang.

I have attached the logs retrieved from the device. 

Regards

Niranjini

Hi there! 

One of our customer-facing issues is that our Ricoh iMFP application is installed on the Ricoh IM C300. Whenever the device goes to sleep mode, after waking up it shows the device please wait screen. To make it work again need to reboot the printer again. We tried to debug it with our application but could not find what could cause this issue.

Please find the attachment. 

We are attaching the screen recording of the device were tried to wake the printer but it shows please wait for the screen continuously. We have collected the Device information logs from this device. Could you please look into these logs and let us know if something is broken on the device? 

Thank you!

I tried to sign the application with demo SDK/J signature request. So far it error out.

The customer has performed the steps that Jade and Brent were able to successfully do in the lab but was unable to get their devices working. There has been an escalation requested for Brent and Jade to do this testing in the Ricoh lab with RightFax 16.6 and the browser option removed from the MP2554 tomorrow to find a solution for the customer.

Please include me scollins@opentext.com along with jadec@opentext.com on any correspondence about this ticket.

Brent, if you could email me and Jade to let us know when you'd be available for testing tomorrow, I'd greatly appreciate it.

mstover 2/28/23: Customer has decided to use an old server with their old devices until they upgrade.

A customer that was previously using version RightFax 16.4 with Ricoh SDK/J integration is attempting to update to version 16.6. All attempts to install using RXOP have failed with the following error. SDK/J not found.

Working with the customer, we asked them to update their firmware to the most recent version and now their device is behaving as if the old sdk/j url is not found:

   "http(s):deviceipaddress/DH/devicemanagement" returns 404 not found

We have always used this endpoint to determine if the device uses SDK/J

We have a model MP C3003 device in house and we updated the firmware on that device as well to veriffy the behavior and we are seeing the same result. After the firmware update, the old endpoint for SDK/J is no longer supported.

Hoping you can verify that this behavior is or is not expected and how to proceed thanks. I will attach a snapshot of the current version and detailed message we were receiving from rxop before the firmware upgrade.

please production sign the rxspServlet 3.8.8

Hello,

A client of ours is having issues with our SDK/J application when attempting to retrieve the current user using AAA. The error I am seeing in the log is "aaa-client could not register with authentication provider" followed by a "org.apache.commons.httpclient.HttpException: AAA: invoke("register",...) failed: Connection refused" error.

I have attached the full log, error occurs Jun 1, 2022 8:38:29 AM.

This is on a IM C4500, using PCC4 by Equitrac as AAA provider. According to the customer, they are only having this issue on some of their machines and it works on other devices. 

Do you have any ideas for troubleshooting this issue? Is there a simple way to test AAA from outside our application?

Our SDK/J application has not been updated in years and still uses version 1.1.1 of the AAA client, could this be the cause of this issue?

Thanks,

Peter

Hi Team,

Please find the attached zip,

We have updated the RXOP libraries with the latest version i.e v3.8.7 and the version from 1.5.10 to 1.5.11 in our Pharos iMFP solution. Let us know if anything else is required from our end. 

Thanks!

Hi Team, 

We are using the demo signature link i.e the demo signing servlet to generate 14 days signed bundles. We are facing the following error in device logs. 

[SDK_P_XLETM]statechange exception === [stderr] java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
[stderr] 	at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:265)
[stderr] 	at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:220)
[stderr] 	at java.util.jar.JarVerifier.processEntry(JarVerifier.java:288)
[stderr] 	at java.util.jar.JarVerifier.update(JarVerifier.java:199)
[stderr] 	at java.util.jar.JarFile.initializeVerifier(JarFile.java:327)
[stderr] 	at java.util.jar.JarFile.getInputStream(JarFile.java:395)

We checked the production build logs and compared with 14 days of signed bundles, we found that this is coming with demo signature bundles only.

We have attached the screenshot and logs. Let us know what we need to do here on our end.

Thanks!