Problem Starting the PaperCut Application Server on Windows

KB Home   |   Problem Starting the PaperCut Application Server on Windows

If after installation you cannot access the PaperCut NG or PaperCut MF Admin web interface, it’s possible that the PaperCut Application Server service has not started for some reason.

First check the PaperCut Application Server service to ensure it’s running; this can be done via the Windows Services applet, found under Administration Tools in the Control Panel. If it’s not running, try to manually start it.

If you continue to have problems accessing the Admin web interface, then the following log files will help diagnose the problem. Please check the following log files for errors or problems (serious errors are denoted on lines which contain the word ERROR in capital letters):

  • [app-path]\server\logs\server.log
  • [app-path]\server\logs\service.log

Some specific problems that may occur are outlined below. Please check these to see if there is a recommended workaround for your particular situation.

If you need further assistance in diagnosing the problem, please send these log files to the PaperCut Support Team, or to your PaperCut implementation partner or reseller.

RAM/Memory Problems

If your server.log file is empty, but your service.log file contains entries like the following, then it indicates a problem related to the memory allocation for the application.

STATUS | wrapper  | 2011/05/23 18:02:12 | Launching a JVM...
INFO   | jvm 5    | 2011/05/23 18:02:13 | Error occurred during initialization of VM
INFO   | jvm 5    | 2011/05/23 18:02:13 | Could not reserve enough space for object heap
INFO   | jvm 5    | 2011/05/23 18:02:13 | Could not create the Java virtual machine.
ERROR  | wrapper  | 2011/05/23 18:02:13 | JVM exited while loading the application.

First, verify that your server meets the software’s minimum memory requirements. These are listed on our PaperCut NG System Requirements page.

In some cases, systems with large amounts of memory also see this problem. This occurs when the Java runtime tries to allocate a large block of memory for the Application Server, and this is not available in a single contiguous block. This causes the Java VM to fail to initialize, and the application too, in turn.

To resolve this problem, you may need to explicitly configure that a larger amount of total maximum memory be allocatable to the application. Instructions to do so can be found in the Increasing the Memory Available to PaperCut NG and PaperCut MF Knowledge Base article.

If you continue to have problems after increasing the maximum possible memory allocation, please contact the PaperCut Support Team, or your PaperCut implementation partner or reseller, including a description of what you have tried so far, along with copies of the server.log and service.log files.

Please also include the following information about your system:

  • Operating system version
  • 32 or 64 bit
  • Amount of physical RAM

Categories: Troubleshooting


Keywords: memory, failure, VM, error, start, boot, install

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on September 12, 2017, at 02:15 AM
Printable View   |   Article History   |   Edit Article