PaperCut Application Server wont start with Symantec Endpoint Protection installed

KB Home   |   PaperCut Application Server wont start with Symantec Endpoint Protection installed

As of late 2010 and early 2011 PaperCut’s support team have seen an increasing number of customers who have problems starting the PaperCut Application Server in Windows environments.

If you open the [app-path]\server\logs\server.log you will see entries similar to below:

2010–12–22 07:19:04,802  WARN log:76 - failed SocketConnector@0.0.0.0:9191:
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind [WrapperSimpleAppMain]
2010–12–22 07:19:05,239  WARN log:76 - failed Server@2fcb4f: 
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind [WrapperSimpleAppMain]
2010–12–22 07:19:05,239 FATAL AppServer:182 - Unable to start application server.
Unrecognized Windows Sockets error: 0: JVM_Bind [WrapperSimpleAppMain]

You can confirm that there is another process or program running on the server that is using TCP port 9191. This is done by opening a Command Prompt and typing netstat -abno > C:\test.txt. This will generate a text file you can open in Notepad. Search through this file to find the first occurrence of :9191 (including the : ). You will see the below output:

[SemSvc.exe]
TCP    0.0.0.0:9191           0.0.0.0:0              LISTENING       4

SemSvc.exe is a process created by Symantec Endpoint Protection. You will need to reconfigure the service to not use port 9191 or uninstall the product. Please consult with your Symantec Endpoint Protection specialist.


Categories: Troubleshooting


keywords: crash

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 February 22, 2011, at 03:47 AM
Printable View   |   Article History   |   Edit Article