- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am now trying to run an exe on a system that does not have Intel Visual Fortran installed. Unfortunately, I am recieving the following error:
Unhandled Exception: System.DllNotFoundException: Unable to load DLL 'employee.d
ll': The application has failed to start because its side-by-side configuration
is incorrect. Please see the application event log for more detail. (Exception f
rom HRESULT: 0x800736B1)
at ConsoleApp.Program.new_employee()
at ConsoleApp.Program.Main(String[] args)
I have run sxstrace and got the following output:
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = x86
CultureFallBacks = en-US;en
ManifestPath = C:\test3\employee.dll
AssemblyDirectory = C:\test3\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\test3\employee.dll.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Resolving reference Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
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.CRT\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT.MANIFEST.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT\Microsoft.VC90.CRT.MANIFEST.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
ERROR: Cannot resolve reference Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
ERROR: Activation Context generation failed.
End Activation Context Generation.
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = x86
CultureFallBacks = en-US;en
ManifestPath = C:\test3\employee.dll
AssemblyDirectory = C:\test3\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\test3\employee.dll.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Resolving reference Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
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.CRT\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT.MANIFEST.
Are there some redistributable files that need to be attached to my Intel Visual Fortran created EXE?
Unhandled Exception: System.DllNotFoundException: Unable to load DLL 'employee.d
ll': The application has failed to start because its side-by-side configuration
is incorrect. Please see the application event log for more detail. (Exception f
rom HRESULT: 0x800736B1)
at ConsoleApp.Program.new_employee()
at ConsoleApp.Program.Main(String[] args)
I have run sxstrace and got the following output:
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = x86
CultureFallBacks = en-US;en
ManifestPath = C:\test3\employee.dll
AssemblyDirectory = C:\test3\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\test3\employee.dll.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Resolving reference Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
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.CRT\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT.MANIFEST.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT\Microsoft.VC90.CRT.MANIFEST.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
ERROR: Cannot resolve reference Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
ERROR: Activation Context generation failed.
End Activation Context Generation.
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = x86
CultureFallBacks = en-US;en
ManifestPath = C:\test3\employee.dll
AssemblyDirectory = C:\test3\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\test3\employee.dll.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Resolving reference Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
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.CRT\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\test3\Microsoft.VC90.CRT.MANIFEST.
Are there some redistributable files that need to be attached to my Intel Visual Fortran created EXE?
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You also need the Microsoft Visual C++ 2008 redistributables. The easiest way to get that is to use their installer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
You also need the Microsoft Visual C++ 2008 redistributables. The easiest way to get that is to use their installer.
Thanks Steve,
That worked. What about the need for the Intel DLLs? It seems like I need libifcoremd.dll,libifcoremdd.dll, and libmmd.dll on one machine(Vista), but onlylibifcoremd.dll, and libmmd.dll on another machine(XP). What are the guidelines to know which ones need to be installed on which machine? Or are there a set od DLLs that should always be installed as an Intel Fortran run-time so to speak?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It depends on how you've built your application. It's unusual to depend on the Microsoft DLLs but not the Intel DLLs, but that is possible. It looks as if a DLL you built is part of this application.
We're preparing a knowledge base article on redistribution that tells all, plus we'll soon have downloadable redistributable installers like Microsoft.
I usually suggest running Dependency Walker on the EXE or DLL you want to distribute to see what the dependencies are.
We're preparing a knowledge base article on redistribution that tells all, plus we'll soon have downloadable redistributable installers like Microsoft.
I usually suggest running Dependency Walker on the EXE or DLL you want to distribute to see what the dependencies are.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page