none
CLR application won't start except on my development machine RRS feed

  • Question

  • I've developed a small CLR application that runs on my development machine, but won't start on any other machines that I've tried it on.  I developed it using Visual Studio 2005 using C++.  Using ntsd on a machine where it won't start, I get the output below.  What am I missing?

    Note that half way through the ntsd output the debugger stopped at breakpoint, although I hadn't set any breakpoints.  I entered a g command to get the rest of the output.

    John



    Microsoft (R) Windows User-Mode Debugger  Version 5.1.2600.0
    Copyright (c) Microsoft Corporation. All rights reserved.

    CommandLine: bin\canoe.exe
    Loaded dbghelp extension DLL
    The call to LoadLibrary(ext) failed with error 2.
    Please check your debugger configuration and/or network access
    Loaded exts extension DLL
    The call to LoadLibrary(uext) failed with error 2.
    Please check your debugger configuration and/or network access
    Loaded ntsdexts extension DLL
    Symbol search path is: *** Invalid *** : Verify _NT_SYMBOL_PATH setting
    Executable search path is:
    ModLoad: 00400000 0040f000   canoe.exe
    ModLoad: 7c900000 7c9af000   ntdll.dll
    ModLoad: 79000000 79045000   C:\WINDOWS\system32\mscoree.dll
    ModLoad: 7c800000 7c8f6000   C:\WINDOWS\system32\KERNEL32.dll
    ModLoad: 77dd0000 77e6b000   C:\WINDOWS\system32\advapi32.dll
    ModLoad: 77e70000 77f02000   C:\WINDOWS\system32\RPCRT4.dll
    ModLoad: 77fe0000 77ff1000   C:\WINDOWS\system32\Secur32.dll
    ModLoad: 10000000 10014000   D:\2944COBA\bin\bctools.dll
    ModLoad: 003c0000 003d8000   D:\2944COBA\bin\dll_bccore.dll
    ModLoad: 76b40000 76b6d000   C:\WINDOWS\system32\WINMM.dll
    ModLoad: 77f10000 77f59000   C:\WINDOWS\system32\GDI32.dll
    ModLoad: 7e410000 7e4a1000   C:\WINDOWS\system32\USER32.dll
    ModLoad: 7c9c0000 7d1d7000   C:\WINDOWS\system32\SHELL32.dll
    ModLoad: 77c10000 77c68000   C:\WINDOWS\system32\msvcrt.dll
    ModLoad: 77f60000 77fd6000   C:\WINDOWS\system32\SHLWAPI.dll
    ModLoad: 78130000 781cb000   C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1
    e18e3b_8.0.50727.762_x-ww_6b128700\MSVCR80.dll
    ModLoad: 003f0000 003fb000   D:\2944COBA\bin\dll_bcmessage.dll
    ModLoad: 00420000 0042f000   D:\2944COBA\bin\dll_zlib.dll
    ModLoad: 00440000 00457000   D:\2944COBA\bin\dll_rtdd.dll
    ModLoad: 00470000 00477000   D:\2944COBA\bin\dll_vcs.dll
    ModLoad: 00490000 00497000   D:\2944COBA\bin\bmpboss.dll
    ModLoad: 004b0000 004cb000   D:\2944COBA\bin\dll_intrpret.dll
    ModLoad: 004e0000 0053a000   D:\2944COBA\bin\dll_sysfunc.dll
    ModLoad: 00550000 00561000   D:\2944COBA\bin\dll_tools.dll
    ModLoad: 00580000 005a8000   D:\2944COBA\bin\dll_bccommon.dll
    ModLoad: 781d0000 782df000   C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1
    e18e3b_8.0.50727.762_x-ww_3bf8fa05\MFC80.DLL
    ModLoad: 77120000 771ab000   C:\WINDOWS\system32\OLEAUT32.dll
    ModLoad: 774e0000 7761d000   C:\WINDOWS\system32\ole32.dll
    ModLoad: 005c0000 005c7000   D:\2944COBA\bin\core.dll
    ModLoad: 005e0000 005e6000   D:\2944COBA\bin\dll_workstation.dll
    ModLoad: 00600000 0060a000   D:\2944COBA\bin\cell_controller.dll
    ModLoad: 00620000 00641000   D:\2944COBA\bin\dll_waveform.dll
    ModLoad: 00660000 00686000   D:\2944COBA\bin\dll_record.dll
    ModLoad: 006a0000 006be000   D:\2944COBA\bin\dll_testrslt.dll
    ModLoad: 006d0000 006e0000   D:\2944COBA\bin\dll_message.dll
    ModLoad: 006f0000 0070c000   D:\2944COBA\bin\display.dll
    ModLoad: 00720000 0072f000   D:\2944COBA\bin\dll_model.dll
    ModLoad: 00740000 00748000   D:\2944COBA\bin\perftimer.dll
    ModLoad: 00760000 00769000   D:\2944COBA\bin\dll_repair.dll
    ModLoad: 00780000 0078a000   D:\2944COBA\bin\dll_host.dll
    ModLoad: 007a0000 007a6000   D:\2944COBA\bin\dll_vtersrvr.dll
    ModLoad: 007c0000 007d0000   D:\2944COBA\bin\dll_vterclnt.dll
    ModLoad: 007e0000 007e7000   D:\2944COBA\bin\dbg_serv.dll
    ModLoad: 00800000 00807000   D:\2944COBA\bin\dll_security.dll
    ModLoad: 00820000 00826000   D:\2944COBA\bin\dll_scanner.dll
    ModLoad: 00840000 00848000   D:\2944COBA\bin\ramper.dll
    ModLoad: 00860000 00870000   D:\2944COBA\bin\cencon.dll
    ModLoad: 00880000 00887000   D:\2944COBA\bin\calib.dll
    ModLoad: 008a0000 008a6000   D:\2944COBA\bin\dll_DCFISComm.dll
    ModLoad: 008c0000 008c6000   D:\2944COBA\bin\pcsonline.dll
    ModLoad: 008e0000 008e6000   D:\2944COBA\bin\dll_trhistory.dll
    ModLoad: 00900000 00907000   D:\2944COBA\bin\cnvh.dll
    ModLoad: 00920000 00927000   D:\2944COBA\bin\adaptivetpm.dll
    ModLoad: 71ab0000 71ac7000   C:\WINDOWS\system32\WS2_32.dll
    ModLoad: 71aa0000 71aa8000   C:\WINDOWS\system32\WS2HELP.dll
    ModLoad: 71a50000 71a8f000   C:\WINDOWS\system32\MSWSOCK.dll
    ModLoad: 7c4c0000 7c53d000   C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1
    e18e3b_8.0.50727.762_x-ww_6b128700\msvcm80.dll
    Break instruction exception - code 80000003 (first chance)
    eax=00251eb4 ebx=7ffda000 ecx=00000005 edx=00000020 esi=00251f48 edi=00251eb4
    eip=7c90120e esp=0012fb20 ebp=0012fc94 iopl=0         nv up ei pl nz na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdl
    l.dll -
    ntdll!DbgBreakPoint:
    7c90120e cc               int     3
    0:000> g
    ModLoad: 773d0000 774d3000   C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Cont
    rols_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll
    ModLoad: 5d090000 5d12a000   C:\WINDOWS\system32\comctl32.dll
    ModLoad: 5d360000 5d36e000   C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b
    9a1e18e3b_8.0.50727.762_x-ww_91481303\MFC80ENU.DLL
    ModLoad: 79e70000 7a3d6000   C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscor
    wks.dll
    ModLoad: 60340000 60348000   C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\cultu
    re.dll
    ModLoad: 790c0000 79b90000   C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\msco
    rlib\dd76096849d6fbeb42bed6d24425d71d\mscorlib.ni.dll
    ModLoad: 79060000 790b3000   C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscor
    jit.dll
    ModLoad: 68000000 68036000   C:\WINDOWS\system32\rsaenh.dll
    ModLoad: 03680000 0369d000   D:\2944COBA\bin\BCVSTools.dll
    C++ EH exception - code e06d7363 (first chance)
    C++ EH exception - code e06d7363 (first chance)
    C++ EH exception - code e06d7363 (first chance)
    Unknown exception - code e0434f4d (first chance)
    C++ EH exception - code e06d7363 (first chance)
    ModLoad: 5e380000 5e409000   C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\diasy
    mreader.dll
    eax=00000000 ebx=00000000 ecx=7c800000 edx=7903f4f8 esi=7c90de50 edi=00000000
    eip=7c90e4f4 esp=0012fc28 ebp=0012fd24 iopl=0         nv up ei pl zr na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    ntdll!KiFastSystemCallRet:
    7c90e4f4 c3               ret
    0:000>
    Thursday, July 31, 2008 2:10 PM

Answers

  • The missing dll, unbeknownst to me, is being generated by Visual Studio, and I should have been distributing it with my executable.  It is a COM interop assembly, and I thought it was part of the third-party installation, but that installation actually contains a COM type library, not the same thing, and Visual Studio quietly generated an interop assembly from the type library.  Problem solved!

    John Gourlay

    • Marked as answer by John Gourlay Thursday, July 31, 2008 6:03 PM
    Thursday, July 31, 2008 6:03 PM

All replies

  • It turns out that my problem is that the application is looking for a referenced third party dll in the wrong place.  It's looking in the same directory as my executable, rather in the directory in which it was installed.  This is really a visual studio question, I guess.  How do I build my application so that it looks for the installed dll?

    Thursday, July 31, 2008 3:34 PM
  • The missing dll, unbeknownst to me, is being generated by Visual Studio, and I should have been distributing it with my executable.  It is a COM interop assembly, and I thought it was part of the third-party installation, but that installation actually contains a COM type library, not the same thing, and Visual Studio quietly generated an interop assembly from the type library.  Problem solved!

    John Gourlay

    • Marked as answer by John Gourlay Thursday, July 31, 2008 6:03 PM
    Thursday, July 31, 2008 6:03 PM