I have also encountered this problem, the workaround:
Scenario One: In the project's properties | Configuration Properties | linker | General, in the Enable incremental link select No. This method blocks the source of the problem, and embeds it directly into the manifest file each time the EXE is generated, rather than the default, depending on the timestamp, to update the manifest file.
Scenario Two: Do not embed the manifest file. In the project's properties | Configuration Properties | inventory Tools | INPUT and Output "embed manifest" to select "No", so that when the EXE file is generated with the build a manifest file (by default, its file name is the full name of the EXE file plus ". manifest"), avoids the problem that the embedded manifest file may fail.
Thank you!
Recently made a project to write a VC6 under the MFC program, the results of uploading to someone else's machine (WIN7) The application of the normal initialization (0XC0150002) failure problem, was thought to be WIN7 problem, then the program copied to a WinXP SP3 program or not.
Why I can on the machine, and other people's machine can't run it?
Start Google, find a solution--when the program is wrong, right-click on "My Computer", then click "Manage", then "Event Viewer", finally See "system", the information is as follows:
(1) Cannot find the accessory assembly Microsoft.VC80.DebugCRT, the previous error is that the referenced assembly is not installed on the system.
(2) Resolve Partial Assembly failed for Microsoft.VC80.DebugCRT. Reference error message: The referenced assembly is not installed on the system.
(3) Generate Activation Context for c:/scanfile/debug/libclamavd.dll failure. Reference error message: Operation completed successfully.
Can judge is LIBCLAMAVD load time out a bit of a problem, looked at its manifest file, its dependent library is Microsoft.VC80.DebugCRT, so the problem is obvious, this DLL is compiled under the VS2005, There is no such environment on the other person's machine, and the application we compiled generates an error due to the lack of the required debug version of the VC runtime.
Workaround: To the installation directory of the vs2005 on my machine, Search for a file with a string Microsoft.VC80.DebugCRT in the name, a total of 3 DLL files (msvcm80d.dll,msvcp80d.dll,msvcr80d.dll) and a manifest file (Microsoft.VC80.DebugCRT . manifest), the problem is solved by copying it to the project executable directory on someone else's machine.
Several points can be found from this question:
(1) Use tools to help locate problems: Event Viewer, depends Walker, etc.
(2) Search efficiency, such as the problem of direct search "application normal initialization failure 0xc0150002" will definitely get a lot of noise information ...
PS: The solution on the net also means that download vcredist_x86, I try not to be very helpful ...
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
Application does not start properly 0xc0150002 solution
