the application was unable to start correctly (0xc0150002)

Question

It was developed on Visual Studio 2005.  I am not able to debug this issue coz it cannot even reach the first line of _tWinMain, where I set a breakpoint.

Answer 1

Maybe this situation?

https://community.rti.com/kb/how-resolve-error-application-was-unable-start-correctly-0xc0150002-click-ok-close-application

Answer 2

The explanation of status code 0xC0150002 advises to check the event log for additional information.

So what did the event log contain regarding this error?

Answer 3

Sorry for the very late reply.

Activation context generation failed for "MessManagerLibrary.dll".Error in manifest or policy file "E:\ws20.....\debug\Microsoft.VC80.DebugCRT.MANIFEST" on line 4. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC80.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.6195". Definition is Microsoft.VC80.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762". Please use sxstrace.exe for detailed diagnosis.

Where to get this "6195"?

Answer 4

Sorry for the late reply.

It was almost the same error, but after installing vs2005 sp1, got the blow error:

Activation context generation failed for "MessManagerLibrary.dll".Error in manifest or policy file "E:\ws20.....\debug\Microsoft.VC80.DebugCRT.MANIFEST" on line 4. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC80.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.6195". Definition is Microsoft.VC80.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762". Please use sxstrace.exe for detailed diagnosis.

Where to get this "6195"?

Answer 5

It was almost the same error, but after installing vs2005 sp1, got the blow error:

...Where to get this "6195"?

I don't know, presumably it's a later SP release?

Answer 6

https://support.microsoft.com/en-us/help/2538242/ms11-025-description-of-the-security-update-for-visual-c-2005-sp1-redi

and for VS2005 see

https://support.microsoft.com/en-us/help/2538218/ms11-025-description-of-the-security-update-for-visual-studio-2005-sp1

https://www.catalog.update.microsoft.com/Search.aspx?q=Visual%20Studio%202005

Answer 7

After installing vs2005 sp1,  I got a new error while compiling and linking:

uuid.lib : fatal error LNK1103: debugging information corrupt; recompile module

If I set "Generate Debug info”to "false", it builds successfully.

When I debug the application, in the middle, I will got a different error:

Debug Assertion Failed!

dbgdel.cpp  line 52

_BLOCK_TYPE_IS_VALID(pHead->nBlockUse).

Answer 8

https://support.microsoft.com/en-us/help/969443/fix-error-message-when-you-build-a-project-that-has-an-enumeration-wit

Since VS2005 SP1 is no longer supported I do not know if the hotfix mentioned in the Microsoft article is still available.

Did you try doing a complete rebuild of all of your project's modules and any libraries that they use?

When I debug the application, in the middle, I will got a different error:

Debug Assertion Failed!

dbgdel.cpp  line 52

_BLOCK_TYPE_IS_VALID(pHead->nBlockUse).

Looks like your application has corrupted the heap.

Answer 9

The hotfix in your link is not available.  Is there any other way to get it?

Could the heap corruption issue possibly be related to the error (fatal error LNK1103)?

Answer 10

Did you do a complete rebuild of all modules and libraries as previously suggested?

My best advice to you is to update to a current, supported version of Visual Studio.  As I noted earlier, VS2005 SP1 is no longer supported -- it reached EOL in 2016.

Answer 11

Yes, I did.

It will generate many other problems to update to a current version of Visual Studio.  Thanks a lot anyway.

Answer 12

You have a bug in your code.

The assertion triggered in dbgdel.cpp line 52 can occur if you try to free a memory block allocated on the heap more than once.

For example -

int *pInt = new int;

delete pInt; // OK

delete pInt; //BOOM!  Debug build asserts.

Answer 13

The application was unable to start correctly (0xc0150002). Click OK to close the application.
happens when you try to start an application compiled against RTI dotnet libraries in a system where the "Visual Studio® 2005 Service Pack 1 Redistributable Package MFC Security Update" is not installed.

The underlying cause is that the system is trying to find the "microsoft.VC80.CRT" file, provided in the mentioned Security Update. You can see the following error in the Application Log:

Activation context generation failed for "...\nddscd.dll". Dependent Assembly Microsoft.VC80.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
You must have the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update installed on the machine where you are running an application built with the release or debug libraries of the following RTI architecture packages:

i86Win32VS2005 and x64Win64VS2005, built with dynamic libraries
i86Win32jdk and x64Win64jdk
i86Win32dotnet2.0 and x64Win64dotnet2.0
The Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update can be obtained from the following Microsoft website:

  http://www.microsoft.com/download/en/details.aspx?id=26347

Answer 14

The initial issue was already resolved.  Currently, the OP's problem is that there is a coding error that corrupts the heap.