ZCC will not load from Windows 2003 server after upgrade to ZCM 10.1.1

  • 7002772
  • 18-Mar-2009
  • 27-Apr-2012


Novell ZENworks 10 Configuration Management
Microsoft Windows 2003 server
Two ZCM servers in the zone


ZCC will not load from Windows 2003 server after upgrade to ZCM 10.1.1

ZCC reports an ERROR connection refused


On the problem server make a back up copy of the /zenworks/share/tomcat/conf/server.xml file then find the passphrase.txt file in the/conf/security folder and try copying the contents of the passphrase.txt file in the/zenworks/conf/security folder to the the keystorePass="" attribute of the Connector element with port=443 of the server.xml file (assuming that ZCM was installed using the default 443 port on SLES or Windows - the port may be different on OES).

For example, if the contents of the passphrase.txt are: 3f526bde6ed9a47f96834d50b3912bbe
then paste the 3f526bde6ed9a47f96834d50b3912bbe string into the keystorePass attribute of the Connector element in the server.xml file:

<!-- Define a SSL HTTP/1.1 Connector on port 443 -->
   <Connector port="443" maxHttpHeaderSize="8192"
               maxThreads="200" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" disableUploadTimeout="true"
               acceptCount="100" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS"
               keystoreFile="/etc/opt/novell/zenworks/security/server.keystore" keystorePass="3f526bde6ed9a47f96834d50b3912bbe"

Additional Information

The problem was exposed during an update from a ZCM 10.1 Windows 2003 server to ZCM 10.1.1.  The first server in the zone had a problem with the system update and the 10.1.1 system update MSI's were attempted to be installed manually to get the server out of the failed update state.  This put the server in a bad state. 

Also during the system update of ZCM 10.1.1 the install seemed to have a problem with finding java on the first server so java from the second server in the zone was copied to the first server so that the re-installation of the 10.1.1 update could continue by running ZCC from the second server.

These environmental issues contributed to the cause of the problem.

As a temporary workaround to ZCC not loading on the first server, ZCC could be run from the second server in the zone.  Temporarily installing a second ZCM server in the zone in order to get ZCC functionality may be a good workaround until the original ZCC problem is corrected.