RXOP

Hi, we're getting an installation error when installing 1.1.7. We're using the ZIP file attached to incident 3501.

This is the exception:

Can you please check the attachment on incident 3501 to see if the signature has expired? 

Thanks,

Nick.

We've been testing our installation software and as part of that we changed the Remote Installation Password. Unfortunately what that was set to has been forgotten and we need to reset this password. We've contacted the local Ricoh support and they've reset the machine as best they can, they've even replaced the NVRam but the password has not reset. Is there any alternative we have other than purchasing a new machine?

RXOP 3.8.0 returns the error "Connection refused" on port 443 when connecting to our C400 and C2500. HTTPS is not set up on these devices, so it should fall back to HTTP. This error does not occur with RXOP 3.7.3.

RXOP 3.8.0 hangs indefinitely when connecting to our 501. This device is set up correctly for both HTTPS and HTTP. This problem does not occur with RXOP 3.7.3. 

I attached the sample code that I've been using to test the RXOP library. Swapping between RXOP 3.7.3 and 3.8.0 jar files is enough to reproduce the problem on our end. The expected command line arguments are IP, username, and password.

How do I get RXOP 3.8.0 to act the same as RXOP 3.7.3 when connecting to these devices?

Regards,
Mike

Hello,

We have a customer that is having trouble deploying our pull print solution to three MP C307 devices.  I am attaching the deployment log, the rxinst log and the trace log.  The trace log is completely empty, so it may not be much help.  It does have the firmware versions in it though.

The main issue is it looks like the device is having trouble accessing the Hdd, which may be causing the device to report back as a "FullNativeSupport" device, when it clearly isn't.

Then, it makes me wonder if I am getting back an empty device trace log because of the issue accessing the Hdd.

Any help is appreciated.

Regards,

Bryan

I updated our solution to use the libraries included in the RxOP 3.8.0 package. When I test the changes I can successfully install RxSP 3.8.0 to the MFP. But setting SP mode values fails. 

Installation of our solution is done in two steps. The first ensures RxSP is installed. If it is, nothing more to do. If it isn't, install it and reboot the MFP. In this case it was already installed as shown in this log:

Hi,

In the attached document, it shows RxOP/RxInst handles detection of the MFP type and pushes the appropriate RxSP package to the MFP. It references RxSP.ZIP which should contain both versions (one for MP and one for IM). I didn't find a ZIP file in any of the recent RxOP release packages (3.7.3 and 3.8.0) but I did find something close in the \roc\roc-ridp-1.6.1\rxop-tools folder. There we see two ZIP files that seem to contain the content implied in the document. these are rxspServlet-3.7.2.zip and rxspservletsop-1.0.zip.

Can you clarify if the document is accurate and if it is, point us to the ZIP file it references? If not, should we be making RxSP.ZIP with the content of rxspServlet-3.7.2.zip and rxspservletsop-1.0.zip? 

If we are to make the ZIP file, I assume it's OK to replace the content with the latest content SDK/J and SmartSDK components from their respective RxOP releases?

If none of this is accurate I'm assuming it's up to us to detect the MFP type and send the appropriate APK or JAR files.

Thanks,

Nick.

We would like to have a new ACL created to support the following new models: Pro 8300S/8310S/8320S, IM 550/600/2702

Hello,

We have a customer experiencing an issue where they have an MP 2555 and are trying to deploy our Pull Print solution.  During our deployment, RXOP is information our deployment application that the device does NOT have a Smart Operation Panel.  According to my documentation, MP 2555 is an Android G2 SOP device.  Is this accurate?

If so, why would the device not be reporting as such?

I am attaching the SMC report (PDF), the deployment log and the rxinst debug log.

Let me know if you need anything else.

Regards,

 Bryan

Hi!

We are unable to configure an IM C2000 device via our installation tool and ROC (our tool was based on ROC 1.6.1).

We were able to initialize the device, but we were unable to configure SP Mode.

We note that when we perform the following settings on the device, they do note persist, returnig to default after reboot.

1. Device Management > Extended Feature Settings > Administrator Tools > Web Installation Settings
2. Device Management > Extended Feature Settings > Administrator Tools > Web Service Settings

Are you awere of this situation with the new devices? How shall we proceed?

Follow IM C2000 logs. These logs contain tests of both tools.

We have attached an image with the error message displayed.

Thanks.

Best regards,

Guilherme Santos

In the past month or so we've run into multiple issues where when we try to install our applications, both through our RXOP base installer and the WIM, our customers will get status codes that we can't find our documentation and that have cryptic descriptions.

The specific code we ran into most recently was from one of the web APIs that RXOP uses, it gave us the code "5105" with the description "apk component error". Obviously, that means something is wrong with the APK but we can't troubleshoot this because we have no idea what could cause this issue (without decompiling a bunch of the libraries provided).

I've found a few of the error codes in the documentation but those aren't the codes we've been receiving. Can we get a list of codes that WIM and the RXOP APIs will return and what they actually mean?