Archive for January, 2011

MED-V v1: Error Message – “Path is not of a Legal Form” when trying to Pack an Image.

January 24, 2011 Leave a comment

When you attempt to pack an image in the MED-V management console, you get the following error:

Operation failed, please try again later.
Error Details: Path is not of a legal form

This can happen if the “PackedImages” sub-directory does not exist beneath the client-side image repository root folder. If you examine the diagnostic logs, you will also notice something similar to the following in the Imagestore.txt file:

Folder PATH listing
Volume serial number is 00000002 2026:EB79
Invalid path – \MED-V IMAGES\
No subfolders exist

If the PackedImages subfolder does not exist, you will get this error as well.

The solution is to manually create the PackedImages directory beneath the MED-V image repository root. The default location on the client is C:\MED-V Images.

App-V: Application Virtualization 4.x NTA Logging Options

January 23, 2011 Leave a comment

In App-V, Network Transport Access logging is turned off by default. It can be turned on for diagnostics when the network is experiencing latency, authentication,  or other connectivity-related issues within a traditional Microsoft Application Virtualization environment using the RTSP (Real-Time Streaming Protocol) transport.By default, the App-V NTA log file is named Sftnta.txt. The Sftnta.txt file is located in the following folder:

%ProgramFiles%\Microsoft Application Virtualization Client\

The following log levels are available:

Level Description
0xFFFFFFFF All logging
0x00000000 No logging
0x0000FFFF All errors
0x00000001 Socket errors
0x00000002 General errors and control flow
0x00000004 RTP errors
0x00000008 RTCP errors
0x00010000 Information
0x00020000 NTA interface
0x00040000 Session creation and deletion
0x00080000 RTSP connection creation and deletion
0x00100000 RTP packets received
0x00200000 RTCP packets received

To enable an NTA log, follow these steps:

1.) Start Registry Editor.

Expand the following registry key:


Create a DWORD value (REG_DWORD) that is named NtaLogMask.

In the Value Data box, type the log level that you want. Then, under Base, select Hexadecimal.

Exit Registry Editor.

Stop the Application Virtualization Client service. Then, restart the Application Virtualization Client  service.

Note: The NTA log causes the Sftnta.txt file to grow fairly large over a short time. This action can adversely affect client performance. Only use the NTA log if Microsoft support recommends that you use the log to diagnose specific client problems. Once you have enabled NTA logging and collected the diagnostic information, please remove the registry entry and restart the Application Virtualization Client  service.

Categories: App-V Tags: , , , , ,

MED-V 1.0: Workspace Fails to Start with “Adjusting VM Window” Message

January 22, 2011 Leave a comment

Has this ever happened to you?

You receive the following error when attempting to launch a MED-V workspace.

“Failed to start Workspace ‘Workspace_name’
“Starting the session failed in the following phase: Adjusting VM Window.”

This issue can arise if there is a dialog box triggered from Virtual PC. This issue has been seen happening with first-time deployments that also involve first time launching of the Virtual PC engine.

A common specific cause of this is found on Windows Vista and Windows 7 where their is an underlying firewall alert that does not appear within regular user contexts but will display immediately with an administrative account. You will see the following message:

“Windows Firewall has blocked some features of this program”

“Windows Firewall has blocked some features of Virtual PC 2007 SP1 on all public, private, and domain networks.”

If you find that when starting the workspace from an Administrative account you get this error, you can enable firewall exemptions for the Virtual PC 2007 SP1 program through the Windows Security Alert dialog box. Once this has been done, a re-attempt of the workspace launch should not get this error again.

A more proactive approach would be to push these firewall exemption rules down via group policy or pre-launch the Virtual PC Console on the workstation as an Administrator and that will also trigger this alert.

Categories: MED-V, VPC Tags: , , , , , , ,

MED-V 1.0 SP1 Error During Image Upload: “The image file already exists on the server”

January 20, 2011 Leave a comment

When you attempt to upload a packed image to an image distribution server within the MED-V management console, you may get the following error:

Failed Uploading image to the server. Please verify that the server is configured correctly.
Error details: The image file <HREF path to file> already exists on the server. Remove the file from the server and try uploading the image again.

You get this error in spite of an existing file not on the image distribution server.

In addition, you will notice 0 byte file markers (labled bitssrv_{GUID}) in the MED-V Server images directory.

This is caused by the directory not having CREATOR OWNER listed in the NTFS permissions list for the directory with its appropriate permissions.

To fix this, you will need to add in the CREATOR OWNER account in the permissions list for the local directory being used by the IIS virtual directory for the MED-V server-based images.

