App-V 5.0 Standalone Mode - Adding and Publishing a Package
This post has moved here
Comments
Anonymous
January 01, 2003
Can you confirm that this is for more than one package or is this issue package specific? Also have you installed the hotfix here: support.microsoft.com/.../2799153Anonymous
January 01, 2003
Check out this post if you are facing the issues discussed: blogs.technet.com/.../0c80070057-app-v-error-code.aspxAnonymous
January 01, 2003
So far I've just tried the one package: a small open-source application called Workrave (http://www.workrave.org) I chose it as I believed, perhaps erroneously, that it was a nice and simple application that I'd have no issues sequencing. I will try something even simpler and let you know how I get on.Anonymous
January 01, 2003
Hi Luke, Is this application specific or are you seeing it across different packages?Anonymous
January 01, 2003
Mark, thanks for your comment, it really does help to know who else is facing this issue and with which packages. I have just downloaded and sequenced the same package and hit exactly the same issue. I am now investigating this internally to see if we can identify a root causeAnonymous
January 01, 2003
Is this issue package specific or is it affecting all applications? Does the add command work fine and the error occur for the publish?Anonymous
January 01, 2003
Hi, the commands are exactly the same as detailed above for the updated package. Also read here for more information: http://blogs.technet.com/b/virtualvibes/archive/2014/02/18/differential-upgrades-with-app-v-5-0.aspxAnonymous
January 01, 2003
Thanks for sharing! A useful combination of PowerShell commands to quickly test packages.Anonymous
January 01, 2003
PS: I did check the AppV Client Event Log but all it contained was: <Event xmlns="schemas.microsoft.com/.../event">
- <System> <Provider Name="Microsoft-AppV-Client" Guid="{E4F68870-5AE8-4E5B-9CE7-CA9ED75B0245}" /> <EventID>1008</EventID> <Version>1</Version> <Level>2</Level> <Task>8</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000100</Keywords> <TimeCreated SystemTime="2013-05-08T14:20:06.383335300Z" /> <EventRecordID>2</EventRecordID> <Correlation ActivityID="{02AB7C68-F800-0005-46C3-7170EF4BCE01}" /> <Execution ProcessID="8024" ThreadID="7644" /> <Channel>Microsoft-AppV-Client/Admin</Channel> <Computer>win7sp1-x64</Computer> <Security UserID="<REMOVED>" /> </System>
- <EventData> <Data Name="Package">{3E2480EF-37C9-4B17-84BC-1B38A8D751EB}</Data> <Data Name="Version">{47C75130-7167-4297-B60C-C7F2101F5B62}</Data> <Data Name="Folder">C:ProgramDataApp-V3E2480EF-37C9-4B17-84BC-1B38A8D751EB47C75130-7167-4297-B60C-C7F2101F5B62</Data> <Data Name="ErrorHigh">1279269900</Data> <Data Name="ErrorLow">2147942487</Data> </EventData> </Event>
Anonymous
January 01, 2003
Thanks, great to know it has been useful!Anonymous
January 01, 2003
I am also getting this error on two different applications. The event log for App-V isn't any help even after enabling all logs.Anonymous
January 01, 2003
This post has been particularly in helping me test sequenced applications.Anonymous
January 01, 2003
Hi, Can you confirm when you get this error? At add or at publish? Also are you using the -DynamicUserConfigurationPath argument? Please paste me the commands you are using so I can verify....Anonymous
January 01, 2003
Hi Pat, your right that in App-V 4.x we had the "AllowIndependentFileStreaming" key in registry which had to be set to 1 in order to stream directly from a file location. This is no longer the case in 5.0. Standalone mode in App-V 4.x and 5.0 is fully supported for production use and we have seen some customers really embrace standalone mode beyond just testing packages. I know some customers using SCCM 2007 are using the methods described above to publish App-V 5.0 packages too.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Hmm... I've just sequenced a small utility I wrote (an executable and a manifest packaged as a .msi) and that seems to have worked just fine... PS C:Windowssystem32> Add-AppvClientPackage -Path '\domainsoftwarepublicMyIP_1.0_x86MyIP_1.0_x86.appv' PackageId : 32aa1202-f82c-44ee-8095-aee6e34edc70 VersionId : 37de4c04-a147-4b16-a1c1-c0bc25a40db2 Name : MyIP_1.0_x86 Version : 0.0.0.1 Path : \domainsoftwarepublicMyIP_1.0_x86MyIP_1.0_x86.appv IsPublishedToUser : False UserPending : False IsPublishedGlobally : False GlobalPending : False InUse : False InUseByCurrentUser : False PackageSize : 548047 PercentLoaded : 50 IsLoading : False HasAssetIntelligence : False PS C:Windowssystem32> Publish-AppvClientPackage MyIP_1.0_x86 PackageId : 32aa1202-f82c-44ee-8095-aee6e34edc70 VersionId : 37de4c04-a147-4b16-a1c1-c0bc25a40db2 Name : MyIP_1.0_x86 Version : 0.0.0.1 Path : \domainsoftwarepublicMyIP_1.0_x86MyIP_1.0_x86.appv IsPublishedToUser : True UserPending : False IsPublishedGlobally : False GlobalPending : False InUse : False InUseByCurrentUser : False PackageSize : 548047 PercentLoaded : 50 IsLoading : False HasAssetIntelligence : True Maybe the issue is with the application I am trying to package? I shall have to try a few others and see if I've just randomly picked one that has an issue... Luke PS: Thanks for taking the time to reply! :)Anonymous
January 01, 2003
Hi Sambit, Looks like a syntax error, can you share the commands you are running?Anonymous
January 01, 2003
Now that's interesting, I have just sequenced the same application and delivered it via standalone mode and hit the same exact error! Looks like this issue is specific to some apps, I will investigate further...Anonymous
March 18, 2013
Great post. Very useful for testing App-V packages.Anonymous
March 29, 2013
Thamim, For the life of me, i cannot get this to work. i keep getting a 0c80070057 error, application virtualization service failed to complete requested operation. operation attempted: configure appv package. Error module: streaming manager. internal error detail: 4c401c0c80070057. the forums at microsoft do not have a fix. these errors hardly come up on search engines. people still have this issue. i have no idea why i cannot get the clients to download and install update publish packages. clients are unsuccessful. ive taken every troubleshooting measure and applied it and still same result.Anonymous
April 05, 2013
In App-v 4 there were some registry entrires that needed to be modified. Is this not the case with App-v 5.0? Also, is standalone mode supported for production use?Anonymous
April 18, 2013
Hi Thamim, I'm also got the same error "0c80070057 " during installation.(standalone mode installation).any solution on this?Anonymous
May 15, 2013
The comment has been removedAnonymous
July 10, 2013
The comment has been removedAnonymous
July 30, 2013
Great post. To quickly test pacakges on a local client I use the following commandline Add-AppvClientPackage -Path "\servercontentpackage.appv" | Publish-AppvClientPackage -Global | Mount-AppvClientPackage -Verbose This commandline, imports, published global and loads (streams) the package to 100%.Anonymous
November 22, 2013
The comment has been removedAnonymous
December 02, 2013
I would like to know if there is any way to uninstall an AppV package manually. Thanks.Anonymous
December 02, 2013
Of course Arka, you can use the unpublish-appvclientpackage and remove-appvclientpackage command to achieve this.Anonymous
February 23, 2014
Nice post ,
But when we want to publish the package and updated package on the client machine from the server .
Can you please let me know the process and cmdlets for this process
Tnq Inadvance !