The customer installed a new SMP Server. Then he renamed the new SMP Server with the same name as his original production SMP Server and attached the original database to the new SMP Server.

After making sure he had all the packages in the same location as he used to in the original SMP Server, the following error message started to occur when one of those packages was requested by a client machine or package server or during NS.Package Refresh scheduled task ran:

GetPackageInfo.aspx: The the source key for package: 6d417916-467c-46a7-a870-6d86d9345b61, agent: ebfcbe2e-fa60-4938-b38d-0c8ef92adef0  is empty
 

Error 1:

GetPackageInfo.aspx: The the source key for package: 6d417916-467c-46a7-a870-6d86d9345b61, agent: ebfcbe2e-fa60-4938-b38d-0c8ef92adef0  is empty
-----------------------------------------------------------------------------------------------------
Date: 26/07/2021 11:01:56, Tick Count: 221503750 (2.13:31:43.7500000), Size: 379 B
Process: w3wp (7140), Thread ID: 71, Module: Altiris.NS.StandardItems.dll
Priority: 2, Source: PackageInfoProvider
File: C:\ProgramData\Symantec\SMP\Logs\a.log

Error 2:

GetPackageInfo.HandleRequest
Unable to retrieve the source key for the package.
   [Altiris.NS.Exceptions.NSComException @ Altiris.NS.StandardItems]
   at Altiris.NS.StandardItems.SiteServer.PackageServer.PackageInfoProvider.GetPackageInfoImpl(CodeProfiler cp, String requestXml, Boolean alreadyRedirected, Boolean internetRequest, Boolean& responseRedirect, Boolean& foundCodebases, Guid& resource)
   at Altiris.NS.StandardItems.SiteServer.PackageServer.PackageInfoProvider.GetPackageInfo(String requestXml, Boolean alreadyRedirected, Boolean internetRequest, Boolean& responseRedirect, Boolean& foundCodebases, Guid& agentGuid)
   at Altiris.Web.NS.Agent.GetPackageInfo.ProcessRequest(Byte[]& packageInfoData, String& packageInfoXml, Boolean& compress, Boolean& responseRedirect, Boolean& bEncrypted)
   at Altiris.Web.NS.Agent.GetPackageInfo.HandleRequest()

COM Exception errcode: 0x8005600C

Exception logged from:
   at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception, String footer)
   at Altiris.NS.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception)
   at Altiris.Web.NS.Agent.GetPackageInfo.HandleRequest()
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.HttpContext.InvokeCancellableCallback(WaitCallback callback, Object state)
   at System.Web.UI.Page.AsyncPageBeginProcessRequest(HttpContext context, AsyncCallback callback, Object extraData)
   at ASP.getpackageinfo_aspx.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object data)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
   at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
   at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
   at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)

-----------------------------------------------------------------------------------------------------
Date: 26/07/2021 11:01:56, Tick Count: 221503750 (2.13:31:43.7500000), Size: 3.61 KB
Process: w3wp (7140), Thread ID: 71, Module: w3wp.exe
Priority: 1, Source: Altiris.Web.NS.Agent.GetPackageInfo.HandleRequest

 

Since this was a new SMP Server renamed as a previous one and attached to a different database than the one that originally this server was installed with, some references for the OwnerNSGuid were not correct. This caused that the PackageShare under IIS Manager>Default Web Site>Altiris was empty or not populated as it should be (missing many subfolders that starts with pkggroup_xxxxxxxxx)

1. Open CoreSettings.config (under c:\Program Data\Symantec\SMP\Settings)

2. Look for the reference like this one:

 <customSetting key="OwnerNSGuid" type="local" value="{e69c7183-8d5b-4382-b8c2-55987dc3355a}" />

3. Check that the value matches with the one on the database. You can run the following query:

If the resulting GUID is not the same as the one on CoreSettings.config, replace the one on CoreSettings.config (under 'value') with the one from the database.

4. Restart Altiris Services, IIS and run NS.Package Refresh.

It should start recreating the proper references and package entries in IIS.

Note:

If the GUID is the same between what is in the database and on the CoreSettings.config, there is the possibility that the mentioned packages in the warning messages are flagged as owned by a different SMP Server. If that is the case, no new codebases will be generated during NS.Package Refresh scheduled task. See KB 158305 "The SMP server is not building package codebase download links for itself" for troubleshooting steps to validate if that is the issue.