ZENworks Service Starts and then Stops after Upgrading to ZENworks 11 SP3 (11.3)

See TID 7014716 for a somewhat similar issue where the service fails to start.

• ZENworks Control Center (ZCC) is unavailable
• The Novell ZENworks Server Service will start without error
• Refreshing the services window shows that the service has stopped again
• The Novell ZENworks Loader Service will start and stay started as opposed to the situation in the above mentioned TID

More debug information can be found with the following steps:

1. Run zenserverw.exe
2. Select the Logging tab
3. Change Level to Debug
4. Specify the Log path as %ZENWORKS_HOME%\logs
5. Specify Redirect Stdout as %ZENWORKS_HOME%\logs\zenserver-out.log
6. Specify Redirect Stderror as %ZENWORKS_HOME%\logs\zenserver-error.log
7. Restart the Novell ZENworks Server Service

The following can be seen in the zenserver-error.log:

ERROR:
org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler ["ajp-bio-8009"]
java.net.BindException: Address already in use: JVM_Bind <null>:8009

The following can be seen when running the command "netstat -nab":

  TCP    127.0.0.1:8009         0.0.0.0:0              LISTENING
 [tomcat7.exe]

Do one of the following:

• Disable the LiveTime service
• Move the Service Desk installation to another server.

Service Desk and ZENworks are conflicting with each other as they both use the same port (8009) for Tomcat by default.