Problem with MFC Application

[maverick786us]

I have an MFC Dialog based application developed in Visual Studio 2008. Everything is perfectly fine. Except, when I run that application in a fresh PC, where, there is no Visual Studio or any other thing, it crashes with this error message.

Problem signature:
Problem Event Name: APPCRASH
Application Name: CodeGen3.0.exe
Application Version: 1.0.0.1
Application Timestamp: 56012e6d
Fault Module Name: CodeGen3.0.exe
Fault Module Version: 1.0.0.1
Fault Module Timestamp: 56012e6d
Exception Code: c0000005
Exception Offset: 00001af5
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 16393
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Can someone help me in resolving this issue?

[Arjay]

You are probably missing the MFC redistribution dlls for the version of VS that you created the program with. See http://www.microsoft.com/en-us/downl....aspx?id=26368

To find out if missing dlls are the problem, run the depends tool on the target machine - http://dependencywalker.com/

[maverick786us]

You are probably missing the MFC redistribution dlls for the version of VS that you created the program with. See http://www.microsoft.com/en-us/downl....aspx?id=26368

To find out if missing dlls are the problem, run the depends tool on the target machine - http://dependencywalker.com/

Even after using this Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update the result is still the same

[maverick786us]

In fact before using the service pack, I created a setup and deployment package (.MSI) so that it will automatically get the dependency and integrate it within the MSI File, but it didn't work

[VladimirF]

I don't think it's a missing library; the Exception Code is Access Violation...
Could you try to install the Dependency Walker on that system, load your application there and do Profile -> Start Profiling?
Does it give you a hint on what function is failing?
A "fresh" PC can differ from you dev system in many ways. For example, there a data file may be missing, and you do not check a return value when opening that file.

[maverick786us]

I don't think it's a missing library; the Exception Code is Access Violation...
Could you try to install the Dependency Walker on that system, load your application there and do Profile -> Start Profiling?
Does it give you a hint on what function is failing?
A "fresh" PC can differ from you dev system in many ways. For example, there a data file may be missing, and you do not check a return value when opening that file.

These are the DLLs that dependency walker found missing.

API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

Does this mean that these DLLs should be there with the EXE file in the fresh PC?

[VictorN]

These are the DLLs that dependency walker found missing.



Does this mean that these DLLs should be there with the EXE file in the fresh PC?

Yes, because your application was supposed to use some functions/data from these DLLs