you should post this on CMS board, right now it's on DS.

agree with Sally,

It seems u have a DNS issue. double click on one of those retries and see if u could manually resolve the location that it wants.

Nelo

DNS Entry's checked and OK.

Retries cannot be opend but the issue is that there is no source location defined for the package as can be seen in de screenshot. Other Policy jobs like lets say Software update plugin install and others have no problems. They do have a source location defined and no problem with downloading and running.

This looks like a package problem.

Can you upload package.xml and log.xml for a sample package?  You can find them in C:\Program Files\Altiris Agent\Agents\SoftwareManagement\Software Delivery\cache\{GUID} (if memory serves).

Also, if on the Symantec Management Console, you go to Settings, Notification Server, Site Settings, then expand Site Management, expand Site Servers, and select the NS, can you screenshot the Package Service portion and upload?

See also this thread which was experiencing the same issue:

https://www-secure.symantec.com/connect/forums/catalogxml-and-other-patch-files-not-getting-deployed-clients#comment-6081961

log.xml and package.xml included.

seeing statusDescription="No package sources returned by server" so no source location to download the package.

how can this be recreated or repaired ?

Was about to repair/reinstall the patch management solution but don't know if that would solve the package server issue

below teh screen shot of the package statistics. What is also peculier is that if opening the agent itself and cheking the package Server tab All packages are available and 0 invalid/retrying or pending. but on the console-Settings-notificationserver-Site server Settings->settings Package service->Package Service Settings their are pending packages for all my package servers. Seems like these two location aren't in synch.

Thanks in advanced..

solved it by replacing C:\ProgramData\Symantec\SMP\Snapshots\{6d417916-467c-46a7-a870-6d86d9345b61}.xml with a valid xml. The xml had been corrupted and was empty. Replace content with:

<FolderSnapShot path="D:\Program Files\Altiris\Patch Management\packages\windowsvulnerabilityscan" time="2012-01-27 22:04:28" hash="wAvDkQyzJMVrlAvf3GdOyA==" PkgVersion="1327698268"><Root  size="6467662" files="5" folders="0" ><File name="AexPatchAssessment.exe" size="635904" lastModifiedTime="2011-11-24 09:13:30" /><File name="catalog.xml" size="751792" lastModifiedTime="2012-01-27 21:04:27" /><File name="hf.xml" size="2243344" lastModifiedTime="2012-01-26 17:46:02" /><File name="servicepacks.xml" size="727318" lastModifiedTime="2012-01-26 20:24:51" /><File name="STPatchAssessmentSrv.exe" size="2109304" lastModifiedTime="2011-11-04 13:07:46" /></Root></FolderSnapShot>

Change the path and don't worry about the data. It will be corrected when PM updates the catalog file

Tried above but had no effect. Seems like de problem lies in the Replication of packages between the package servers. One of the four Siteservers synced up all packages overnight and inow all clients under that Siteserver seem to have no problems with running the assessmentscan and are reciving their pacthes.

Why this one Siteserver suddenly Syncs its packages correctly and the other three remain having the problem is the issue. other odd thing is that in the consloe (screenshot) you can see that there are pending packages but starting up the Agent interface under the Package Server tab shows everything in order. no pending or invalid packages and the correct number off availeble packages on all four Siteservers. Also under D:\Program Files\Altiris\Altiris Agent\Package Delivery\ the packages apear on all Site Servers. DJIPSDS106 is also the NS and is not syncing its packages.

I am hesitand to delete the snapshots .xml on de NS under C:\ProgramData\Symantec\SMP\Snapshots\  and running scheduled task NS.Package Refrech to correct the problem because their is a Siteserver where the package sync is working correctly. There four I would draw the conclusion that teh snapshots on the NS should be OK or is this a incorrect ?

Does anyone know how to repair or trigger the packages Sync proces in this particular situation ? 

I'd review for potential package server problems:
http://www.symantec.com/business/support/index?page=answers&startover=y&language=Change+Support+Language&question_box=%22No+package+sources+returned+by+server%22&product_finder=Add+a+product+for+best+results&productselectorkey=not_set&myclicker.x=0&myclicker.y=0

You may want to review this KB first on all site servers, to ensure you've configured them correctly:
http://www.symantec.com/docs/HOWTO63116