PaperCut Web Interface Wont Load

KB Home   |   PaperCut Web Interface Wont Load

Main.NoAccessToWebInterface History

Hide minor edits - Show changes to output

April 12, 2019, at 08:15 PM by Alan Morris - Added a couple other Windows services that we have encountered recently
Changed lines 75-76 from:
In our experience not all services return an ID that matches a running process in task manager.
to:
In our experience not all services return an ID that matches an easily identified process in task manager.  Some will report the PID of Windows operating system, 4.
Added lines 85-86:
*Windows Remote Management (WS-Management)
*Routing and Remote Access
June 06, 2016, at 07:06 AM by Shane Higgins -
Added lines 71-72:
\\
Changed lines 75-80 from:
In our experience not all services return an ID that matches a running process in task manager. If this is the case then there is no easy way to find out what was stopping the PaperCut Admin UI from loading.
to:
In our experience not all services return an ID that matches a running process in task manager.

[@TCP    0.0.0.0:9191          0.0.0.0:0              LISTENING      4
[cannot obtain ownership information] @]

If this is the case then there is no easy way to find out what was stopping the PaperCut Admin UI from loading.
Added line 83:
*World Wide Web publishing service (IIS)
Changed line 76 from:
Appcore
to:
*Appcore
Changed lines 77-80 from:
[=ASCServiceManger=]
[=LightTPDService=]
[=PHPService=]
to:
*[=ASCServiceManger=]
*[=LightTPDService=]
*[=PHPService=]
September 05, 2013, at 12:24 PM by RossM - Added services that have caused 403 errors
Changed lines 77-80 from:
ASCServiceManger
LightTPDService
PHPService
to:
[=ASCServiceManger=]
[=
LightTPDService=]
[=
PHPService=]
Added lines 71-80:
!! Other services to check

In our experience not all services return an ID that matches a running process in task manager. If this is the case then there is no easy way to find out what was stopping the PaperCut Admin UI from loading.
Our support staff via remote software to a customers site have gone through a process of stopping a service, restarting the PaperCut Application Server service and refreshing the Admin UI. Below is a list of services that support have noticed can cause the Admin UI to return a 403 Forbidden error.

Appcore
ASCServiceManger
LightTPDService
PHPService

Changed line 84 from:
[-Keywords: PaperCut browser error, 404, open port 9191 -]
to:
[-Keywords: PaperCut browser error, 404, open port 9191, fm audit, fm -]
Added lines 77-80:
!! Anti-Virus

PaperCut has recently (March 2012) had reports that Sophos Endpoint Security and Control, version 9.7, can prevent the PaperCut Application Server from starting. This was resolved by adding an exception to Sophos.

Changed line 84 from:
[-Keywords: PaperCut browser error, 404, open port 9191 -]
to:
[-Keywords: PaperCut browser error, 404, open port 9191 -]
Changed lines 3-4 from:
There are a number of possible issues that can cause the PaperCut Administration Console and User Web Pages to become unavailable. These can range from network issues, firewalls settings, to stopped services to perhaps even a corrupt hard drive. This KB article will list many of the possible issues and their resolutions.
to:
There are a number of possible issues that can cause the PaperCut Administration Console and User Web Pages to become unavailable. These can range from network issues, firewall settings, to stopped services to perhaps even a corrupt hard drive. This KB article will list many of the possible issues and their resolutions.
Changed lines 3-4 from:
There are a number of possible issues that can cause the PaperCut Administration Console and User Web Pages to become unavailable. These can range from network issues to stopped services to perhaps even a corrupt hard drive. This KB article will list many of the possible issues and their resolutions.
to:
There are a number of possible issues that can cause the PaperCut Administration Console and User Web Pages to become unavailable. These can range from network issues, firewalls settings, to stopped services to perhaps even a corrupt hard drive. This KB article will list many of the possible issues and their resolutions.
Changed line 80 from:
[-Keywords: -]
to:
[-Keywords: PaperCut browser error, 404, open port 9191 -]
Changed lines 67-70 from:
to:
Other examples:
[@TCP    0.0.0.0:9191          0.0.0.0:0              LISTENING      1724
 [FMAuditOnsiteServiceController.exe] @]

Changed lines 52-53 from:
To troubleshoot this we need to find out what process has TCP port 9191 open. To do this, open a command prompt on the PaperCut Server and type in the following command: [@netstat -abon > C:\papercut.txt@].
to:
To troubleshoot this we need to find out what process has TCP port 9191 open. To do this, open a command prompt on the PaperCut Server and type in the following command:
 [@netstat -abon > C:\papercut.txt@].
