The World Simplified is a Virtual World

The Adventures of Justin Zarb and Dave Falkus in the Virtual Jungle

App-V error code 06-0000000E Explained

App-V error code 06-0000000E Explained

  • Comments 1
  • Likes

Hi all,

Recently I’ve been onsite with a few customers and the following App-V error keeps occurring when a user tries to launch an App-V application.

clip_image001

Research

If you search on the internet you will find the following KB that we (Microsoft) provide to our customers to troubleshoot this message.

Error message in the Microsoft SoftGrid Client when you try to start an application: "Error code: xxxxxx-xxxxxx06-0000000E"

http://support.microsoft.com/kb/930633

As you can see this is referencing our previous version Softricity, the resolution in the article is below.

To resolve this issue, use Registry Editor to verify that the path of the SoftGrid "user data" directory is valid. To do this, follow these steps:

1. From the SoftGrid Client, start Registry Editor.

2. Locate and then expand the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Softricity\SoftGrid Client\CurrentVersion\Configuration

3. Right-click UserDataDirectory, and then click Modify.

4. Review and, if it is necessary, correct the path that is specified in the Value data box.

5. Exit Registry Editor.

If you try to start an application and you do not have access to the path that is specified in the Value data box, the application will not start, and you will receive the errors that are mentioned.

As we are using App-V 4.6 SP2 the same error occurs but when we check the new registry location the default location is %APPDATA%

X86 Client - HKLM \SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration

X64 Client - HKLM\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\Configuration

clip_image003

Troubleshooting Steps

So what did we do to figure out what the issue is?

Firstly as the user we opened a command prompt and ran a “set” to check the environment variable for %APPDATA% and the following was returned:

APPDATA=C:\Users\Dave\Appdata\Roaming

This is what we expected so where do we go now? Next we though lets check the App-V client is pulling the correct variables when the application launches. We enabled verbose logging by running the following command:

Sftlist /verboselog

We then reproduced the issue and the log pulled the correct value as shown.

[05/22/2013 12:37:55:041 SWAP VRB] {hap=12:app=Remote Desktop Connection Manager 2.2.2.426:tid=A88:usr=Dave}

SetEnvironmentVariable(name=APPDATA, value=C:\Users\Dave\AppData\Roaming)

As a note, to reset to log back to default run a sftlist /infolog so the log doesn’t grow rapidly and affect the clients performance.

Where do we go from here?

Well, how many people know that the App-V client has two configuration locations in the registry?

As above we have the Local Machine keys depending on the Client version installed:

X86 Client - HKLM \SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration

X64 Client - HKLM\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\Configuration

But we also have configuration on a per user basis in the following location:

HKEY_CURRENT_USER\Software\Microsoft\SoftGrid\4.5\Client

clip_image005

Within this part of the registry there is a key UserInfo which also holds a string name called “DataDirectory”. So when a user launches an application the App-V client reads the UserDataDirectory key from HKEY_LOCAL_MACHINE and then sets the “DataDirectory” value under HKEY_CURRENT_USER. If this path isn’t available, incorrect or the user doesn’t have write access to this location then the 06-0000000E error will occur.

This value was a path wasn’t a valid location which meant the application wouldn’t launch. We changed the value of the key to the correct %APPDATA% environment variable stated above and then guess what the application launched.

Conclusion

I hope this helps with troubleshooting this error code and explains why this error can occur.

David Falkus | Premier Field Engineer | Application Virtualization

Comments
  • Thanks David. I just the exact same error and your blog helped me nail the issue in no time :)

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment