SOLVED

Package creation failed: Not enough memory resources are available to complete this operation.

%3CLINGO-SUB%20id%3D%22lingo-sub-334579%22%20slang%3D%22en-US%22%3EPackage%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-334579%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20am%20currently%20using%20MSIX%20Packaging%20Tools%20to%20package%20my%20desktop%20application%20to%20MSIX%20with%20Set-up.exe%20installer.%20While%20during%20the%20process%20of%20MakeAppx.exe%2C%20it%20failed%20with%20message%20%22MakeAppx%20%3A%20error%3A%200x8007000e%20-%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20help%20me%20with%20this%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481450%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481450%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Adityag%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECould%20you%20share%20some%20additional%20details%20with%20me%20to%20help%20narrow%20down%20the%20issue%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EInformation%20that%20would%20help%20me%3A%3C%2FP%3E%0A%3CP%3E1.%20Are%20you%20running%20x86%20or%20x64%20version%20of%20the%20tool%3F%3C%2FP%3E%0A%3CP%3E2.%20Are%20you%20running%20the%20conversion%20locally%20or%20on%20a%20vm%2Fremote%20machine.%3C%2FP%3E%0A%3CP%3E3.%20How%20much%20physical%20memory%20does%20your%20conversion%20environment%20have%3F%20Are%20you%20running%20other%20programs%20in%20the%20background%20while%20conversion%20is%20happening%3F%3C%2FP%3E%0A%3CP%3E4.%20Does%20the%20issue%20repro%20consistently%20and%20with%20all%20installers%3F%20Or%20is%20there%20a%20particular%20installer%20that%20is%20triggering%20this%20problem%20for%20you%3F%3C%2FP%3E%0A%3CP%3E5.%20Can%20you%20share%20the%20conversion%20log%20and%20the%20specific%20failure%20you%20see%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFeel%20free%20to%20file%20a%20feedback%20item%20via%20feedback%20hub%20or%20reply%20to%20me%20directly%20if%20have%20data%20that%20you%20prefer%20to%20keep%20more%20private.%26nbsp%3B%20Please%20review%20your%20logs%20for%20sensitive%20content%20before%20sharing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%0A%3CP%3EJames%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480972%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480972%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20still%20facing%20this%20error%2C%20and%20I%20picked%20up%20the%20MSIX%20packaging%20tool%20Store%20app%20about%20a%20week%20ago.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-358135%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-358135%22%20slang%3D%22en-US%22%3E%3CP%3EHey%2C%20I've%20faced%20the%20same%20issue%2C%20because%20I%20was%20running%20from%20Developer%20Command%20Prompt%2C%20then%20I%20switched%20to%20cmd%20and%20launched%20manually%20from%20%22C%3A%5CProgram%20Files%20(x86)%5CWindows%20Kits%5C10%5Cbin%5C%3CWINSDK_VERSION%3E%5Cx64%22%26nbsp%3B10.0.17763.0%20sdk%20have%20no%20such%20problem%20so%20I%20was%20able%20to%20build%20app%20successfully.%20Cheers%3C%2FWINSDK_VERSION%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-356430%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356430%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20D4rkV0id%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20particular%20failure%20hitting%20x64%20machines%20shouldn't%20hit%20on%20a%20x86%20machine.%26nbsp%3B%20If%20you%20are%20seeing%20x86%20specific%20failures%2C%20please%20share%20the%20logs%20with%20me%20to%20review.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3CBR%20%2F%3EJames%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-356289%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356289%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20there.%20Can%20you%20provide%20any%20workaround%2C%20old%20version%20for%20example%2C%20till%20you%20fix%20the%20issue%3F%20I%20need%20to%20build%20package%20for%20our%20customers%20but%20can't%20because%20of%20error%2C%20it%20repeats%20across%20all%20windows%20devices%20we%20have.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-355761%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-355761%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20about%20x32%20machines%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-355408%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-355408%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20working%20on%20the%20insider%20track.%26nbsp%3B%20It%20should%20be%20available%20towards%20the%20end%20of%20the%20month%20or%20early%20March.%26nbsp%3B%20Updates%20will%20be%20available%20on%20the%20docs%20site%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FMSIXToolPreview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FMSIXToolPreview%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EJohn%20Vintzel%20(%40jvintzel)%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EProgram%20Manager%20Lead%2C%20MSIX%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-355122%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-355122%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20I've%20been%20facing%20the%20same%20issue%20as%20well%20with%20the%20current%20version%20of%20the%20tool%20(v1.2019.110.0)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20there%20any%20updates%20regarding%20the%20release%20to%20the%20insider%20track%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDickson%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-338577%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-338577%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20will%20be%20in%20the%20insider%20track%2C%20but%20the%20builds%20are%20not%20yet%20live.%26nbsp%3B%20We%20expect%20to%20have%20more%20information%20in%20the%20next%20week%20or%20so%20on%20releases%20to%20the%20insider%20track.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJohn%20Vintzel%20(%40jvintzel)%3C%2FP%3E%0A%3CP%3EProgram%20Manager%20Lead%2C%20MSIX%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-335086%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-335086%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20the%20update%20that%20fixes%20this%20issue%20live%20on%20the%20Insider%20track%3F%20I%20am%20also%20running%20in%20to%20this%20problem%20every%20time%20I%20try%20to%20convert%20my%20program.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ETommy%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-334848%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-334848%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mei%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20do%20a%20release%20of%20our%20tool%20every%20few%20months%2C%20and%20our%20most%20recent%20one%20was%20in%20January.%20If%20you%20are%20interested%20in%20getting%20updates%20faster%2C%20we%20recently%20created%20a%20MSIX%20Packaging%20Tool%20Insider%20Preview%20Program%2C%20which%20you%20can%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fmpt-overview%23msix-packaging-tool-insider-preview-program%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ejoin%20here%3C%2FA%3E.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%3C%2FP%3E%0A%3CP%3ESharla%26nbsp%3B%3C%2FP%3E%0A%3CP%3EProgram%20Manager%2C%20MSIX%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-334833%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-334833%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20James%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECorrect%2C%20I%20am%20running%20on%20an%20x64%20machine.%20Thanks%20for%20the%20suggestion.%20When%20will%20the%20new%20update%20be%20released%20approximately%3F%20I%20will%20update%20the%20tool%20once%20it's%20available.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMei%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-334655%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-334655%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mei%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20assume%20you%20are%20running%20on%20an%20x64%20machine%3F%20This%20is%20a%20known%20issue%20that%20has%20been%20addressed.%20You'll%20need%20to%20pick%20up%20a%20newer%20update%20of%20the%20tool%20when%20it%20is%20available.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3CBR%20%2F%3EJames%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1599386%22%20slang%3D%22en-US%22%3ERe%3A%20Package%20creation%20failed%3A%20Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1599386%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20receiving%20a%20similar%20error%20(The%20package%20failed%20to%20load%20due%20to%20error%200x8007000E%20%22Not%20enough%20memory%20resources%20are%20available%20to%20complete%20this%20operation.%22.%20This%20occurs%20when%20CPackage%3A%3ALoadFromXML%20fails)%20but%20when%20I%20try%20to%20open%20an%20old%20package%20in%20VS%202017.%26nbsp%3B%20We%20are%20currently%20upgrading%20our%20servers%20to%202019%20SQL%20from%202012.%26nbsp%3B%20These%20packages%20we%20developed%20in%20BIDs%202008%20then%20converted%20to%20DTSX%20in%202010%20data%20tools.%26nbsp%3B%20We%20need%20to%20convert%2Frebuild%20them%20in%20VS%202017.%26nbsp%3B%20any%20help%20on%20this%20would%20be%20great.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F280760%22%20target%3D%22_blank%22%3E%40mei_9%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi, I am currently using MSIX Packaging Tools to package my desktop application to MSIX with Set-up.exe installer. While during the process of MakeAppx.exe, it failed with message "MakeAppx : error: 0x8007000e - Not enough memory resources are available to complete this operation."

 

