Mapdb Errors in PaperCut
Help! Our PaperCut server is failing to start, and when we try to log into the browser we see an error message that mentions MapDB. What does it mean and how can we fix this?
If you’re encountering this problem you may see one of these errors when trying to access the Web Interface of your PaperCut Server.
An error occurred starting the PaperCut MF application server service. To resolve this error, try restarting the service. To report this problem, please email the support team at firstname.lastname@example.org. A detailed error log is recorded in the server log file: C:\Program Files\PaperCut MF\server\logs\server.log Error description: 0 Error details: java.lang.IndexOutOfBoundsException: 0 ...
Or the error details may give one of these messages instead:
java.io.IOException: Checksum does not match, data broken
Error details: java.io.EOFException
Errors like these typically pertain to configuration stores PaperCut uses called MapDB files. The trouble begins when the application is in the middle of writing to these files and can’t gracefully finish the operation, maybe because the server suddenly lost power or ran out of disk space. MapDB files essentially backup of all the current connections PaperCut had open at the time the service started, and thankfully they aren’t too important, but prior to PaperCut version 18.3.6 when we resolved this known issue we did hear about this affecting a number of customers.
To get this fixed and working…
- Stop the PaperCut Application server service following these steps
- Navigate to
[app-path]\server\data\internal(On a 64-bit Windows server running PaperCut MF, this path might be C:\Program Files\PaperCut MF\server\data\internal).
- Copy all the files containing “mapdb” in the name to a different folder, such as the desktop. Then delete these files from the source folder.
- Restart the PaperCut Application Server service.
- PaperCut will then create a new set of MapDB files after the restart, and after a moment you should be able to log into the web interface of the PaperCut server.
If our advice doesn’t pan out, it might be an indication of a deeper database issue, and in that scenario, please give our support team a call directly so we can investigate.
Still have questions?
Let us know! We love chatting about what’s going on under the hood. Feel free to leave a comment below or visit our Support Portal for further assistance.
Keywords: mapdb,Failed to initialise job event store,job event store