Hi Folks,

I'm having issues distributing a large 50GB wim file. We have 2x distribution points that do not have issues distributing other, smaller files, so this should not be a permissions issue or a network access account issue. 

These areas of logs seem the most interesting on distmgr:

Taking package snapshot for package UBP00183 from source \\blabla\bla.wim   SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)
Failed to find space for 56149452431 bytes. SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)
CFileLibrary::FindAvailableLibraryPath failed; 0x8007050f   SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)
CFileLibrary::AddFile failed; 0x8007050f    SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)
CContentDefinition::AddFile failed; 0x8007050f  SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)
Failed to add the file. Please check if this file exists.   SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)
SnapshotPackage() failed. Error = 0x8007050F    SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)
STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=XAVIER.campus.bath.ac.uk SITE=UBP PID=2408 TID=43244 GMTDATE=Fri Jul 24 11:02:05.733 2015 ISTR0="\\blabla\bla.wim" ISTR1="PAC Windows 7 x64 2015 Build - 2015-7-23" ISTR2="UBP00183" ISTR3="30" ISTR4="97" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="UBP00183"   SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)
Failed to take snapshot of package UBP00183 SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=UBP00183, Version=1, Status=2302  SMS_DISTRIBUTION_MANAGER    24/07/2015 12:02:05 43244 (0xA8EC)

The Distribution Points have sufficient storage space and manually copying the file over doesn't present any issues. I have noticed that the drives hosting the content library on the site server (which is not a dp), have <20GB free space. Is there something I don't know about the stages SCCM goes through to distribute content? Does it transitionally exist on the site server before making its way out to DPs?

Thanks for any suggestions.

• Edited by Shuurajou Friday, July 24, 2015 12:07 PM

So, I've now figured this out. I hope this helps anyone in the future. 

On our site server, we have:

C:\ Physical Drive (local disk for Windows and OS stuff) - NO_SMS_ON_DRIVE.SMS.

D:\ Physical Drive (SCCM installation) - does not contain NO_SMS_ON_DRIVE, because we need it to have SCCM components.

I:\ iSCSIDrive (Content Library) -  does not contain NO_SMS_ON_DRIVE, because we need it to have the content library.

It appears what happened, is that the I:\ drive became full and then overflowed into the D:\ drive, which also became full. Now to try and figure out how to get the FileLib content back off D:\ now we've expanded the I:\ drive, and how to ascertain what CM12 will consider to be it's primary content library location on the site server... now the overflow has happened.

• Marked as answer by Shuurajou Friday, July 24, 2015 12:20 PM