Distribution Manager Failed To Access The Source Directory

Question

_{Wednesday, March 25, 2015 2:33 PM}

Hello All,

I have this issue distributing content to my Distribution Points for months now. I keep running into this error below:

Distribution Manager Failed to Access the source directory (\share\folder\file.wim)

Possible Cause: Distribution Manager does not have sufficient rights to the source directory.

Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.

Possible Cause: There is not enough disk space available on the site server.

Solution: Verify that there is enough free disk space available on the site server.

I checked the distmgr.log file and received these messages: 

GetTempFileNameA failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
CFileLibrary::AddFile failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
CContentDefinition::AddFile failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
Failed to add the file. Please check if this file exists.    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
SnapshotPackage() failed. Error = 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
Failed to take snapshot of package CSU0006A    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)

There is enough space on the site server and the site server has full control over the source directory. I wish I can give you more information but I'm hoping this is enough info to get some assistance. If more information is needed please let me know!

All replies (13)

_{Thursday, March 26, 2015 9:19 PM ✅Answered}

Check both share and NTLM permission on your share. Please also check permission inheritance on subfolders.

_{Friday, March 27, 2015 6:59 AM ✅Answered | 1 vote}

We usually give the DP's computer account and the site server computer account read access to these shares in our environment.

... which is not enough for drivers and updates (as there will also files be added).

Torsten Meringer | http://www.mssccmfaq.de

_{Monday, April 20, 2015 11:08 PM ✅Answered | 1 vote}

I got a fix! The SCCMContentLib folder was corrupted. So I renamed it SCCMContentLib.old. When I distributed software, Config Man recreated the folders!

Thanks for your help!

_{Wednesday, March 25, 2015 8:19 PM}

Can you please add a few more of the log lines preceding the ones you posted?

_{Wednesday, March 25, 2015 8:31 PM}

Was your site migrated from 2007 and the DPs upgraded?

Jeff

_{Wednesday, March 25, 2015 8:57 PM}

I actually may have misread the original question.  Are you trying to distribute content and it fails with the mentioned errors?

If so, look at Anti-virus software and make sure you have exclusions in place.  If the content contains anything like autorun.inf or some other common file that A/V quarantines, then that may explain the issue.

Jeff

_{Friday, March 27, 2015 6:43 AM}

It sounds like it is likely permissions on the location of the content. As Hermann has said check the share permissions and the NTFS permissions on the source location. read access should be enough. We usually give the DP's computer account and the site server computer account read access to these shares in our environment.

_{Friday, March 27, 2015 10:50 AM}

We usually give the DP's computer account and the site server computer account read access to these shares in our environment.

... which is not enough for drivers and updates (as there will also files be added).

Torsten Meringer | http://www.mssccmfaq.de

... And for capture Image too if your capture destination points on that share

_{Monday, April 20, 2015 8:26 PM}

I'm sorry about the late reply. I'm still having the same issue. The line before the errors is: Set share security on share \share\SCCMContentLib$   

_{Monday, April 20, 2015 8:27 PM}

No. Config Man 2012 was a fresh install.

_{Monday, April 20, 2015 9:07 PM}

Okay. I think I'm close. I found the folder SCCMContentLib and it is missing the pkglib folder. In addition to this, the filelib folder is corrupted.

Config Man is trying to access these folders but to no avail. Is there a way to fix corrupted SCCMContentLib folders???

_{Monday, September 10, 2018 4:17 AM}

Hello. I have the same problem. I create different folder make the package. but getting the same problem.

1. I have set permission for involved folder.

2. I have added user to involved folder.

3. Other user can access to this path.

But The error still exist.

_{Wednesday, November 28, 2018 10:39 PM}

I just want to say...

I LOVE YOU