Package Server could not access own Web Site using HTTP, although it is configured to serve it.
search cancel

Package Server could not access own Web Site using HTTP, although it is configured to serve it.

book

Article ID: 176112

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

Package Server agent plug-in was recently upgraded on multiple Package Servers. After that, the Agent UI shows an error message referring to:

"Package Server is configured to publish http(s) codebases, but could not access it's own web site" 

The Agent logs shows an entry like this one:

Package Server could not access own Web Site using HTTP, although it is configured to serve it. The HTTP requests from clients cannot be served. See logs for detailed failure reason. (health state: 0x00001311).

The issue is not with the HTTPS reference as usually we had seen before is but with HTTP.

Note: The actual packages are able to download via HTTP, HTTPS, or UNC without problems even when this message is present.

Package Server could not access own Web Site using HTTP, although it is configured to serve it. The HTTP requests from clients cannot be served. See logs for detailed failure reason. (health state: 0x00001311).

-----------------------------------------------------------------------------------------------------

Date: 9/27/2019 10:12:25 AM, Tick Count: 1217130156 (14.02:05:30.1560000), Size: 456 B

Process: AeXNSAgent.exe (11156), Thread ID: 9948, Module: AeXNSCPackageServer.dll

Priority: 1, Source: Package Server Agent

Environment

ITMS 8.x

Cause

The Site Server Communication Profile for each affected Package Server had 2 server names displayed. Something like:

HTTP communication hosts: SiteServer1.yourdomain.com:80;www.SiteServer1.yourdomain.com:80

The Site Server certificates had an entry under Details tab>Field "Subject Alternative Name" on the certificate that was invalid. In this case, the certificate had these names:

DNS Name=SiteServer1.yourdomain.com
DNS Name=www.SiteServer1.yourdomain.com

where "www.SiteServer1.yourdomain.com" didn't resolve properly or is invalid.

Resolution

Option 1:

  1. Recreate certificates to have the proper Alternate Names.
  2. Add that new certificate to the affected Site Server Communication Profiles.

Note: Make sure that does certificates are propagated to the client machines before removing the previous one.

Option 2:
Disable the option to pull those references from the certificates.

  1. Use NSconfigurator "C:\Program Files\Altiris\Notification Server\Bin\Tools\NSConfigurator.exe" on the NS and "Enable" the "DisableSiteServerProfileCertificateHostsPopulation" option.  This creates the entry in the CoreSettings.Config file:

  2. Go to each of the Site Server Communication Profiles (under SMP Console>Settings>Agents and Plu-ins>Symantec Management Agent>Symantec Management Agent Communication Profiles>Site Server Communication Profiles) and remove the invalid reference from "HTTP communication hosts" section. Save changes.

  3. After saving the change, run the "NS.Site Server Profiles Syncronization" in Windows Task Scheduler to process the change.
  4. Also run "NS.CEM Certificate Synchronization Schedule"
  5. Then, go to the Site Servers and request a new configuration. That should take care of the error message.
Powered by Wolken Software