Legacy ImageMagick Discussions Archive

Just installed ImageMagick 6.5.4 64 bit static version. When i try to run mogrify i get the following message.

"The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail."

Not sure where to look to fix this issue. I have tried reinstalling, but the install always seems to work fine.

Any help would be appreciated,

Thanks,

See http://www.imagemagick.org/script/binar ... hp#windows. Did you install the Visual C++ 2008 Redistributable Package (x64) as it suggests?

Yes, I have installed Visual C++ 2008 Redistributable Package (x64).

I also get the same error message with "identify". "convert" and "imdisplay" work fine, but both "identify" and "mogrify" fail with the side-by-side configuration error message

Thanks,

Very odd that convert works but mogrify fails since they are built side-by-side with the same parameters. Right now we're clueless what the problem could be. We tried reproducing the problem but all ImageMagick programs work fine on our 64-bit system

Not sure if this helps, but this is the detailed info from the event viewer:

Activation context generation failed for "C:\Program Files\ImageMagick-6.5.4-Q16\mogrify.exe".Error in manifest or policy file "C:\Program Files\ImageMagick-6.5.4-Q16\Microsoft.VC90.OpenMP.MANIFEST" on line 11. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC90.OpenMP,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Definition is Microsoft.VC90.OpenMP,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Please use sxstrace.exe for detailed diagnosis.

Thanks,

I'm having the same issue. I'm running the newest x64 static version installed from the Windows executable on Windows 7 64-bit RC1. I also installed the Visual C++ package. I'm not sure if convert failed or not because I didn't notice an output message, the shell just advanced to a fresh prompt. Identify failed with the message referred to by the OP. I ran sxstrace.exe and here is the parsed output file content:

=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = Wow32
CultureFallBacks = en-US;en
ManifestPath = C:\Program Files\ImageMagick-6.5.4-Q16\identify.exe
AssemblyDirectory = C:\Program Files\ImageMagick-6.5.4-Q16\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\Program Files\ImageMagick-6.5.4-Q16\identify.exe.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC90.OpenMP,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Resolving reference Microsoft.VC90.OpenMP,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
INFO: Resolving reference for ProcessorArchitecture WOW64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.OpenMP\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.OpenMP.DLL.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.OpenMP\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.OpenMP.DLL.
INFO: Attempt to probe manifest at C:\Program Files\ImageMagick-6.5.4-Q16\Microsoft.VC90.OpenMP.DLL.
INFO: Attempt to probe manifest at C:\Program Files\ImageMagick-6.5.4-Q16\Microsoft.VC90.OpenMP.MANIFEST.
INFO: Manifest found at C:\Program Files\ImageMagick-6.5.4-Q16\Microsoft.VC90.OpenMP.MANIFEST.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC90.OpenMP.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
INFO: Resolving reference for ProcessorArchitecture WOW64.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.OpenMP.mui\9.0.21022.8_en-US_1fc8b3b9a1e18e3b\Microsoft.VC90.OpenMP.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.OpenMP.mui\9.0.21022.8_en_1fc8b3b9a1e18e3b\Microsoft.VC90.OpenMP.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.OpenMP.mui\9.0.21022.8_en-US_1fc8b3b9a1e18e3b\Microsoft.VC90.OpenMP.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.OpenMP.mui\9.0.21022.8_en_1fc8b3b9a1e18e3b\Microsoft.VC90.OpenMP.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Parsing Manifest File C:\Program Files\ImageMagick-6.5.4-Q16\Microsoft.VC90.OpenMP.MANIFEST.
INFO: Manifest Definition Identity is Microsoft.VC90.OpenMP,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
ERROR: Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC90.OpenMP,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Definition is Microsoft.VC90.OpenMP,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
ERROR: Activation Context generation failed.
End Activation Context Generation.

Just wondering if anyone has been able to recreate this bug.

Can you try with the latest ImageMagick release, 6.5.5-0. We updated the manifests with the latest Microsoft patches and all is well on our three Windows boxes (Vista, Windows 2003, and Windows NT).

Okay, I got it to work! Turns out I needed to install both the x86 and x64 versions of the MS C++ SP1 package. I also installed the newest 6.5.4.Q16 version of ImageMagick.

Thanks for your help!

I experienced similar issue with Windows Vista 32-bit. I installed IM ver. 6.5.5-0 Q16. Same error, except it occurred with any IM app, including convert. I got a slightly different error after I installed the dynamic version. A popup dialog read: "The application failed to initialize properly (0xc0150002). Click OK to terminate the application."

Thanks to this thread, I installed the MS C++ package as indicated below (and at the very bottom of the IM downloads page). It fixed the problem.

At first, I didn't see the "if any problems" note, then I ignored it, thinking I didn't need it since I'm not doing C++ development. Silly me. I'm posting reply here to hopefully help others.

magick wrote:Can you try with the latest ImageMagick release, 6.5.5-0. We updated the manifests with the latest Microsoft patches and all is well on our three Windows boxes (Vista, Windows 2003, and Windows NT).

New version works great. I did not have to install the x86 version of the MS C++ packages, only the x64 ones.

Thanks,