I recently received a report from a customer of mine using App-V 4.5.1.16811 on XenApp 4.5 whereby a user would encounter error 0A-0000E005 whenever the user would try to start an App-V application on XenApp. The error looks like this:
Those familiar with App-V will recognize this as a very common error that usually is due to a corrupt UsrVol*.pkg file in the users App-V user data directory. This user’s problem was a bit different because this user was getting it on all App-V applications. Also, purging the user’s App-V user data directory did nothing to solve the issue.
I did some digging on the Internet and came up with all the usual suspects. Upgrading the client to App-V 4.6 wasn’t an option because it’s a production environment and that would require proper planning / execution. Besides, only this user was having problems. There were approximately 2k other users that were happily running their apps on App-V 4.5 all day long.
So I poked around this user’s configuration a bit more. While the user was logged on, I then purged their HKCU\Software\Microsoft\SoftGrid\4.5\Client\Applications list. After doing so, the error message changed to a 14-00000003 error message as seen below.
Progress, as in I changed the error, but unfortunately did not fix the problem. One other thing that I noticed that was strange about this user is that they were unable to logoff successfully from Citrix. It seemed like userinit.exe was never properly ending and therefore their sessions would get stuck on the XenApp server.
This XenApp environment uses Flex Profile with only AppData folder redirection (not my favorite, but I digress). So I started going after the only thing that made this user any different from anyone else and that which would follow this user from Citrix server to Citrix server….our old friend AppData.
Rather than purge app data in it’s entirety I decided to selectively delete the AppData contents until I could narrow down what was causing the issue.
The result? The Microsoft Crypto folder appears as though it may have been corrupt. Once I deleted it, she was all set. It solved both the App-V error as well as the session hang/logoff issues. If you look on the Internet you’ll find scads of problems related to the Crypto folder being corrupt. Specifically with respect to App-V, I haven’t seen any, but chalk this up to one now. 😉
Hope this helps someone else out there.
Tim Mangan says
Had a similar issue with a customer on 4.6, no apps launching just last month. Their error was 14-00000005 and 03-00007003. Issue was a profile server failure but once that failed over to a new server logons stopped having the problem. In that case, there wasn’t enough time to track down exactly what the permission issue (005) was, but the bottom line was that these things can affect App-V and look like App-V errors, when it is just bad profile / redirection biting.
Andrew Morgan says
Hi Shawn!
Thanks for sharing, out of pure nerdy curiosity was the customer using RTSP or RTSPS?
Shawn Bass says
@Andrew – Neither. Independent File Streaming so it was going over SMB. And the SMB source path was fully accessible so that error is irrelevant in this case.
Pål Røtnes says
I had a 0A-0000E005 error from a user after updating a package. Worked for several other, not her.
Tried clearing the pkg. Tried unloading, clearing and deleting the package from the server. Found this article and tried deleting the crypto folder. No luck… Tried nuking her entire profile, local on TS and roaming, and clearing the pkg again. Still did not help. At this point there should not be anything left to cause this, but somehow there is. Luckily this was a very simple user so I made a new user for her. Application worked right away. I copied her home folder and she was happy user again. Me? I’m a confused a slightly more irritated administrator. What could cause this?