ITMS 8.X GetPackageInfo.aspx fails with Error 0x8005600B and 'non-package server' Log Entry

Products

• IT Management Suite

Issue/Introduction

Target agents or Package Servers fail to download package information. The Symantec Management Agent logs show the following errors:

• Error Type: SMP Server error
• Error Code: No error description available (0x8005600B)
• Error Note: HTTP Status 200: 200 OK
• Component: AeXNetComms.dll / AeXPackageDelivery.dll
• Operation: 'Direct: Get' failed for .../Altiris/NS/Agent/GetPackageInfo.aspx

   

  SMP Server Log Analysis

  When reviewing the Symantec Management Platform (SMP/NS) logs, the following critical entry is found at the time of the failure:

  GetPackageInfo.aspx was called by non-package server with Package Server request type by agent [ClientGUID], the response will not be generated.

Environment

ITMS 8.7.x, 8.8.x

Cause

This error occurs when an agent (identified by GUID ClientGUID) sends a request to the Notification Server claiming to be a Package Server, but the Notification Server's database does not have that specific resource flagged or authorized as a valid Package Server.

Common triggers include:

1. Stale Site Server Settings: The agent was previously a Package Server but has been uninstalled or the role was removed, yet it is still attempting to perform Package Server-specific requests.
2. Configuration Mismatch: The agent is using a Communication Profile that incorrectly forces it to act as a Package Server.
3. Database Inconsistency: The resource is marked as a Package Server in one table but missing the required associations in the Site Server tables.

Resolution

1. Verify Package Server Role

1. In the SMP Console, navigate to Settings > All Settings > Notification Server > Site Server Settings.
2. Check if the agent [ClientGUID] is listed under Site Servers > [Site Name] > Package Service.
3. If it should NOT be a Package Server, ensure the role is completely removed from the console and that the agent has received the updated policy.

2. Reset Agent Communication

On the affected client machine:

1. Open the Symantec Management Agent interface.
2. Click Update Configuration to ensure it has the latest Site Server role assignments.
3. If the issue persists, reset the agent GUID or reinstall the agent to clear any cached role identities.

3. Validate Site Server Synchronization

1. On the SMP Server, run the NS.Package Refresh and NS.Site Server Profiles Synchronization scheduled tasks from the Windows Task Scheduler.
2. This forces the Notification Server to reconcile which agents are authorized to make 'Package Server request type' calls.