The MED-V Blog

The Microsoft Enterprise Desktop Virtualization blog.

Solution: The Virtual PC engine may crash when attempt to start MED-V a workspace

Solution: The Virtual PC engine may crash when attempt to start MED-V a workspace

  • Comments 1
  • Likes

image When you attempt to start MED-V a 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:         
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:         
Computer:     
Description:

The following information was included with the event:

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MED-V Workspace" />
    <EventID Qualifiers="0">0</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-09-22T16:24:30.000Z" />
    <EventRecordID>1372</EventRecordID>
    <Channel>_evt_Application.evt</Channel>
    <Computer></Computer>
    <Security />
  </System>
  <EventData>
    <Data>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()</Data>
  </EventData>
</Event>

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.

Resolution

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.

Hope this helps,

Steve Thomas | Senior Support Escalation Engineer

Comments
  • It does not post any error,It just freezes..!

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