Getting registration error of '[could not determine]' at URL

  • Document ID:7005551
  • Creation Date:26-Mar-2010
  • Modified Date:14-Dec-2015
    • Micro Focus Products:
      ZENworks Configuration Management

Environment

Novell ZENworks 10 Configuration Management with Support Pack 2 - 10.2 Registration

Situation

Unable to get zone configuration information.

Registration was successful but it could not determine the zone.

E.G.

 
ERROR:
 
"Successfully registered with zone "[could not determine]" at URL <fdnqofzcmserver>"

Agent was also not able to contact the zone configuration servlet on the server.
 
ERROR:
 
[DEBUG] [03/25/2010 15:09:56.194] [1764] [ZenworksWindowsService] [8] [] [ZMD] [] [GetCurrentURIFromConnectMan - URI is bad https://10.2.212.7/zenworks-zoneconfig/ trying to find another one] [] []
 [DEBUG] [03/25/2010 15:09:56.194] [1764] [ZenworksWindowsService] [8] [] [ConnectMan] [] [FindNextContent()] [] []
 [DEBUG] [03/25/2010 15:09:56.194] [1764] [ZenworksWindowsService] [8] [] [ConnectMan] [] [   badUri: https://10.2.212.7/zenworks-zoneconfig/ ] [] []
 [DEBUG] [03/25/2010 15:09:56.194] [1764] [ZenworksWindowsService] [8] [] [ConnectMan] [] [   Exception: Client found response content type of 'text/html;charset=UTF-8', but expected 'text/xml'.

Resolution

This is fixed in version 11.4.1 - see KB 7016895 "ZENworks Configuration Management 11.4.1 - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7016895

Workaround:
 
  1. Check the zoneconfig URL 'https://<zcmserverip>/zenworks-zoneconfig' and see if it shows the following:



  2. Stop all ZCM services on the server using novell-zenworks-configure -c Start from the command line.
  3. Go to the folder Linux (/opt/novell/zenworks/share/tomcat/webapps), Windows (%ZENWORKS_HOME%\share\tomcat\webapps ) make sure that the last version of the zenworks-zoneconfig.war is in that folder.
  4. Move the whole directory 'zenworks-zoneconfig' out of this folder.
  5. Start all the ZCM services.
  6. Test the zoneconfig URL again. If it appears like below screen shot then it is a working servlet.