Can anyone help me with this issue?

 

 

14 Replies
best response confirmed by mei_9 (New Contributor)
Solution

Hi Mei,

 

I assume you are running on an x64 machine? This is a known issue that has been addressed. You'll need to pick up a newer update of the tool when it is available.

 

Thanks!
James

Hi James,

 

Correct, I am running on an x64 machine. Thanks for the suggestion. When will the new update be released approximately? I will update the tool once it's available.

 

Mei

Hi Mei, 

 

We do a release of our tool every few months, and our most recent one was in January. If you are interested in getting updates faster, we recently created a MSIX Packaging Tool Insider Preview Program, which you can join here

 

Best,

Sharla 

Program Manager, MSIX

Is the update that fixes this issue live on the Insider track? I am also running in to this problem every time I try to convert my program.

 

Thanks,

Tommy

It will be in the insider track, but the builds are not yet live.  We expect to have more information in the next week or so on releases to the insider track.

 

John Vintzel (@jvintzel)

Program Manager Lead, MSIX

Hi I've been facing the same issue as well with the current version of the tool (v1.2019.110.0)

 

Are there any updates regarding the release to the insider track? 

 

Dickson

We are working on the insider track.  It should be available towards the end of the month or early March.  Updates will be available on the docs site: https://aka.ms/MSIXToolPreview

 

John Vintzel (@jvintzel)

Program Manager Lead, MSIX

Hello there. Can you provide any workaround, old version for example, till you fix the issue? I need to build package for our customers but can't because of error, it repeats across all windows devices we have.

Hi D4rkV0id,

 

The particular failure hitting x64 machines shouldn't hit on a x86 machine.  If you are seeing x86 specific failures, please share the logs with me to review.

 

Thanks!
James

 

 

Hey, I've faced the same issue, because I was running from Developer Command Prompt, then I switched to cmd and launched manually from "C:\Program Files (x86)\Windows Kits\10\bin\<winsdk_version>\x64" 10.0.17763.0 sdk have no such problem so I was able to build app successfully. Cheers

I'm still facing this error, and I picked up the MSIX packaging tool Store app about a week ago.

Hi Adityag,

 

Could you share some additional details with me to help narrow down the issue?

 

Information that would help me:

1. Are you running x86 or x64 version of the tool?

2. Are you running the conversion locally or on a vm/remote machine.

3. How much physical memory does your conversion environment have? Are you running other programs in the background while conversion is happening?

4. Does the issue repro consistently and with all installers? Or is there a particular installer that is triggering this problem for you?

5. Can you share the conversion log and the specific failure you see?

 

Feel free to file a feedback item via feedback hub or reply to me directly if have data that you prefer to keep more private.  Please review your logs for sensitive content before sharing.

 

Thanks!

James

I am receiving a similar error (The package failed to load due to error 0x8007000E "Not enough memory resources are available to complete this operation.". This occurs when CPackage::LoadFromXML fails) but when I try to open an old package in VS 2017.  We are currently upgrading our servers to 2019 SQL from 2012.  These packages we developed in BIDs 2008 then converted to DTSX in 2010 data tools.  We need to convert/rebuild them in VS 2017.  any help on this would be great. 

 

 

@mei_9