Problem using c++ library

Question

i'm trying to use an executable file (written in c) that calls a c++ library. I'm getting this error in my Windows 2008 box:

Faulting application name: sample.exe, version: 0.0.0.0, time stamp: 0x4d668157
Faulting module name: MSVCR90.dll, version: 9.0.30729.4974, time stamp: 0x4b7a226f
Exception code: 0xc0000417
Fault offset: 0x0002fc96
Faulting process id: 0xf10
Faulting application start time: 0x01cbd45775cc7011
Faulting application path: C:\Bprobe\sample.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4974_none_50940634bcb759cb\MSVCR90.dll
Report Id: b37b5e67-404a-11e0-b69c-00155d2fb513

The same exe works in windows 7 and XP so i'm guessing it's a missing component.

Any ideas?

Thanks, Gonzalo

EDIT: This doesn't seem to be a problem exclusive to Windows 2008, i just tested in an XP and got the same error (i do have other XP boxes where it worked).

Answer 1

Exception code 0xc0000417 is STATUS_INVALID_CRUNTIME_PARAMETER. Sounds like an invalid parameter was passed to a C runtime function.

I would launch the application under a debugger, with WinDBG or VS if you have it installed on this machine. Set the debugger to break on all first chance exceptions (or you could add in this exception code directly and have it break only on this exception) and when you hit the exception, examine the call stack. Use Microsoft's public symbol server to resolve symbols (it will have the VS 2008 CRT library symbols). Have the .pdb for your .exe present or on the symbol search path.

If frames from your module are anywhere on the call stack, double click the first one starting from the top down. Check to see which C runtime function is being called.

Answer 2

This isn't a missing library issue, but the information you've given is insufficient to even begin to diagnose the problem. Try running the program in a debugger and seeing where it crashes. Most likely either the program or the library you're using is incompatible with Windows 7 - ie, it makes some bad assumptions it was never allowed to make, resulting in crashes when those assumptions turn out not to be true in Win7.

If you do not have source code, try the compatibility wizard (right click exe -> troubleshoot compatibility). If this doesn't help, contact the vendor and have them fix the bug in their program.