Package Servers are unable to download any new packages as they believe that the SMP Server is too busy to fulfil their request.
Server is busy. Package sources request is backing off
Due to a previous hierarchical structure being broken, the database maintained references to the child SMP which was decommissioned. Unfortunately, the CMDB had associated various packages with this decommissioned server. As a result when the Package Servers had downloaded the Package XML they were attempting to download the packages from the decommissioned server. Since they were not getting a response they were incorrectly reporting that the Server was busy.
NOTE: Before implementing the following steps please take a full backup of the Database
The first step in resolving this issue is to determine the GUID of the correct SMP Server. You can identify this by executing the following SQL Query:
Make a note of the GUID, which is returned.
The next step is to identify the correct OriginNSSourceNSID (This is used to identify which package is associated to which SMP Server) of the SMP Server, whose GUID we located in Step 1. Execute the following SQL Query to return a list of OriginNSSourceNSIDs in your environment:
SELECT ID, OriginNSGUID, SourceNSGuid
WHERE OriginNSGUID = SourceNSGUID
Verify that the result return matches the GUID returned in Step 1. You want to make sure that you note down the ID, which is returned.
The final step is to execute the following SQL Query, which will go through the CMDB and update the package association to the correct SMP Server:
SET OriginNSSourceNSId = 'Change this to the ID of the SMP Server returned in Step 2'
WHERE ItemGuid in (
FROM SWDPACKAGE SP
INNER JOIN ItemNSSource NSS on NSS.ItemGuid = SP.PackageID
INNER JOIN SWDOriginator NSO on NSO.OriginatorID = SP._OriginatorID
Symantec Management Platform 7.x
Imported Document ID: TECH180825
Subscribing will provide email updates when this Article is updated. Login is required.