Packages may try to access a Distribution Point that was removed

Packages may try to access a Distribution Point that was removed

  • Comments 4
  • Likes

image

If you take a look at all the calls we get here in the SMS/ConfigMgr support group, this one would have to rank right up there in popularity.  What happens here is the Distribution Point (DP) share, or the DP itself, is removed but you still have packages pointing to the missing resource. 

Usually you'll know this is what happened because the distmgr.log shows something like the following:

Cannot establish connection to
["Display=\\<server>\<share>\"]MSWNET:["SMS_SITE=<site>"]\\<server>\<share>\ SMS_DISTRIBUTION_M
ANAGER 17672 (0x4508)

Error occurred. SMS_DISTRIBUTION_MANAGER 17672 (0x4508)

You'll also notice that the DP share name (or the DP) is listed in the list of available DP's for the
package and is shown as unknown.  So now what do you do?  Here's how you can remove those entries for the nonexistent server/share:

1. Backup the ConfigMgr database.

2. Find the entries for the DP package share:

Queries to find references to the invalid DP share in the various tables:

Select * from packages where shareName like '%\\DPNAME\SHARE%'
Select * from pkgservers where NALpath like '%\\DPNAME\SHARE%'
Select * from pkgstatus where pkgserver like '%\\DPNAME\SHARE%'
Select * from contentdpmap where serverpath like '%\\DPNAME\SHARE%'
Select * from DPinfo where server name like '%DPNAME%'

3. Delete any entries from any of the above tables that point to the nonexistent share:

Queries to delete references to the invalid DP share:

Delete from packages where shareName like '%\\DPNAME\SHARE%'
Delete from pkgservers where NALpath like '%\\DPNAME\SHARE%'
Delete from pkgstatus where pkgserver like '%\\DPNAME\SHARE%'
Delete from contentdpmap where serverpath like '%\\DPNAME\SHARE%'
Delete from DPinfo where server name like '%DPNAME%'

Note: The ‘packages’ table doesn’t exist in ConfigMgr 2007 as it does on SMS 2003 but the cleanup process still works on ConfigMgr if you exclude the ‘Packages’ table from the cleanup.

4. To test, create a blank text file in the package source location.  Restart the site component manager, refresh the DP's and then monitor distmgr.log, making sure you receive no more errors like the one above.

That should do it!

I must extend a special thanks to A. Subramani and Manoj Kamath for their work on this issue.  Without them this posted never would have been.

J.C. Hornbeck | Manageability Knowledge Engineer

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Feed: The Configuration Manager Support Team Blog Posted on: Wednesday, February 25, 2009 9:10 AM Author

  • I had this issue, It works fine for primary site but for secondary site you have to delete files for each package where the DP was selected:

    <Seconday Site>\<Drive>\SMS\Inboxes\PkgInfo.box delete <PackageID>.ICO+<PackageID>.NAL+<PackageID>.PKG

    <Seconday Site>\<Drive>\SMS\Inboxes\Distmgr.box Delete <PackageID>.PKG

    <Seconday Site>\<Drive>\SMS\Inboxes\Distmgr.box  Delete <PackageID>.PKG

    <Seconday Site>\<Drive>\CAP_SiteCodes\PkgInfo.box Delete <PackageID>.ICO+<PackageID>.NAL+<PackageID>.PKG

  • Looks like a typo in the last query, the column named "server name" doesn't have a space:

    Try changing from:

    Select * from DPinfo where server name like '%DPNAME%'

    to

    Select * from DPinfo where ServerName like '%DPNAME%'

    and from:

    Delete from DPinfo where server name like '%DPNAME%'

    to

    Delete from DPinfo where ServerName like '%DPNAME%'

  • @Tyson: You are right. The last query has an extra space between server and name.