October 03, 2011, at 07:25 PM by Rick - clarified how page loads when app. server starts
Changed lines 39-40 from:
This error should normally only be seen when the PaperCut Application Server is [[http://en.wikipedia.org/wiki/Booting|booting]] (i.e. very early part of starting up). This process generally only takes a second or so. If you refresh your Web Browser in a moment, normal operation should resume.
to:
This error should normally only be seen when the PaperCut Application Server is [[http://en.wikipedia.org/wiki/Booting|booting]] (i.e. very early part of starting up). This process generally only takes a second or so. When the Application server is started you can refresh your Web Browser and the page will load.
Changed lines 67-68 from:
!! I use SUSE Linux and the Application Server just doesn't start?
to:
!! I use SUSE Linux and the Application Server just doesn't start.
September 21, 2011, at 01:03 AM by tim - get rid of work-in-progress, link to other database problems
Changed lines 3-8 from:
!! This is a work in progress.

Check back soon!

There are a number of possible issues that can cause the PaperCut Administration Console and User Web Pages
to become unavailable. These can range from network issues to stopped services to perhaps even a corrupt hard drive. This KB article will list as many of the possible issues and their resolutions.
to:
There are a number of possible issues that can cause the PaperCut Administration Console and User Web Pages to become unavailable. These can range from network issues to stopped services to perhaps even a corrupt hard drive. This KB article will list many of the possible issues and their resolutions.
Added lines 24-25:
For other possible database problems, please refer to: [[RestoringACorruptDatabase]].
September 21, 2011, at 12:53 AM by tim - stop from wiki interpreting as markup
Changed lines 64-65 from:
You can see that something is listening on TCP Port 9191. This is process ID 4872. It's also listening on 9393 in this example. You can try opening Windows Task Manager, clicking on the Processes tab, then View -> Select Columns and ticking PID (Process Identifier) and clicking OK. This should give you a list of PIDs to compare this against.
to:
You can see that something is listening on TCP Port 9191. This is process ID 4872. It's also listening on 9393 in this example. You can try opening Windows Task Manager, clicking on the Processes tab, then View -> Select Columns and ticking PID (Process Identifier) and clicking OK. This should give you a list of [=PIDs=] to compare this against.
Changed lines 52-53 from:
In this instance it looks like something might already be listening on TCP port 9191, stopping PaperCut from running properly. We've had reports of of [[ApplicationServerFailsToStartSymantec |Symantec Endpoint Protection]] causing this issue, there may be other applications that do this as well.
to:
In this instance it looks like something might already be listening on TCP port 9191, stopping PaperCut from running properly. We've had reports of [[ApplicationServerFailsToStartSymantec |Symantec Endpoint Protection]] causing this issue, there may be other applications that do this as well.
Changed lines 52-53 from:
In this instance it looks like something might already be listening on TCP port 9191, stopping from PaperCut running properly. We've had reports of of [[ApplicationServerFailsToStartSymantec |Symantec Endpoint Protection]] causing this issue, there may be other applications that do this as well.
to:
In this instance it looks like something might already be listening on TCP port 9191, stopping PaperCut from running properly. We've had reports of of [[ApplicationServerFailsToStartSymantec |Symantec Endpoint Protection]] causing this issue, there may be other applications that do this as well.
September 19, 2011, at 03:41 PM by 67.170.157.102 - typos
Changed lines 26-27 from:
If you are using an [[https://www.papercut.com/products/ng/manual/ch-ext-db.html|External Database]] please check that the PaperCut Application Server has good connectivity to the External Database and that the Database Services (Oracle, `PosgreSQL, `MySQL, MSSQL) are available and not corrupt.
to:
If you are using an [[https://www.papercut.com/products/ng/manual/ch-ext-db.html|External Database]] please check that the PaperCut Application Server has good connectivity to the External Database and that the Database Services (Oracle, `PosgreSQL, `MySQL, MSSQL) are available and are not corrupt.
Changed lines 64-65 from:
You can see that something is listening on TCP Port 9191. This is process ID 4872. It's also listening on 93939 in this example. You can try opening Windows Task Manager, clicking on the Processes tab, then View -> Select Columns and ticking PID (Process Identifier) and clicking OK. This should give you a list of PIDs to compare this against.
to:
You can see that something is listening on TCP Port 9191. This is process ID 4872. It's also listening on 9393 in this example. You can try opening Windows Task Manager, clicking on the Processes tab, then View -> Select Columns and ticking PID (Process Identifier) and clicking OK. This should give you a list of PIDs to compare this against.
Changed lines 71-72 from:
We have had a couple of reports that even though Yast (Yast2 etc) shows that PaperCut's Application Server is setup correctly at the correct run levels that the PaperCut Application Server just doesn't run. If you invoke it manually via the [@/etc/init.d/papercut start@] command, it starts correctly.
to:
We have had a couple of reports that even though Yast (Yast2 etc) shows that PaperCut's Application Server is set up correctly at the correct run levels, that the PaperCut Application Server just doesn't run. If you invoke it manually via the [@/etc/init.d/papercut start@] command, it starts correctly.
Changed lines 49-50 from:
[@failed SocketConnector@0.0.0.0:9191: java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind [WrapperSimpleAppMain]@]
to:
[@failed SocketConnector@0.0.0.0:9191: java.net.SocketException:@]
 [@
Unrecognized Windows Sockets error: 0: JVM_Bind [WrapperSimpleAppMain]@]
Deleted lines 73-74:
TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous
Changed line 75 from:
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
to:
''Categories:'' [[Category.Troubleshooting|+]]
Changed line 77 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: -]
Changed lines 57-58 from:
[@Proto Local Address Foreign Address State PID
TCP 0.0.0.0:9191
0.0.0.0:0 LISTENING 4872
to:
[@Proto Local Address Foreign Address State    PID
TCP 
0.0.0.0:9191  0.0.0.0:0      LISTENING 4872
Changed line 60 from:
TCP 0.0.0.0:9393 0.0.0.0:0 LISTENING 4872
to:
TCP   0.0.0.0:9393  0.0.0.0:0     LISTENING 4872
Changed lines 53-56 from:
To troubleshoot this we need to find out what process has TCP port 9191 open. To do this, open a command prompt on the PaperCut Server and type in the following command: "[@netstat -abon > C:\papercut.txt@]"

Then open the [@C:\papercut.txt"@] file and search for "9191". You will likely see results like this.
to:
To troubleshoot this we need to find out what process has TCP port 9191 open. To do this, open a command prompt on the PaperCut Server and type in the following command: [@netstat -abon > C:\papercut.txt@].

Then open the [@C:\papercut.txt@] file and search for [@9191@]. You will likely see results like this.
Changed lines 49-50 from:
[@failed `SocketConnector@0.0.0.0:9191: java.net.`SocketException: Unrecognized Windows Sockets error: 0: `JVM_Bind [`WrapperSimpleAppMain]@]
to:
[@failed SocketConnector@0.0.0.0:9191: java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind [WrapperSimpleAppMain]@]
Added lines 45-67:
!! Socket errors and Stolen Ports

There are some times when the PaperCut Application Server just doesn't start and when you look in the [@[app-path]\server\logs\server.log@] you see an error message that is very similar to the error message below:

[@failed `SocketConnector@0.0.0.0:9191: java.net.`SocketException: Unrecognized Windows Sockets error: 0: `JVM_Bind [`WrapperSimpleAppMain]@]

In this instance it looks like something might already be listening on TCP port 9191, stopping from PaperCut running properly. We've had reports of of [[ApplicationServerFailsToStartSymantec |Symantec Endpoint Protection]] causing this issue, there may be other applications that do this as well.

To troubleshoot this we need to find out what process has TCP port 9191 open. To do this, open a command prompt on the PaperCut Server and type in the following command: "[@netstat -abon > C:\papercut.txt@]"

Then open the [@C:\papercut.txt"@] file and search for "9191". You will likely see results like this.

[@Proto Local Address Foreign Address State PID
TCP 0.0.0.0:9191 0.0.0.0:0 LISTENING 4872
[System]
TCP 0.0.0.0:9393 0.0.0.0:0 LISTENING 4872
[System]@]

You can see that something is listening on TCP Port 9191. This is process ID 4872. It's also listening on 93939 in this example. You can try opening Windows Task Manager, clicking on the Processes tab, then View -> Select Columns and ticking PID (Process Identifier) and clicking OK. This should give you a list of PIDs to compare this against.

Using this, you should be able to narrow down what and where something is listening on PaperCut's TCP port 9191.

Changed lines 49-50 from:
In these couple of cases it was reported that changes needed to be made to the SUSE program AppArmor. The exact changes required are unknown at this time.
to:
In these couple of cases it was reported that changes needed to be made to the SUSE program `AppArmor. The exact changes required are unknown at this time.
Added lines 45-50:
!! I use SUSE Linux and the Application Server just doesn't start?

We have had a couple of reports that even though Yast (Yast2 etc) shows that PaperCut's Application Server is setup correctly at the correct run levels that the PaperCut Application Server just doesn't run. If you invoke it manually via the [@/etc/init.d/papercut start@] command, it starts correctly.

In these couple of cases it was reported that changes needed to be made to the SUSE program AppArmor. The exact changes required are unknown at this time.

Added lines 30-33:
If you encounter HTTP errors you may find a solution below. If not, please contact PaperCut Technical Support for further advice.

Shown below are some of the more common errors.

Changed lines 39-40 from:
This error should normally only be seen when the PaperCut Application Server is [[http://en.wikipedia.org/wiki/Booting|booting] (i.e. very early part of starting up). This process generally only takes a second or so. If you refresh your Web Browser in a moment, normal operation should resume.
to:
Variations may include [@/admin /user /release@] and [@/@]

This error should normally only be seen when the PaperCut Application Server is [[http://en
.wikipedia.org/wiki/Booting|booting]] (i.e. very early part of starting up). This process generally only takes a second or so. If you refresh your Web Browser in a moment, normal operation should resume.

If you have something else other than the above listed paths then you may have the wrong URL. Please check the URL and try again
.
Changed lines 30-31 from:
HTTP ERROR: 404
to:
[@HTTP ERROR: 404
Deleted line 31:
Changed lines 33-35 from:

Powered by Jetty://
to:
Powered by Jetty://@]
Changed lines 26-27 from:
If you are using an [[https://www.papercut.com/products/ng/manual/ch-ext-db.html|External Database]] please check that the PaperCut Application Server has good connectivity to the External Database and that the Database Services (Oracle, PosgreSQL, MySQL, MSSQL) are available and not corrupt.
to:
If you are using an [[https://www.papercut.com/products/ng/manual/ch-ext-db.html|External Database]] please check that the PaperCut Application Server has good connectivity to the External Database and that the Database Services (Oracle, `PosgreSQL, `MySQL, MSSQL) are available and not corrupt.

!! HTTP Errors

HTTP ERROR: 404

Problem accessing /app. Reason:

    NOT_FOUND

Powered by Jetty://

This error should normally only be seen when the PaperCut Application Server is [[http://en.wikipedia.org/wiki/Booting|booting] (i.e. very early part of starting up). This process generally only takes a second or so. If you refresh your Web Browser in a moment, normal operation should resume
.
Changed lines 26-27 from:
If you are using an [https://www.papercut.com/products/ng/manual/ch-ext-db.html|External Database] please check that the PaperCut Application Server has good connectivity to the External Database and that the Database Services (Oracle, PosgreSQL, MySQL, MSSQL) are available and not corrupt.
to:
If you are using an [[https://www.papercut.com/products/ng/manual/ch-ext-db.html|External Database]] please check that the PaperCut Application Server has good connectivity to the External Database and that the Database Services (Oracle, PosgreSQL, MySQL, MSSQL) are available and not corrupt.
Changed lines 26-27 from:
If you are using an [[https://www.papercut.com/products/ng/manual/ch-ext-db.html External Database]] please check that the PaperCut Application Server has good connectivity to the External Database and that the Database Services (Oracle, PosgreSQL, MySQL, MSSQL) are available and not corrupt.
to:
If you are using an [https://www.papercut.com/products/ng/manual/ch-ext-db.html|External Database] please check that the PaperCut Application Server has good connectivity to the External Database and that the Database Services (Oracle, PosgreSQL, MySQL, MSSQL) are available and not corrupt.
Added lines 26-27:
If you are using an [[https://www.papercut.com/products/ng/manual/ch-ext-db.html External Database]] please check that the PaperCut Application Server has good connectivity to the External Database and that the Database Services (Oracle, PosgreSQL, MySQL, MSSQL) are available and not corrupt.
Changed line 23 from:
* System currently unavailable - There was an error connecting to the PostgreSQL database. The system will attempt to reconnect in 30 seconds.
to:
* System currently unavailable - There was an error connecting to the `PostgreSQL database. The system will attempt to reconnect in 30 seconds.
Added lines 18-25:
!! Database problems

If you see the following errors you may have a database problem.

* System temporarily unavailable - There was an error connecting to the database. Please try again later. If the problem persists, please contact your network administrator.
* System currently unavailable - There was an error connecting to the PostgreSQL database. The system will attempt to reconnect in 30 seconds.
* Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

Added lines 1-23:
(:title PaperCut Web Interface Wont Load:)

!! This is a work in progress.

Check back soon!

There are a number of possible issues that can cause the PaperCut Administration Console and User Web Pages to become unavailable. These can range from network issues to stopped services to perhaps even a corrupt hard drive. This KB article will list as many of the possible issues and their resolutions.

!! Common troubleshooting tools

In this KB article we will use some advanced troubleshooting tools such as 'ping', 'telnet', 'traceroute', 'net start' etc. We will provide example usage that is relevant for PaperCut troubleshooting.

* '''ping''' - found on all operating systems, used to see if a destination computer / router / printer is online and responding.
* '''telnet''' - found on all operating systems, used to see if basic TCP connections can be made to a destination computer / router / printer.
* '''traceroute''' - found on all operating systems with slight variations, used to show the network path between two computers / routers / printers.
* '''net start''' & '''net stop''' - found on Microsoft Windows operating systems. Used to start and stop services such as the PaperCut Application Server and PaperCut Print Provider.

TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous

----
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
----
[-Keywords: TODO keywords here if needed-]

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 April 12, 2019, at 08:15 PM
Printable View   |   Article History   |   Edit Article