Ever since my blog on Adding and Publishing a Package in Standalone Mode I have noticed an increased number of people hitting this issue when trying to add/publish their App-V packages. Having grappled with what the cause of this could be for the last few weeks, bouncing ideas around with some of our App-V people internally it looks like I am starting to understand why this happens, I thought I would share these findings with you all…
Please be aware I am still in the investigation phase with this so the following points apply:
- This may not be the only cause for this error code
- This might not be the fix for everyone facing this error code
- Please do let me know if this works for you using the comments form below, would be great to hear from you!
Here’s what you are probably seeing if using standalone mode when you try and add the package:
If using full infrastructure (App-V Management Server) you will notice your packages do not publish, using either method you will probably see these messages in the event viewer logs:
What seems to be in common in all packages that throw up this issue is they have the UserProgramFiles directory in the package:
By deleting this from the package (I have even seen that just deleting the Common subfolder works too), then saving the package, it then can be added to the client machine:
Not sure. I am investigating further. Meanwhile I’d love to hear how you are getting on with this error code and if you found the above works for you…..
I have been receiving this error when trying to package JDK 6. This did not solve my problem though (there is no UserProgramFiles folder) :-(
This did solve my problem with R 3.0.0. Thank you very much for the update to the original post.
@Adam - I have been unable to replicate this issue with Java EE SDK 6 Update 4: www.oracle.com/.../java-ee-sdk-6u3-jdk-6u29-downloads-523388.html Can you provide more information about what you distribution you are using?
@Mark - No problems, it was your comments that helped me investigate this issue further, thanks for sharing your experiences!
I am using Java SE Development Kit 6u45 x64 available at: www.oracle.com/.../java-archive-downloads-javase6-419409.html
I figured out that if I set "C:\Program Files\Java\jdk1.6.0_45" as the Primary Virtual Application Directory (also the default installation path), it does not seem to take correctly and my package doesn't work and I get the error. If i set the PVAD to say "C:\JDK 6 (64-bit)" and install there it seems to work ok. Also note that I am sequencing it as Middleware (not sure if that matters or not).
I ran into the same suggestion here: (social.technet.microsoft.com/.../appv-5-error-when-trying-to-import-a-package-0c80070057) and it certainly fixed the problem I was having.
Same type errors, but I don't have a UserProgramFiles to delete. I hope this is fixed in SP2 and that SP2 is released soon. I can't see how these random malfunctions are acceptable at all. There should at least be a hotfix out by now. This actually works in our parallell SoftGrid 4.1 environment, but broke for App-V 5.
I understand this is definitely an annoying one! Can you check the package file system inside the package editor under VFS and compare this to what you see in the actual .appv, if you see any inconsistencies delete the files or folders from within the package editor and see if that fixes the issue.
SP2 is not far away!
Was having the same issue. Removing it from the VFS worked.
Good to hear!
Saved my head and the wall next to me :-). thanks Thamim. I wonder if you got to the bottom of it?