Apply to: Subfolders and files only
Permissions: Allow Traverse Folder/Execute File, List Folder/Read Data, Read attributes, read extended attrobutes, Read permissions

Categories: MED-V Tags: , , , ,

Do not Use App-V for Legacy Locale/Regional Settings Compatibility – Use AppLocale

January 19, 2011 3 comments

Recently, we have had some customers asking us about leveraging App-V to virtualize locales. You may also refer to them as regional settings. Since Windows 2000, the Windows operating system has been multi-locale aware and is able to preserve user-specific locales.

The user locale determines which default settings a user wants to use for formatting dates, times, currency, and large numbers. The user locale is not the language. The only influence the user locale has on the language is on the names of the days and months. For example, if you use the long date format to display “April 22, 2010,” the “April” string will change based on the user locale.

Changing the user locale automatically adds an Input Locale with the default settings for the associated language. I made some serious tests involving easily discernable applications with regional setting differences (locale differences.) While the operating system now support user locales, there are still legacy applications that only recognize system locales. Some of these applications may be hard-coded to correspond to a specific locale.

App-V is language or locale neutral and should have full support for different languages and character scripts, sorting orders, time/date/address formats, various International keyboards and global Input Method Editors (IME), and other locale settings.  This approach is called “single World-Wide binary”.

It is important to understand that while we are locale aware, the actual isolation and sandboxing of the locale regional settings takes place at a system level even though the preferences are stored at the user profile level.  App-V is not expected to make the application localized or culture-aware if it’s not already supported. It won’t make the application to work on a culture that the application does not originally support in the locally installation.

If it were as simple as simple as making registry modifications within the virtual environment, this may would work.  Most locale-aware applications, however  will actually call API’s directly in Windows whether they are user locales or system locales. For example, retrieving  the user locale by calling GetUserDefaultLCID and the system locale by calling GetSystemDefaultLCID. When the application is calling the API directly, it is not reading the registry entries because it is calling the Win32 API directly and it will be querying the registry – but outside the virtual environment.


We recommend that users look to the AppLocale Utility as a possible remediation. The AppLocale utility allows users to run a legacy application without changing to the code-page/system locale needed by that particular application. AppLocale emulates the code-page required by that legacy application without changing the machine’s system locale. This can provide the “sandbox” you may need for the application’s locale.

AppLocale Information:


SCVMM 2008 and 2008 R2: Error when Connecting through VMConnect or RDP: 0x8009030e

January 18, 2011 2 comments

You may notice that you may run into problems with credentials going stale when trying to connect to a Virtual Machine from the SCVMM 2008 or SCVMM 2008 R2 console. When this happens, you get the following error when launching VMConnect.exe to connect to the VM:

An authentication error has occured (Code: 0x8009030e)

Remote computer:

You will also get this error when trying to RDP or connecting through the Hyper-V Management console as well.

The result code 0x8009030e refers to SEC_E_NO_CREDENTIALS in this context or:

“No credentials are available in the security package.”

The security credentials stored by the Hyper-V Host are stale and need to be reset for this particular virtual machines. Other virtual machines may be affected  as well but this setting is actually stored on a per-VM basis.

There is no equivalent way to delete existing stale or missing credentials for Hyper-V hosts in SCVMM. This needs to be corrected on the Hyper-V host.

On the Hyper-V Host, open up the Hyper-V Management Console. Select the host, the select “Hyper-V settings”

In the Hyper-V Settings option, under User Credentials, uncheck “Use default credentials automatically”

Connect to the Virtual Machine again, it will prompt to enter username and password.

Enter credentials, check the box “Remember my credentials”.

VMCONNECT and RDP should be successful. Once verified, return to the Hyper-V Settings option, under User Credentials, check “Use default credentials automatically”

MED-V 1.0: Unexpected Condition Errors During Image Download

January 15, 2011 Leave a comment

When launching a MED-V workspace, you may get the following error after selecting the workspace image to download:

Failed to download Workspace image. Reported error: An error occured while downloading ‘http://server/directory/file.ckm.index&#8217;:
An unexpected condition prevented the server from fufilling the request


This is another internal error which could denote errors in IIS configuration. Most often, it relates to errors in the web.config file.

Fortunately, any mistake barring corruption can be adjusted in the IIS interface on Windows 2008 or Windows 2008 R2. In most cases, it relates to MIME types not being properly configured. Often the *.CKM and *.INDEX MIME entries have not been added or have been added at the parent level, but overridden by a local MIME setting, or not properly propagating.

For more information on various BITS errors you may get when downloading images from a MED-V image distribution server, please refer to the following link:

Categories: MED-V Tags: , , ,