Jump to content


limiteddenial

Error - Operating System snapshot failure

Recommended Posts

I'm trying to import and distribute a captured wim file but it fails when creating a snapshot. The wim file is on a network share that all the site systems have access to(verified).

 

The wim is 145GB(I know, it is an absurd size)

 

The primary site only has 50GB free between 2 drives. But since the content isn't being distributed to that server I don't think the space is an issue. Even if it creates a hash on that server it should be fill up any one of those drives.

 

The DP I'm trying to distribute the wim has one drive that has 429GB free and another drive that has 1.8TB free. Quota's aren't enabled on the distribution point.

 

I have tested with the default windows wim which is roughly around 3GB and that distributes fine to all the DPs.

 

 

 

Here are the log entries from distmgr.log from the primary site:

 

DPConnection::Connect: For $(PrimarySite), logged-on as $(SMSserviceAccount) SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:23 AM 10072 (0x2758)
DPConnection::Disconnect: For $(PrimarySite), reverted to SYSTEM context SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:23 AM 10072 (0x2758)
Failed to find space for 145000776127 bytes. SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
CFileLibrary::FindAvailableLibraryPath failed; 0x8007050f SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
CFileLibrary::AddFile failed; 0x8007050f SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
CContentDefinition::AddFile failed; 0x8007050f SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
Failed to add the file. Please check if this file exists. SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
SnapshotPackage() failed. Error = 0x8007050F SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=$(PrimarySite) SITE=$(Site) PID=4524 TID=10072 GMTDATE=Wed Jul 22 12:24:24.107 2015 ISTR0="$(share)\images\Win7\Lab\x64\Windows 7x64 Lab F2015R00.wim" ISTR1="Windows 7x64 Lab F2015R00" ISTR2="$(PackageID)" ISTR3="30" ISTR4="60" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="$(PackageID)" SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=$(PackageID), Version=1, Status=2302 SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=$(PrimarySite) SITE=$(Site) PID=4524 TID=10072 GMTDATE=Wed Jul 22 12:24:24.248 2015 ISTR0="Windows 7x64 Lab F2015R00" ISTR1="$(PackageID)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="$(PackageID)" SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
Failed to process package $(PackageID) after 40 retries, will retry 60 more times SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758)
Any help would be greatly appreciated.
Thanks

Share this post


Link to post
Share on other sites

The sending server still has to create a snapshot of the files it needs to send; it'll create those files locally on the server and store them locally, not on the file share the source resides on. At that point it then sends from the local server out to the DPs; however, the files will still reside on the Primary in one way or another.

 

Adding a larger HDD to the sending server should allow it to process.

 

And, Jesus, that's a big WIM :P

  • Like 1

Share this post


Link to post
Share on other sites

The sending server still has to create a snapshot of the files it needs to send; it'll create those files locally on the server and store them locally, not on the file share the source resides on. At that point it then sends from the local server out to the DPs; however, the files will still reside on the Primary in one way or another.

 

Adding a larger HDD to the sending server should allow it to process.

 

And, Jesus, that's a big WIM :P

 

Thanks, I was under the impression the primary site didn't store the content locally and only the DPs would. Appreciate the clarification.

 

I increased the hdd on the primary site and everything was happy again.

Share this post


Link to post
Share on other sites

Thanks for the info, just what I needed. This thread made me clear that the Primary Site Server also needs sufficient storage for deployments and not only the DP. So the fact that the Site Server makes a snapshot clears a lot of fog for me.

 

Pretty obvious actually

 

 

post-32512-0-89704600-1449755000.png

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.