This application has failed to start because the application configuration is incorrect

This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

xxxxxxx-xxxxxx2C-000036B1

This error indicates that certain components that needs to available to the application are not when running a virtualized application within App-V.

VC++ 2005: http://www.microsoft.com/download/en/details.aspx?id=3387
VC++ 2005 SP1: http://www.microsoft.com/download/en/details.aspx?id=5638
VC++ 2005 SP1 ATL security update: http://www.microsoft.com/download/en/details.aspx?id=14431
VC++ 2008: http://www.microsoft.com/downloads/details.aspx?familyid=9b2da534-3e03-4391-8a4d-074b9f2bc1bf
VC++ 2008 SP1: http://www.microsoft.com/download/en/details.aspx?id=5582
VC++ 2008 SP1 with ATL security update: http://www.microsoft.com/download/en/details.aspx?id=15303
VC++ 2010: http://www.microsoft.com/download/en/details.aspx?id=5555
VC++ 2010 SP1: http://www.microsoft.com/download/en/details.aspx?id=8328
Visual J# 2.0: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=4712
VS 2010 F# 2.0 SP1: http://www.microsoft.com/download/en/details.aspx?id=15834

Incase installing one of the above does not remedy the problem – you can manually setup the missing sidebyside-component. Review the error
message from the Application Log – see example below;

Log Name:      Application

Source:        SideBySide

Level:         Error

Keywords:      Classic

Description:

Activation context generation failed for “Q:\ecowin.002\VFS\CSIDL_PROGRAM_FILES\EcoWin\EcoWin.exe”. Dependent Assembly Vinga.vscom90u,processorArchitecture=”X86″,publicKeyToken=”e520fe831c9439c8″,type=”Win32″,version=”1.0.0.55″ could not be found. Please use sxstrace.exe for detailed diagnosis.

Locate the referenced file within the package and copy it to the same folder as the application.
Create the first manifest to tell Ecowin where it should get its above Vinga.vscom90u (named ecowin.exe.manifest)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
</requestedPrivileges>
</security>
</trustInfo>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Vinga.vscom90u" version="1.0.0.55" processorArchitecture="x86"></assemblyIdentity>
</dependentAssembly>
</dependency>
</assembly>

The second manifest telling Ecowin where VScom90u.dll was (named Vinga.vscom90u.manifest)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<noInheritable />
<assemblyIdentity type="win32" name="Vinga.vscom90u" publicKeyToken="e520fe831c9439c8" version="1.0.0.55" processorArchitecture="x86" />
<file name="vscom90u.dll" />
</assembly>

The version, name, type, processorArchitecture, publicKeyToken are all picked up from the original error message.

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *