KonicaMinolta common error codes and what they mean

 First things first : Have you tried a good ol’ power-cycle? Ah, the classic troubleshooting phrase for the ages! “Have you tried turning it off and turning it on again?” It may seem like a simple (and humorous) suggestion, but it’s often an effective solution for various technical issues. Rebooting a KM MFP can reset its state, clear temporary glitches, and resolve many common problems. How’s the firmware? Do you Know if the Konica Minolta MFD’s firmware and the version of PaperCut comply with Konica Minolta’s bEST certification?(US ONLY) When dealing with KM (Konica Minolta) devices, it’s essential to understand your “bEST Certified” levels, where specific versions of firmware are exclusively paired with specific versions of PaperCut for optimal compatibility and performance. This certification ensures that the integration between KM devices and PaperCut is reliable. To check whether your KM device is “bEST Certified” and compatible with PaperCut, you can follow this link: KM bEST Certified Solutions . If your KM device is not listed on the “bEST Certified” solutions page, it is highly recommended that you promptly contact your KM device vendor. If you are not in the US, Please reach out to your KM dealer as your firmware version may need to be specialised for your PaperCut Build. Have you tried unembedding/re-embedding the device ? To address the issue, navigate to the ‘Device’ tab in PaperCut and access the settings for the device in question. From there, proceed to the ‘Advanced Config’ tab and locate the key labeled ’ext-device.integration.enabled.’ Change the value of this key to ‘N’ and then select ‘Update’ to save the changes Locate the key “ext-device.konica-minolta.force-app-registration” Change the value of this key to ‘Y’ and then select ‘Update’ to save the changes. Turn the device Off, wait for a few minutes and turn the device on again. Next, go back to the ‘Summary’ tab for the device and take a look at the message displayed in the black status bar about halfway down the page. In case the message indicates ‘Started: Stopped integration,’ return to the ‘Advanced Config’ tab for the device and find the key labeled ’ext-device.integration.enabled.’ Change the value of this key to ‘Y,’ and then select ‘Update’ to save the changes. Turn the device off, wait for a few minutes and turn the device on again. Have you tried resetting the Mapdb Files ? What are Mapdb files? MapDB files are PaperCut’s way of having parts of its database close at hand. They effectively work as a PaperCut Cache for its own database. In the case of KM devices there maybe some left-over files that are giving our devices grief Follow these steps and see if the behaviour continues Have you tried resetting the Capabilities Files ? What are Capabilities files? Capabilities files are PaperCut’s way of having parts of its knowledge close at hand. They effectively work as a PaperCut Cache for its own devices. (The issues fixed in this way were permanently fixed in later papercut versions listed here. Login to the PaperCut admin interface. Navigate to the “devices” tab Click into the Device having issues In the URL there should be a Number with an “=l” before it ( at the end of the URL) (this will likely be a 4-5 digit number like “34034”) Write that number down for later. Stop the PaperCut Application server service following these steps Navigate to [app-path]\server\data\devices(On a 64-bit Windows server running PaperCut MF, this path might be C:\Program Files\PaperCut MF\server\data\devices). Find the file with that number written down as its name (this will likely be a 4-5 digit number like “34034”) and cut it out of that directory and paste it on the desktop Restart the PaperCut Application Server service. PaperCut will then create a new file after the restart, and after a moment you should be able to log into the web interface of the PaperCut server. Are there any errors in the PaperCut admin interface? Check the device status window in Devices > [device name] > Device Status and look for an error. Below are examples of specific errors we’ve seen and their resolutions. “Error 1” Please set ‘Try Setting ext-device.konica-minolta.login.delete-sessions-on-register’ to ‘N.’ . This issue may also be fixed by upgrading PaperCut. “Error 8” Option 1: ( You Might want to Re-create the device as an OpenApi 2.3. Device in the PaperCut admin interface first) *First, connect to the device’s Webpage and create a self-signed certificate. Details on how-to are in the manual right here *​ Then, go through all of the appropriate settings As per the KM manual(above). Be sure that the OpenApi setting is set to “Enable, SSL Only.” Be sure that the Certificate Verification setting is set to “Do Not Confirm.” Then Set the TCP Socket Setting should be set to “Enable.” Turn off the Device, then turn it back on Option 2: If you see the “Error 8 - Authentication” message in Papercut: •At the panel, the MFP Screen may be completely blank, with no login information. •In the machine settings(within the webpage of the device), go to Utility > Administrator Settings > User Authentication and turn all options off. •Then power cycle the Konica Minolta. •After the restart, it should take about 10 minutes for Papercut to fully configure it, however everything should be working by then. Option 3: For a fix to the KM Error: “changeAuthenticationSetting: error=8, message=NotExistAuthApplication.” *Please note that some settings may only be visible on the panel, particularly on older models. Turn off the user authentication setting in the KM, and it will prompt to clear all data. Once that is done, turn the authentication setting back on, and Papercut should connect without any issues. *This is just a workaround until the bEST firmware is applied, or upgrades are done. Option 4: If you see an “Error=8 - Not exist” static screen on a KM, you have three options: Have your copier/vendor put it on the correct firmware and version of Papercut as per the bEST guide with KM. If you set iOption to “N” (Disable), it should connect fine just, but it may not be ideal seeing as many functions are not available without the i-option. You could create the device in the PaperCut admin interfaced as Open API 3.1+ (that is, if you are don’t care about having integrated scanning.) “Error 9” The best way to clear the “error: 9” is by making an adjustment to the advanced config keys. Login to the PaperCut admin interface, go to the “Devices” tab, click on the name of one of the Konica Minolta device in the “Device List” section. At the top click the “Advanced Config” subtab. From there, use the “Quick find:” search bar to locate the these two keys: ext-device.konica-minolta.force-app-registration ext-device.konica-minolta.logout-before-app-registration Switch both of these from “N” to “Y”, be sure to click “Update” after switching each one respectively. When you’re done, restart the PaperCut Application Server service(if this option is not available to you at the time you made the changes, we recommend power cycling the device or re-embedding it). If the previous troubleshooting steps do not resolve the issue, it is possible that your device has reached its End of Life (EOL), and the developer unit on the machine might need to be replaced. Over time, devices can experience wear and tear, which can lead to performance issues and printing errors. it’s also worth considering other potential culprits, such as the “ozone filter life counter” and the “Transfer Roller Unit counter.” If these counters are too high, contact your KM MFP vendor about resetting the counters. “Error 29” One may get this following error message on a KM C354e when trying to set it up with PaperCut: “Started (with errors) - There was an error communicating with the device Error: setApplication: error=29, message=CMS MFP Setting Check Error” The root cause of this behaviour is often associated with the KonicaMinolta switch 43, which is a device-side switch. To resolve the problem, you can reach out to your KM vendor or service provider and inquire about setting the switch to “0x03.” “Error 59” You May see this on a KonicaMinolta 554e for error=59, message=InputDeviceType. The device was initially created as OpenAPI 4.0+. Error: getDeviceInfo: error=59, message=InputDeviceType One option to resolve this error is to try deleting and re-creating the device in PaperCut while setting it up as OpenAPI 3.1+ instead of OpenAPI 4.0+. This adjustment may help to overcome any compatibility issues that arose with the OpenAPI versions relationship with the PaperCut version. Alternatively, if you have embedded the MFP as an OpenAPI 4.0+ device, the error could be related to having both the external keyboard and card reader enabled simultaneously. To tackle this, you can either remove the keyboard physically or implement the following solution with a little help from your KM technician : Set Soft Switch 25 = 60 to enable Function Level 7. Set Soft Switch 135 = 04 to disable the keyboard. Immediately reboot the copier after making each of these changes. “Error 92” When integrating a KM device with PaperCut, you may encounter an Error Code 92, which could manifest either at the device’s panel or within the PaperCut admin interface. Navigate to the advanced configuration settings of the device by going to Devices > Select Device > Advanced Config > ext-device.integration.enabled. Set the “ext-device.integration.enabled” key to “N.” Similarly, find the “ext-device.konica-minolta.force-app-registration” key in the advanced configuration settings. Set the “ext-device.konica-minolta.force-app-registration” key to “N” as well. Click on “Update” for both keys respectively to apply the changes. Wait for approximately 2-3 minutes to allow the adjustments to take effect. After the waiting period, set both keys back to “Y.” Click on “Update” for both keys again to save the changes. If this does not work, try deleting the device and recreating it in PaperCut with a different name. Is the device timing out when trying to connect to the server? The Powershell Test Open a powershell on the PaperCut Application server and type these commands: “tnc (ipaddressofyourprinter) -port 50003” and “tnc (ipaddressofyourprinter) -port 9191” and “tnc (ipaddressofyourprinter) -port 9192” Here is a quick example from above: tnc 192.168.12.1 -port 9192 If the test fails, that is definitive proof that there is something network-side that is working against PaperCut running in the way it should. In this case, There are three things to check: Network ACL(s)Network Firewall(s)Network Content Filter(s) ​​​​