Problem starting PaperCut Application Server on Windows
on 27 May 2011 10:41 AM
If after installation you cannot access the PaperCut administration interface it's possible that the PaperCut Application Server service has not started for some reason.
First check the "PaperCut Application Server" service in the Windows control panel to ensure it's running. If it's not running try to manually start it.
If you continue to have problems accessing PaperCut, then the PaperCut log files will help diagnose the problem. Please check the following log files for errors or problems:
Some specific problems that may occur are outlined below. Please check these to see if there is a recommended work-around there.
If you need further assistance in diagnosing the problem, please ZIP up these log files and send them to us.
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 PaperCut Application Server minimum memory requirements. These are listed in the system requirements.
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 PaperCut and this is not available in a single contiguous block. This causes the Java VM to fail to initialize.
To resolve this problem we need to explicitly set the amount of memory allocated to PaperCut. To do this:
1. Create a text file in the directory:
2. Open the file in a text editor and add the following line to make PaperCut use 512 MB of physical RAM. You may choose a different size but it is not recommended to use below 384M.
3. Save the text file
4. Restart the PaperCut Application Server service using Control Panel->Admin Tools->Services.
5. If this resolved the problem, the service should now start and the server log file (
If you continue to have problems after making this change please contact support and include a description of what you have tried and the
Please also include information about your system: