![]() : Page Page(3,Container(0, 66064)) is at version 430, the log file contains change version 1,641, either there are log records of this page missing, or this page did not get written out to disk properly. (next exception 1) - Page Page(3,Container(0, 66064)) is at version 430, the log file contains change version 1,641, either there are log records of this page missing, or this page did not get written out to disk properly. ![]() ERROR DatabaseUtils:316 - Unable to establish database connection. The lines that follow that message may offer clues to what the problem is. More information about the root cause can be found in the server.log file (further down in this article we explain where this is stored) if you open this file and look for the string “Unable to establish database connection”. In the example above, the message is “Connection refused” and this issue was reproduced by simply pointing to a nonexistent database. Instead of seeing the PaperCut login page, you might see a simple page with the message “System currently unavailable” with information about the database connection details, and what error was received when PaperCut tried to connect. Make certain you are browsing to the correct login URL, for example: For more information, see our article How do I log in? This might be seen if you are browsing to a non-existent URL. If not, please continue reading.Ī 404 error means the page wasn’t found. Wait a minute or two and then try logging into the web interface to see if the issue is resolved. This happens because PaperCut occasionally takes a long time to start up. If you see a message like “Error 1053: The service did not respond to the start or control request in a timely fashion” there’s no need to panic just yet. Alternatively, configure the service to run as the default Local System until the issues can be resolved. To resolve, right click on the service, choose Properties, click the logon tab, and have the Admin update the password for this service account. If you see a message like “Error 1069: The service did not start due to a logon failure” this occurs when PaperCut has been configured to run as a Service Account but the password used for this account has expired or changed. Look for any errors when the service starts up.Right-click on this service and choose Restart.Look for the PaperCut Primary Application Server service and make a note about whether it is started or not.On a Windows PaperCut server open the Services menu by pressing Windows key + R, then type services.msc and hit the enter key.See Stopping and Starting PaperCut Services for information on how to check whether the service is started on other platforms like macOS and Linux. The first thing to check is to ensure the PaperCut Primary Application server service is started. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |