Issue With App-V 5 and Java Mission Control

I recently encountered a strange error when trying to sequence the Java JDK. It has a shortcut named Mission Control, which produced the following error message when trying to launch on the client:

JDK Mission Control Error
Invalid Configuration Location – The configuration area at ‘C:\Users\testadmin\.eclipse\810663534\configuration’ is not writable. Please choose a writeable location using the ‘-configuration’ command line option.

This folder is present in the VFS and should be writeable. I tried various tricks such as enabling full VFS write permissions and setting the PVAD to this location, but to no avail. I first thought it might be something to do with the folder name starting with a dot – Windows doesn’t really like this, for instance it won’t let you create such a folder through Explorer. Busting out Procmon however showed that the application is trying to create and delete a .dll file in this folder to see if it’s writable; and this file extension is read-only in the VFS (see here for more info on which file types are blocked). Here is the Procmon trace:

JDK Mission Control - without local folder

Since this folder is in the VFS, I would not expect to see the first few PATH NOT FOUND entries, so perhaps there is something else going on here that’s forcing it to look at the real file system instead of the VFS. The app works however if I create the folder on the local file system:

JDK Mission Control - with local folder

So, the simplest solution to this is to not launch the Java Mission Control shortcut during sequencing! This way the folder never gets created or captured, and it will create the folder on the local file system automatically.

This issue is not just limited to the Java JDK. I have seen a forum post where the same issue affects Eclipse, and I also happened to run into the exact same issue on two other applications in the same week. The error message is identical, and they all appear to have some code based on a modified version of Eclipse.

 

5 responses on “Issue With App-V 5 and Java Mission Control

  1. Mikael Berglind

    Hello Dan!

    Did u find a solution for this java eclipse problem

    1. Only the solution described in the article, I’m afraid I haven’t come across this or any similar applications since.

    2. Julie

      Hi Mikael,

      There may be two options. I’ve only tried option 1 for Eclipse C++ and Java versions:

      1) Modify the config.ini file: replace @user.home/workspace entry with a drive letter path

      2) Define a user environment variable
      Reference: http://www.timehat.com/javas-user-home-is-wrong-on-windows/

      I’ve seen the reference to the environment variable before possibly on the Eclipse site but I had already sequenced the applications before searching for a cleaner alternative.

      Julie

  2. Pingback: The Microsoft App-V 5.0 Sequencer and Client Troubleshooting Guide - The Official Microsoft App-V Team Blog - Site Home - TechNet Blogs

  3. Peter_Rdam

    Hi all,

    I have two apps which generated this error. Archi and SAP BO Designstudio. Basically this specific error is easy to resolve.

    – During sequencing, just start the application for the first time
    – Go to the installdir of the application
    – Find a folder with the name ‘Configuration’. Open the config.ini file from that folder
    – Add the line: osgi.configuration.area.readOnly=true and save the ini file.
    – Finish the sequencing process

    After doing this, both of the apps started without errors. But, due to checking the error log of SAP BO Designstudio, I had to make another change in the config.ini. I also had to replace the property ‘osgi.instance.area’ with ‘osgi.instance.area.default’. Now, it runs without any errors.

    I think with some help of the documentation of help.eclipse.org, it should be possible to get other applications fully working within the VFS.

    http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html

    Note: When using the readOnly property, the bundles (folders) as configured in the ‘osgi.bundles’ line must exist in the configuration folder. So if you are using the -configuration switch, be sure those bundles are present on that location.

Leave a Reply