Friday, May 30, 2014

The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over



When creating or updating a device driver package SCCM 2012 console displays the package distributed successfully. However when we run the task sequence, the task sequence will fail with “This task sequence cannot be run because a package referenced by the task sequence couldn’t not be found.”
If we browse to the distribution point for the package under SMSPKG$ location, we won’t be able to locate the package folder. Which means the primary server processes the request and completed the request successfully. But nothing has copied to the distribution point. Now it is time to look into distmgr.log on the primary server.
On the distmgr.log  we will see;
Successfully created/updated the package LAB00289 then few lines down;
Attempting to add or update a package on a distribution point then
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over.
So the driver package doesn’t have anything to copy to the distribution points. So open the package source folder and check for the contents in that folder. That must be empty for whatever reason.
To fix this problem; re-import the drivers to the package then re-distribute them to the all the distribution points.

Make sure that the contents are available o the package source folder.

1 comment:

  1. Today I had exact problem and fixed with your solution.
    Thanks for the post.

    ReplyDelete