KBJust a quick FYI on a new KB we published this morning:

=====

Symptoms

After applying Microsoft Security Update KB2647174 Microsoft Access virtualized with Microsoft Application Virtualization (App-V) may fail to launch with an error similar to the following:

Application Virtualization Error

The Application Virtualization Client could not launch Microsoft Access 2010 v1.
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
Error code: 4604EE8-1B401F2C-000036B1

Other Microsoft Office components (Word, Excel, etc.) load successfully.

Cause

KB2647174 inserts new side-by-side assemblies that may conflict with those contained in packages that have been sequenced using older versions of the Microsoft Visual Studio 2008 runtime. This issue only occurs on applications sequenced with Microsoft App-V 4.6 and below. App-V 4.6 SP1 is not affected. In addition, this issue only affects Office installations sequenced on Windows XP. Windows 7, Windows Vista, and Windows Server 2008 and above are not affected.

Resolution

To resolve this issue, either:

1. Resequence the package using the 4.6 SP1 (or greater) Sequencer

-or-

2. Open the package for upgrade in the Sequencer and locate the file <package root>\office14\msaccess.exe.config.

In the App-V 4.5 Sequencer, Select File then Open for Package Upgrade.... When the package loads, select Tools then Sequencing Wizard to begin monitoring.

In the App-V 4.6 SP1 Sequencer, choose File then Open... then select Update Application in Existing Package. Follow the wizard until you reach the Select Installer screen. There, choose Perform a custom installation. and click Next. Click Run... and then choose Notepad.exe.

Once the package is loaded, open msaccess.exe.config in Notepad and change these lines:

<?xml version="1.0"?><!-- Microsoft AppVirt generated config file.--><configuration>
<windows>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly><assemblyIdentity type="win32" name="Microsoft.VC90.CRT" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<bindingRedirect oldVersion="9.0.30201.0-9.0.30729.4148" newVersion="9.0.30729.4148"/>
</dependentAssembly></assemblyBinding>
</windows>
</configuration>

To

<?xml version="1.0"?><!-- Microsoft AppVirt generated config file.--><configuration>
<windows>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.CRT" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<bindingRedirect oldVersion="9.0.20718.0-9.0.21022.8" newVersion="9.0.30729.4148"/>
<bindingRedirect oldVersion="9.0.30201.0-9.0.30729.4148" newVersion="9.0.30729.4148"/>
</dependentAssembly></assemblyBinding>

</windows>

</configuration>

Save the file, then save the package and redistribute.

=====

For the most current information please see the following KB:

KB2541008 - Microsoft App-V 4.6 error 2C-000036B1 when launching Access after applying KB2467174

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

clip_image001 clip_image002