Missing Copy Functions in Documentation
Incident Properties
Question
Hello Team,
We are in the development of adding the below copy functions in our PF360 app, which is not present previously.
We go through the documentation. So far we added the Auto Density, Original Type, Original Orientation, Centering and Mirror.
But we can't see the below items in the documentation.
1. Batch, Store File in Original Setting
2. Stamp, Un Auth Copy, Color Overlay, Image Quality adjust and Positive/Negative in Edit color settings.
3. All Functions in 2 Sided/Combine/Series.
Please advice.
Scan fails with file type "TIFF/JPEG Single page" or "PDF Single page" and "Delete Blank Page".
Incident Properties
Question
Hello,
We are currently encountering an issue with two specific scan settings in our PCC5 or Unified Client application. The scan fails whenever the combination of "File Type" set to "TIFF/JPEG Single page" or "PDF Single page" and "Delete Blank Page" enabled is used.
The logs for this issue show a status code 400 returned from the device:
08-09 15:34:21.726 27558 27764 I System.out: 2024.08.09 15:34:21.725 [ INFO]: pool-4-thread-1: (RicohWebApiController) RicohWebApiController status : 400
08-09 15:34:21.727 27558 27764 I System.out: 2024.08.09 15:34:21.727 [ INFO]: pool-4-thread-1: (RicohWebApiController) RicohWebApiController getFile error : {\"errors\":[{\"message_id\":\"error.over_upper_limit\",\"message\":\"\"}]}
08-09 15:34:21.729 27558 27764 I System.out: 2024.08.09 15:34:21.729 [ INFO]: pool-4-thread-1: (RicohWebApiController) RicohWebApiController Stop loop
08-09 15:34:21.730 27558 27764 I System.out: 2024.08.09 15:34:21.729 [ERROR]: pool-4-thread-1: (RicohWebApiController) RicohWebApiController HTTP STATUS:400
08-09 15:34:21.731 27558 27764 I System.out: 2024.08.09 15:34:21.730 [DEBUG]: pool-4-thread-1: (ScanFileTransferManager) ScanFileTransferManager originalFilePath:
08-09 15:34:21.731 27558 27764 I System.out: 2024.08.09 15:34:21.731 [DEBUG]: pool-4-thread-1: (ScanFileTransferManager) ScanFileTransferManager newFileName:
08-09 15:34:21.733 27558 27764 I System.out: 2024.08.09 15:34:21.732 [ERROR]: pool-4-thread-1: (ScanFileTransferManager) ScanFileTransferManager moveFileToApplicationArea, FrameworkException: com.nuance.ndi.framework.exceptions.IFrameworkException: newFileName is empty\n\tat com.nuance.ndi.neuf.ricohplatform.scan.transfer.ScanFileTransferManager.moveFileToApplicationArea(ScanFileTransferManager.java:667)\n\tat com.nuance.ndi.neuf.ricohplatform.scan.transfer.ScanFileTransferManager.processEventAsync(ScanFileTransferManager.java:538)\n\tat com.nuance.ndi.neuf.ricohplatform.scan.transfer.ScanFileTransferManager.process(ScanFileTransferManager.java:427)\n\tat com.nuance.ndi.neuf.ricohplatform.scan.transfer.ScanFileTransferManager$5.run(ScanFileTransferManager.java:407)\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)\n\tat java.lang.Thread.run(Thread.java:919)
08-09 15:34:21.733 27558 27764 I System.out: com.nuance.ndi.framework.exceptions.IFrameworkException: newFileName is empty
08-09 15:34:21.733 27558 27764 I System.out: at com.nuance.ndi.neuf.ricohplatform.scan.transfer.ScanFileTransferManager.moveFileToApplicationArea(ScanFileTransferManager.java:667)
08-09 15:34:21.733 27558 27764 I System.out: at com.nuance.ndi.neuf.ricohplatform.scan.transfer.ScanFileTransferManager.processEventAsync(ScanFileTransferManager.java:538)
08-09 15:34:21.733 27558 27764 I System.out: at com.nuance.ndi.neuf.ricohplatform.scan.transfer.ScanFileTransferManager.process(ScanFileTransferManager.java:427)
08-09 15:34:21.733 27558 27764 I System.out: at com.nuance.ndi.neuf.ricohplatform.scan.transfer.ScanFileTransferManager$5.run(ScanFileTransferManager.java:407)
08-09 15:34:21.733 27558 27764 I System.out: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
08-09 15:34:21.733 27558 27764 I System.out: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
08-09 15:34:21.733 27558 27764 I System.out: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
08-09 15:34:21.733 27558 27764 I System.out: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
08-09 15:34:21.733 27558 27764 I System.out: at java.lang.Thread.run(Thread.java:919)
Could you please help us understand why the device is returning a 400 status code with this combination of scan settings?
Thank you,
Krishna
FIPS 140-2
Incident Properties
Question
Do the Ricoh MFPs with SOP have FIPS 140-2 capability for encryption? If so, how is it enabled. If not, is there any documentation on how to implement it.
LDAP/AD Admin user authentication failed when FAR is enabled
Incident Properties
Question
Hi Team,
Initially, when the request came to support Device LDAP/AD Admin User login when FAR is enabled, we had a call with the Ricoh team to setup the FAR configuration and required Firmware installation we tested the below scenarios:
1. FAR Enabled and Unified Application in Auth On - Device LDAP/AD Admin User login failed.
2. FAR Enabled and Unified Application in Auth Off - Device LDAP/AD Admin User login success.
3. FAR Enabled and Unified Application is not installed - Device LDAP/AD Admin User login success.
Now when we are testing it again below is the result
1. FAR Enabled and Unified Application in Auth On - Device LDAP/AD Admin User login success.
2. FAR Enabled and Unified Application in Auth Off - Device LDAP/AD Admin User login failed.
3. FAR Enabled and Unified Application is not installed - Device LDAP/AD Admin User login failed.
We have cross checked every configuration on the device but couldn't identify for what reason it is failing. When our application is not installed it should have worked. What could be the reason, Can you please help us identify the cause. Could it be because of some configuration issue?
As part of our installation, we enabled a few properties, but we are resetting them back to default during uninstallation.
Thanks.
product sign dm agent for 4neo
Incident Properties
Question
Please product sign the 4neo DMAgent
IM C2010 Emulator
Incident Properties
Question
Hello Team,
Currently we are working on the Ricoh Smart SDK Emulator(V 2.40 and V 5.00) to develop the application.
We are looking to test our application in IM C2010 using emulator.
We can't able to locate the model "IM C2010" Printer in the above emulators. Please advice.
Certificate validation issue with 8.00 firmware
Incident Properties
Question
As requested, I am opening a separate ticket for the certificate validation issue (from here: Update on firmware issue with processing of getSubjectAltNames() | Ricoh Developer Program (RiDP) (ricoh-ridp.com))
The logs are attached, you can easily find the error multiple times throughout the log by searching for "SSLPeerUnverifiedException". It appears to be exactly the same issue as previously, i.e. "hostname Hostname faxus1.xmedius.com not verified:" followed by the certificate of the CA rather than the actual certificate for faxus1.xmedius.com.
Maintenance Signing Request
Incident Properties
Question
We are requesting a new maintenance signature.
This is an additional bug fix for an issue where a user would log into the printer, initiate a scan job from the native scan app, but then if they open our app a dialog box would display "Scanning Scan Next Page or Complete?" Scan jobs from our app should be treated separate from the native scan app and this should fix that.
Production sign Dm agent for 4neo
Incident Properties
Question
product sign the 4neo Dm agent 1.30
Maintenance Signature request for v1.1.1 of RfIdeasReaderPlugin
Incident Properties
Question
While using our reader plugin, Ricoh USA discovered a minor bug in our Plugin. Instead of returning the full 64 bits of the card credential, our plugin was only returning 32 bits. The customer in question was using a 37 bit credential and observed that bits were being truncated before the credential id was returned to the Kofax print solution. We have implemented a 7 line code fix and have tested the fix internally before submitting this maintenance request.