Archive

Archive for March, 2011

Important notice for those of you building C++ projects with App-V virtualized Visual Studio 2008 . . .

March 31, 2011 1 comment

. . . if you build it with debugging enabled it will not complete and will throw an error in the console window.

When using a virtualized instance of Visual Studio (sequenced following the instructions at http://technet.microsoft.com/en-us/appvirtualization/dd334515.aspx)

When users build a C++ project in Visual Studio 2008 with debugging enabled the compiled program will not run and gives an error in the console window and/or the interface.

ERROR in Visual Studio Interface:

 “Unable to start program ‘path_to_program\program_name.exe’.”

“This application has failed to start because the application configuration is incorrect. Review the manifest file for possible errors. Reinstalling the application may fix this problem. For more details, please see the application event log.”

ERROR in console window:

“The system cannot execute the specified program.”

[To reproduce this specifically:

Create a new empty C++ project in Visual Studio. Write any compilable and runable code. Build the project (F7). Run the project without debugging (CTRL+F5) ]

 This problem does not occur when the project is set to release mode – only in debug mode.

This is caused by the debug run-time modules not being captured inside the virtual application package because of how the Application Virtualization side-by-side process works during sequencing. The debug runtimes are not used, so they are left out.

In order to work around this, the developer will need to install the debug runtimes on the local machine. They can be built out of Visual Studio 2008 pretty easily as follows:

 1. From Visual Studio, navigate to “File” – “New” – “Project.”

2. Select and expand “Other Project Types,” then “Setup and Deployment.”

3. In the Visual Studio Templates area, select “Setup Project.” Click “OK.”

4. In the Project window, Right-click “Setup1” and select “Add” – “Merge Module.”

5. Select all debug runtimes desired from the list.

6. Click Open

7. Right-click Setup1 and select “Build.”

8. Execute the project. It will install the modules you selected. 

Advertisements

MED-V: How to Configure the MED-V v1 Client to Generate a User Dump on an Exception


When the Virtual PC Engine, Workspace, or MED-V v1 Client crashes or encounters an exception when deployed in a MED-V v1 environment, there is no user dump created or a minidump listed in Windows Error Reporting.

This default behavior is by design. The client is not configured by default to generate dump files on unhandled exceptions.

There is an option to turn UEF (Unhandled Exception Filtering) on but it requires a modification to the registry on the MED-V client.

To enable UEF User Dump generation, please do the following:

1.) Open Registry Editor.

2.) Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Kidaro

3.) Create the following values (New – DWORD Value)

Name: DumpType
Data Type: dword
Value: 3ff

Name: GenerateDumpOnException
Data Type: dword
Value: 1

Name: WriteEventLogOnException
Data Type: dword
Value: 1

Name: DisplayMessageOnException
Data Type: dword
Value: 1

4.) Exit Registry Editor

5.) Restart the MED-V Client Service.

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

Virtual PC 2007 SP1 x64 edition installs into the Program Files(x86) directory


When you install Virtual PC 2007 Service Pack 1 on a computer running Windows Vista or Windows 7 x64 edition, the installation appears in a subdirectory of the “Program Files (x86)” directory. Additionally, the VirtualPC.exe process displays in Task Manager as a 32-bit process.

When Virtual PC 2007 is installed on a 64-bit host Operating System it installs to the 32-bit program files directory. This is because unlike Virtual Server, Virtual PC 2007 is a 32-bit application which uses 64-bit drivers when necessary.

In order to run on a 64-bit host Operating System the drivers must be 64-bit themselves, but the only benefits of making the application 64-bit is the ability to access larger amounts of memory and to run more virtual machines at the same time. While both of these things are very important for Virtual Server, they are not as important for Virtual PC.

This works as designed for hosting 32-bit operating systems as guests on x64 hosts.

Categories: Virtualization, VPC Tags: , , , , , ,

MED-V v1.0: Virtual PC Engine Crashes


When you attempt to start a MED-V 1.0 workspace using a test image or a deployed image, the Virtual PC engine may crash and generate a Fault Report using Windows Error Reporting. Subsequently, the MED-V Workspace will fail to start.

The Virtual PC engine crash will show the following fault:

{virtual pc.exe, 6.0.210.0, unknown, 0.0.0.0, ffff08ef}

You will also see the following event in the Application Event Log:

Log Name: Application
Source: MED-V Workspace
Date: 9/22/2009 12:24:30 PM
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: CSS-W013
Description:

The following information was included with the event:

