MED-V 2.0 workspace setup fails with a fatal error

Article ID: 2504827 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

When installing the MED-V 2.0 workspace on a Windows 7 machine, a fatal error occurs and in the MED-V install log and the following error is reported:


0810 Decompressing VHD to: C:\ProgramData\Microsoft\Medv\Workspace\MEDV.vhd

0811 A generic exception occured while unpacking VHD

0812 System.IO.IOException: I/O error encountered in attempting to open file ---> Xceed.Compression.CompressionException: Expected end of stream not found

0813    at Xceed.Compression.ManagedDeflateDecompressor.Decompress(Byte buffer, Int32 offset, Int32 count, Boolean& endOfData, Byte& decompressed, Int32& remaining)

0814    at Xceed.Compression.CompressedStream.Read(Byte buffer, Int32 offset, Int32 count)

0815    at Xceed.Utils.Streams.ChecksumStream.Read(Byte buffer, Int32 offset, Int32 count)

0816    at Xceed.Zip.ReaderWriter.ZipReader.ReadItemData(Byte buffer, Int32 offset, Int32 count)

0817    at Microsoft.Medv.WorkspaceCustomActions.VhdUtil.Decompress(Session session, String compressedVhdPath, String vhdInstallationFilePath, Boolean overwriteExistingVhd)

0818    --- End of inner exception stack trace ---

0819    at Microsoft.Medv.WorkspaceCustomActions.VhdUtil.Decompress(Session session, String compressedVhdPath, String vhdInstallationFilePath, Boolean overwriteExistingVhd)

0820 at Microsoft.Medv.WorkspaceCustomActions.CustomActions.InstallVhd(Session session)0821 CustomAction InstallVhdFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

CAUSE

This issue can be caused by antivirus software that is installed on the Windows 7 system if the real-time scanning component is configured to monitor the MED-V files.

RESOLUTION

  1. To resolve this issue, configure the real-time scanning component within your antivirus software to exclude the following files:
    • *.VHD - These represent the Virtual Hard Disk Image files. These will be on all MED-V version 2.0 clients (Windows 7 host machines) running Workspaces.

      *.VSV
       - These represent Virtual PC Saved State files. These will be on all MED-V clients running Workspaces.

      *.MEDV - This is the packed image format used by MED-V version 2.0. These will be present on the MED-V mage Distribution Servers, locally packed images on MED-V Administration workstations, and as pre-staged images (workspaces) on the clients. 

      *.VMC - These represent the Base Virtual Machine Settings File. Will be found on all MED-V v.2 Clients and test/packaging workstations.

      *.VUD - These represent Virtual PC Undo Disk Files. These may appear on testing/packaging workstations when test images are being used to finalize workspace policies.

MORE INFORMATION

For information on adding exclusions or exceptions to a specific Anti-Virus software, please refer to the documentation provided by the vendor. For Microsoft Forefront, please review the following article: http://technet.microsoft.com/en-us/library/bb418942.aspx
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2504827 - Last Review: March 10, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft Enterprise Desktop Virtualization 2.0
Keywords: 
KB2504827

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com