Problem Starting the PaperCut Application Server on Windows

KB Home   |   Problem Starting the PaperCut Application Server on Windows

Main.ProblemStartingPaperCutOnWindows History

Hide minor edits - Show changes to output

September 12, 2017, at 02:15 AM by peterf - Revised content, and updated to mention new feature in 17.3
Changed lines 1-7 from:
(:title Problem starting PaperCut Application Server on Windows:)

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:
to:
(:title 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):
Changed lines 12-19 from:
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 [[https://www.papercut.com/contact/ | support]].

!!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 to PaperCut.
to:
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 [[https://www.papercut.com/contact/ | 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.
Changed lines 28-48 from:
First, verify that your server meets the PaperCut Application Server minimum memory requirements.  These are listed in the [[https://www.papercut.com/system-requirements/ | 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: @@[app-path]\server\custom\@@ directory called @@service.conf@@.

'''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.

-->@@
[=wrapper.java.additional.6=-Xmx512m=]@@

'''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 (@@[app-path]\server\logs\server.log@@) will show the new "max memory" setting.

If you continue to have problems after making this change please contact support and include a description of what you have tried and the @@server.log@@ and @@service.log@@ files.

Please also include information about your
system:
to:
First, verify that your server meets the software's minimum memory requirements.  These are listed on our [[https://www.papercut.com/products/ng/system-requirements/ | 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 [[https://www.papercut.com/kb/Main/IncreaseMaxMemoryUsage|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
[[https://www.papercut.com/contact/ | 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:
Changed lines 40-41 from:
* Amount of physical RAM.
to:
* Amount of physical RAM
Added lines 47-52:
Please also include information about your system:
* Operating system version
* 32 or 64 bit
* Amount of physical RAM.

Added lines 1-50:
(:title Problem starting PaperCut Application Server on Windows:)

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:
* @@[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 work-around there.

If you need further assistance in diagnosing the problem, please ZIP up these log files and send them to [[https://www.papercut.com/contact/ | support]].

!!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 to PaperCut.

[@
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 [[https://www.papercut.com/system-requirements/ | 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: @@[app-path]\server\custom\@@ directory called @@service.conf@@.

'''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.

-->@@[=wrapper.java.additional.6=-Xmx512m=]@@

'''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 (@@[app-path]\server\logs\server.log@@) will show the new "max memory" setting.

If you continue to have problems after making this change please contact support and include a description of what you have tried and the @@server.log@@ and @@service.log@@ files.

----
''Categories:'' [[Category.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