Having a strange issue with package distribution. On my new ConfigMgr 2012 install, I cannot distribute some packages. For example, the ConfigMgr client install, and both boot images are experiencing issues, but new packages I am creating, like OS install source, copy just fine (although they take a while due to package size).
I have a CAS and single primary, I'm making my admin console connection to the CAS, and I'm adding the primary site's distribution point (actually, a distribution point group that contains the distribution point, but I've tried both ways) to the package. I see on the primary site that it recieves notification of the package, but then says it hasn't recieved content from the CAS yet, so it'll wait. Meanwhile, the CAS logs the following snippet:
Sending a copy of package CAS00004 to site CHC SMS_DISTRIBUTION_MANAGER 7/26/2012 7:55:26 AM 3600 (0x0E10) The reporting site of site CHC is this site. SMS_DISTRIBUTION_MANAGER 7/26/2012 7:55:26 AM 3600 (0x0E10) Use drive C for storing the compressed package. SMS_DISTRIBUTION_MANAGER 7/26/2012 7:55:26 AM 3600 (0x0E10) CContentBundle::AddContentDefinitionItems failed; 0x80070003 SMS_DISTRIBUTION_MANAGER 7/26/2012 7:55:26 AM 3600 (0x0E10) CDistributionManager::AddContentToBundle failed; 0x80070003 SMS_DISTRIBUTION_MANAGER 7/26/2012 7:55:26 AM 3600 (0x0E10) CDistributionManager::CreatePackageBundle failed; 0x80070003 SMS_DISTRIBUTION_MANAGER 7/26/2012 7:55:26 AM 3600 (0x0E10) Error creating package bundle to send copy of package CAS00004 to site CHC. SMS_DISTRIBUTION_MANAGER 7/26/2012 7:55:26 AM 3600 (0x0E10)
There's also this in the SMS_Distribution_Manager summarizer:
-------------
Distribution Manager failed to process package "Boot image (x64)" (package ID = CAS00004).
Possible cause: Distribution manager does not have access to either the package source directory or the distribution point.
Solution: Verify that distribution manager can access the package source directory/distribution point.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
Possible cause: There is not enough disk space available on the site server computer or the distribution point.
Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
Possible cause: The package source directory contains files that might be in use by an active process.
Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
-------------
So, I assume the CAS is trying to create a package bundle locally - I know it has enough disk, over 10GB, I know it has permissions (as it's the local system), I don't believe this is an LFN issue, since it's a pre-created ConfigMgr package, and I'm pretty sure the images aren't in use right now. To rule out permissions issues, I've made the CAS and primary site computer accounts local admins of each other, so even if it is trying to copy across, it shouldn't be having any issues.
Has anyone else seen anything like this? It's pretty crippling, since I can't get my boot images to distribute properly. I've tried removing the content from the DP and re-adding, no luck. It's like I need to somehow reset the status of the package and get ConfigMgr to start over completely.
Thanks,
Andrew
Andrew Topp