KB172026546: FlexProofE/PackProof - Proof Server Application stops after start up

Summary

FlexProof/PackProof Proof Server stops a few seconds after the start up.

Symptoms

When you start up the Proof Server, after a few seconds or minutes it stops again. If you check the Proof server log (C:\ProgramData\Esko\Proof\Server\Log\Server.log), you will find an error like this:

08/10/2015 13:15:45.461,414,0,10752,Server,PRINTSERVER-HP,Socket connection to port 50005 failed

08/10/2015 13:15:45.474,415,0,10752,Server,PRINTSERVER-HP,Listening thread could not be started. Error=-2034

08/10/2015 13:16:00.556,416,2000,10752,Server,PRINTSERVER-HP,Server Stopped (service)

This happens when the Proof Server is installed on the same server of Automation Engine or Imaging Engine. It can happen that an Automation Engine or Imaging Engine process holds a port (50005 in this case) that is needed to run the Proof Server. You can verify this f.i. by running currports (available in the "extra" folder of the Automation Engine install DVD), check which process allocates the mentioned port (50005).

Workaround 1 > temporarily solution

To solve this situation, proceed like this:

1. Stop BGMD (Automation Engine) or Imaging Engine (in Automation Engine > Configure > Imaging Engine)
2. Start up the Proof Server.
3. Start up again BGMD or Imaging Engine.

In this way, the Proof server will hold the ports that are needed for it and Automation Engine/Imaging Engine will be addressed to other free ones.

Workaround 2 > permanent solution

1. Click the windows start button and type "cmd"
2. Right click the "Command Prompt" icon and choose "Run as administrator"
3. Type the following in the dos box: sc config BGMD depend= lanmanserver/"Esko Proof Server" (double quotes needed around services with spaces in the name)

Verify if the Esko Proof Server service is added by typing this command: sc qc BGMD
You should see dependencies listed: lanmanserver and Esko Proof Server