469,365 Members | 1,785 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,365 developers. It's quick & easy.

Visual Studio error ntstatus 0xc0150002

shoonya
161 100+
Hi,
I am bit new to visual studio.
I am having following error while building the project.

Expand|Select|Wrap|Line Numbers
  1. LDR: LdrpWalkImportDescriptor() failed to probe abc.dll for its manifest, ntstatus 0xc0150002
  2.  
  3. abc.exe': Loaded 'C:\WINDOWS\incops3\ICDCNL.dll', Binary was not built with debug information.
  4.  
What should I do in this case.
I am using xp and visual studio2005

Shoonya
Feb 13 '09 #1
10 19170
weaknessforcats
9,208 Expert Mod 8TB
Visual Studio has two types of builds: Release and Debug.

Release builds do not contain code to support the debugger whereas Debug builds do. It means that Debug builds are larger and run slower than Release builds due to that debugger support code. Debug builds also require a .pdb file (program database built and maintained by Visual Studio).

You will find that moving your Debug executable to another computer will cause a crash at run time because the .pdb file is missing.

The default build is Debug.

That means your .DLL needs to be a debug DLL. It looks like you have a relase build DLL. Most DLLs come in both versions. The usual convention is MyDll.dll for the Release version and MyDllD.dll for the debug version.

After your debugging is complete and you are ready to distribute your executable, then you make a final Release build and send that out.

You switch the build type between Release and Debug by using your Configuration Manager.
Feb 14 '09 #2
shoonya
161 100+
Hi,

thanks for the prompt reply,

I am using debug mode.
I gave a full clean and build my whole project in debug mode, then also I am getting this error.

Can you tell me where to find "configuration manager"

Shoonya
Feb 17 '09 #3
weaknessforcats
9,208 Expert Mod 8TB
Go to your Project Properties.

There is a button in the upper-right corner labeled "Configuration Manager".
Feb 17 '09 #4
shoonya
161 100+
I checked in "configuration manager"

All the modules are having "Debug" against it
and I never changed it to "Release"
so if i am giving fresh build then all my dll should be in "debug" mode.

but then also It's giving same error again
:(

Shoonya
Feb 18 '09 #5
Savage
1,764 Expert 1GB
Is your DLL abc.dll or ICDCNL.dll?
What wfc was saying holds true only for ICDCNL.dll.

As for the other message,I think it is a VS2005 bug.
Do you have SP1 installed?
Feb 18 '09 #6
shoonya
161 100+
My dll is abc.dll
and i have got SP3 installed
Feb 18 '09 #7
shoonya
161 100+
What exactly is this "VS2005 bug"
there are similar systems here having SP3 but their visual studio is running fine with same piece of code

I have already got my visual studio re-installed
Feb 18 '09 #8
weaknessforcats
9,208 Expert Mod 8TB
The original error was that abc.exe (a debug project) was executing inside Visual Studio and it loaded an ICDCNL.dll that was not a debug dll.

You have to change your project to a release project in order to use this dll.
Feb 18 '09 #9
shoonya
161 100+
Hi,

That problem is still not resolved. Can anybody provide some more help..

Shoonya
May 27 '09 #10
shoonya
161 100+
giving more details:

I am having many projects, and 1 has been set as "startup project", say FOO
On starting the debug, it's giving message "foo.exe has triggered a breakpoint"
and it breaks at line no: 459, file: crtdll.c
and output window is having above mentioned error.


Shoonya
May 27 '09 #11

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

1 post views Thread by YAQ | last post: by
1 post views Thread by Jodie Schau | last post: by
reply views Thread by Alan S | last post: by
reply views Thread by Maxim Kazitov | last post: by
1 post views Thread by harris_cohen | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.