Failed intializing the service log: System.TimeoutException: Timed out waiting for the shared memroy client to initialize
at Kidaro.Foundation.Log.PrettyLogProxy.InitializeSharedMemoryClient()
at Kidaro.Foundation.Log.PrettyLogProxy.Start()
at Kidaro.Workspaces.Service.WorkspaceService.ServiceStartThread()

Failed intializing the service log: System.TimeoutException: Timed out waiting for the shared memroy client to initialize
at Kidaro.Foundation.Log.PrettyLogProxy.InitializeSharedMemoryClient()
at Kidaro.Foundation.Log.PrettyLogProxy.Start()
at Kidaro.Workspaces.Service.WorkspaceService.ServiceStartThread()

Cause

This can happen if the MED-V Workspace (the workspace installation) binaries have been installed along with the client on the physical host machine. The MED-V workspace installer should only be run inside the virtual machine being used to create the workspace.

To resolve this issue, please do the following:

1.) Uninstall both the MED-V Workspace and the MED-V Client.

2.) Reinstall the MED-V Client.

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

SCVMM 2008: Reports generated from OpsMgr 2007 SP1 in Japanese change back to English after a few days


You have an environment where SCVMM 2008 is installed with Operations Manager integration. When you run a report using the Japanese version of Operations Manager, the initial reports show up properly in Japanese. After about two days, when you go to run the report again, you will find the language is changed back to English.

This has confirmed to be a problem on the SC Operations Manager 2007 side. It has been a confirmed to be a bug in 2007 SP1.

There is no workaround although the issue has been fixed for System Center Operations Manager 2007 R2.

There will be no hotfix for SP1.

The best resolution is to upgrade the Operations Manager environment to 2007 R2.

App-V 4.5: The App-V Management Server Service fails to start with Service-Specific Error 268480320

March 8, 2011 4 comments

You may get the following error message when you try to start the App-V Management Server service:

“Windows could not start the Application Virtualization Management Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 268480320

System Event Log will show the same error under Event ID 7024.

You will also see the following error in the SFT-SERVER.LOG file on the App-V Management server:

SW_ProtocolServer::ConfigureLogPipeline – – – – 1 44864 “Unexpected Error creating Log Pipeline.

This relates to the Provider Pipeline Logging Configuration which is configured at the Server Group Level.

You may also see a false positive log message stating that the server was unable to connect to the data source. The server is able to connect, but the database records it is reading in for the pipeline (to the MESSAGE_LOG table) is incorrect.

To resolve and prevent this issue, it will require correct log pipeline configuration. This is done as follows:

1.) Launch the Application Virtualization Management Console.

2.) From the Server Groups node, right-click the Server Group your App-V Server belongs to and select “Properties.”

3.) Click on the “Logging” tab.

4.) Select “SQL Database” and select “Edit.”

5.) Make necessary modifications under these considerations:

– If the SQL Server you are connecting to contains multiple instances, you will need to select “Dynamically Determine Port.”

– If the SQL Server you are connecting to resides on the default instance, select port 1433 and disable “Dynamically Determine Port.”

– If the SQL Server you are connecting to is using a non-standard port, specify the port and disable “Dynamically Determine Port.”

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

MED-V 1.0: Single Sign-on (SSO) fails even though it is properly set in the Workspace Policy

March 3, 2011 3 comments

MED-V offers a feature where persistent workspaces can leverage a host machine or domain account for single sign-on. This property is enabled only when Workspace is persistent is selected.

When you configure Single Sign-on for a workspace policy in the MED-V management console (per guidelines specified here: http://technet.microsoft.com/en-us/library/ee348992.aspx) you may find that the workspace will either:

– Logon automatically using the local administrator account.

or

– Prompt for a local login inside a Virtual Machine Window (especially if domain joined).

This can be caused by one of the following:

– A failure to either set the VM setup script’s “Join Domain” component properly in the management console.

– A failure to join the domain due to an underlying issue

– Not including the “Disable Auto-login” component as the last step in the VM setup script.

If this is happening you will need to verify the following:

– If the “Join Domain” option is not included, please add it per the guidelines in the following link: http://technet.microsoft.com/en-us/library/ee348997.aspx

– If there is a failure to join the domain or connect to the domain, it is best to check the System Event Log in the workspace’s guest OS. There are several ways to access this event log from MED-V. A common way is to publish the Start Menu or a Command Prompt (CMD.EXE) within the workspace policy and launch the Event Viewer directly. Refer to the following link for publishing applications: http://technet.microsoft.com/en-us/library/ee348923.aspx

– The “Disable Auto-login” component should be added as the last step in the VM setup script following the “Join Domain” component.

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