One bad Location URL causes all devices to fail new registrations

  • 7009328
  • 09-Sep-2011
  • 27-Apr-2012

Environment

Novell ZENworks 11 Configuration Management

Situation

If any Primary or Satellite server has a bad URL for any capability, new devices cannot register to the zone.
 
ERROR (running zac reg ):
 
Registration sucessful for [Could not Determine]

ERROR (in zmd-messages.log):
 
[DEBUG] [06/15/2011 11:07:22.875] [328] [ZenworksWindowsService] [33] []
[ClosestServers] [] [Error extracting host from URI
http://:80/zenworks-content/ . Error: Invalid URI: The hostname could not be
parsed.] [] []
[DEBUG] [06/15/2011 11:07:22.875] [328] [ZenworksWindowsService] [33] []
[ClosestServers] [] [Error extracting host from URI
https://:443/ . Error:
Invalid URI: The hostname could not be parsed.] [] []

[DEBUG] [06/15/2011 11:07:22.906] [328] [ZenworksWindowsService] [33] []
[LocationConfigBasedService] [] [Could not get location configuration
Type: System.NullReferenceException
Message: Object reference not set to an instance of an object.
Stack Trace:
       at
Novell.Zenworks.Zmd.Certificates.CertManager.AddAltHostNames(X509Certificate
cert, IEnumerable`1 hosts)
       at
Novell.Zenworks.Zmd.Certificates.CertManager.AddCertificates(IEnumerable`1
certificateMaps, Dictionary`2 certUID2hostMapping)
       at
Novell.Zenworks.Zmd.LocationConfigBasedService.AddCertsForServers(List`1
serverElements)
       at
Novell.Zenworks.Zmd.LocationConfigBasedService.GetLocationConfiguration()
       at Novell.Zenworks.Zmd.LocationConfigBasedService.Create(String
serverRoot)


Resolution

This is fixed in version 11.2 - see KB 7010044 "ZENworks Configuration Management 11.2 - update information and list of fixes" which can be found at https://www.novell.com/support
 
Workaround:
 
Fix DNS to ensure that the server host name is valid.  If using Alternative DNS names ensure that they are resolvable in DNS from the primary server.  In the above error example, an Alternative DNS entry was not resolvable.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.