We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

Various errors w/ CGI app [Answered]RSS

18 replies

Last post Oct 22, 2008 01:10 PM by VorlonShadow

  • Various errors w/ CGI app

    Oct 07, 2008 04:12 PM|VorlonShadow|LINK

    I have written a simple CGI (.exe) app in Delphi 5.  It simply generates a .PDF file, and re-directs the browser to that .PDF file which has been stored in a certain folder on the web site.  When I try to execute it from the web site, various errors have been happening. At the moment, I get the error, "Connection Interrupted"

    Earlier, it was complaining about it not returning all header information (or something like that), and it said, "The headers it did return were """. I re-booted the server, and I have not seen this error since then.

    I can run the app from the straight Command prompt, and it returns a properly formatted HTML page.

    The Event log is returning an error each time I try to run the program:

    Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module msvcrt.dll, version 7.0.6001.18000, time stamp 0x4791a727, exception code 0xc0000005, fault offset 0x0000a11d, process id 0xea8, application start time 0x01c928b53c3ce344.

    This would appear to be a problem with IIS, not my CGI app. Right?

    Does anyone know how I might find and fix this issue?

    Thanks,
    Jesse

  • Re: Various errors w/ CGI app

    Oct 07, 2008 04:46 PM|ma_khan|LINK

     exception code 0xc0000005 means that a memory Access Violation is happening.. you might want to debug a little bit more... Is there any error that you see on the page??

  • Re: Various errors w/ CGI app

    Oct 07, 2008 04:52 PM|dispensa|LINK

    It's probably not an IIS bug; can you post a stack trace?
  • Re: Various errors w/ CGI app

    Oct 07, 2008 05:08 PM|VorlonShadow|LINK

    OK.  It's back.  Before, I was getting a general error like "cannot connect", or something like that.  Now, I'm getting the error,

    HTTP Error 502.2 - Bad Gateway

    The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "".

    Detailed Error Information<div id="details-left">
    Module CgiModule
    Notification ExecuteRequestHandler
    Handler WebCert
    Error Code 0xc0000005
    </div> <div id="details-right">
    Requested URL http://www.castleberryweb.com:80/dlg/bpamem/bpa/bin/webcerts.exe
    Physical Path D:\inetpub\CastleberryWeb\DLG\BPAMem\bpa\bin\webcerts.exe
    Logon Method Anonymous
    Logon User Anonymous
    </div>

    As mentioned earlier, it says it's not returning a complete set of headers, and the headers it is returning is "".  I can run the CGI app in a straight command prompt, though, and it returns a fully HTML formatted page.  As far as HTTP headers go, in my Delphi Code, I've tried various methods.  I've tried:

          Response.CustomHeaders.Add('Content-type: text/html');
          Response.CustomHeaders.Add('HTTP/1.0 200 OK');

    I've also tried:

          Response.ContentType := 'Content-type: text/html';
          Response.ContentEncoding := 'HTTP/1.0 200 OK';

    I've also tried a simple:

             cResponse :=
               'Content-type: text/html' + #10#13 +
               'HTTP/1.0 200 OK' + #10#13 // ... (rest of code here)
            Response.Content := cResponse;

     They all return "blank headers" from what I can tell, If the issue is missing header records, I would think that the message would read, "the headers that are returns are "list headers here"", instead of just "", but it's not seeing anything that I've sent using any of these methods.

     Any ideas?

    Thanks,
    Jesse

  • Re: Various errors w/ CGI app

    Oct 07, 2008 05:09 PM|VorlonShadow|LINK

    dispensa

    It's probably not an IIS bug; can you post a stack trace?
     

    I'm not getting a trace stack.  When I try to execute the CGI app straight up, I get this, as well as when I try it through the normal route (through my application).  If there's some way for me to get a stack trace out of this anyway, if you can let me know how, that'd be great, but basically, I run the .exe from the straight URL line in my browser, and I get this.

    Jesse

  • Re: Various errors w/ CGI app

    Oct 07, 2008 05:21 PM|dispensa|LINK

    Jumping in late here, so apologies if this is off..., but blank headers would be the result if the .exe (or the IIS worker process) crashes out during responding. It might work in the command-line case due to different input or something; hard to say. To get a stack, if it's really w3wp that's crashing, you can either narrow down to one w3wp and attach to it with a debugger or attach to w3svc with child debugging turned on and then send your request. You can do this with ntsd or (much preferably) WinDbg.
  • Re: Various errors w/ CGI app

    Oct 08, 2008 03:02 PM|VorlonShadow|LINK

    dispensa

    To get a stack, if it's really w3wp that's crashing, you can either narrow down to one w3wp and attach to it with a debugger or attach to w3svc with child debugging turned on and then send your request. You can do this with ntsd or (much preferably) WinDbg
     

    OK. We're getting beyond my capabilities here.  I have no idea how to "narrow down to one w3wp", nor how to "attach to w3svc with child debugging turned on", and once I did figure that out, where would I go to the the stack trace.  Once  get the stack trace, what would that tell me, then?  It would seem to me that my .exe is causing w3wp to crash some way.  What's the difference in running it from a command prompt, and running it from a browser prompt?  Doesn't IIS just execute the .exe?  I guess I'm not technical enough to understand what might cause this.  I could try tins in WS03, but I have a feeling it would work, as I have several CGI's already working on that server.

    Any ideas you can pass along to help me figure out what might be causing it to crash would be great.

     Thanks,
    Jesse

  • Re: Various errors w/ CGI app

    Oct 08, 2008 05:00 PM|dispensa|LINK

    By narrowing down to one worker process, you can tell which to attach to with the debugger; it could just be as easy as stopping IIS and re-starting it, and then asking for a page from the site you're troubleshooting (but not the CGI, of course). That should spawn one w3wp. If you get a stack, it may tell you exactly the problem, even if you don't quite know how to read a stack trace. I don't know anything about Delphi, though, but if you get a stack that you don't understand and nobody here can help you, you could probably post it elsewhere. As to why it would work on the command line but crash in the context of IIS, it's hard to say what difference is important, but it's gotta be something. For example, it will likely run under a different security context, have different access to files, registry keys, other secured objects, etc. It could be getting different parameters from the server. It could be that it's in a non-interactive session on Vista or 2k8 that's trying to throw up UI and crashing because it doesn't get a response. One other thing - you could add lots of debug logging to a logfile at every point in the execution and see where it breaks. See if you can narrow it down that way.
  • Re: Various errors w/ CGI app

    Oct 09, 2008 08:43 AM|VorlonShadow|LINK

    OK.  That's interesting.  I understand the concept. But, what I'm getting at is HOW DO I DO THIS?  I guess I can narrow down a w3wp.exe process using the task manager.  The issue is that right now, there are no web pages being accessed, and there are still 2 w3wp.exe processes running.  I guess I can figure out which one is being used by accessing a web page on the web site, then watching the CPU and memory usage spike, then note that process.

    OK, say I figure out how to do that.  How do I "attach a debugger".  I have no earthly idea how to do that in Windows, nor how to get the trace stack from the debugger once I've done that.  Could someone guide me in the right direction here?

    BTW, a little piece of additional information here.  If this is a "Visual Studio" thing, I'm not running Visual Studio. All my pages are hand coded.

    Thanks,
    Jesse

  • Re: Various errors w/ CGI app

    Oct 09, 2008 10:13 AM|ma_khan|LINK

  • Re: Various errors w/ CGI app

    Oct 09, 2008 02:07 PM|VorlonShadow|LINK

     OK.  I think I may have something.  I downloaded and installed WinDBG.  I figured out the process to attach the debug process to, and here is the log that it gave me:

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    *** wait with pending attach
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    ModLoad: 00810000 00818000   c:\windows\system32\inetsrv\w3wp.exe
    ModLoad: 77380000 774a7000   C:\Windows\system32\ntdll.dll
    ModLoad: 772a0000 7737b000   C:\Windows\system32\kernel32.dll
    ModLoad: 75d60000 75e26000   C:\Windows\system32\ADVAPI32.dll
    ModLoad: 75ff0000 760b3000   C:\Windows\system32\RPCRT4.dll
    ModLoad: 774b0000 7755a000   C:\Windows\system32\msvcrt.dll
    ModLoad: 75cc0000 75d5d000   C:\Windows\system32\USER32.dll
    ModLoad: 75fa0000 75feb000   C:\Windows\system32\GDI32.dll
    ModLoad: 75e30000 75f74000   C:\Windows\system32\ole32.dll
    ModLoad: 73a20000 73a55000   c:\windows\system32\inetsrv\IISUTIL.dll
    ModLoad: 754b0000 755a1000   C:\Windows\system32\CRYPT32.dll
    ModLoad: 75660000 75672000   C:\Windows\system32\MSASN1.dll
    ModLoad: 75ab0000 75ace000   C:\Windows\system32\USERENV.dll
    ModLoad: 75a90000 75aa4000   C:\Windows\system32\Secur32.dll
    ModLoad: 75c00000 75c2d000   C:\Windows\system32\WS2_32.dll
    ModLoad: 76320000 76326000   C:\Windows\system32\NSI.dll
    ModLoad: 75f80000 75f9e000   C:\Windows\system32\IMM32.DLL
    ModLoad: 763e0000 764a8000   C:\Windows\system32\MSCTF.dll
    ModLoad: 76fd0000 76fd9000   C:\Windows\system32\LPK.DLL
    ModLoad: 77560000 775dd000   C:\Windows\system32\USP10.dll
    ModLoad: 74f10000 74f31000   C:\Windows\system32\NTMARTA.DLL
    ModLoad: 762a0000 762ea000   C:\Windows\system32\WLDAP32.dll
    ModLoad: 75bf0000 75bf7000   C:\Windows\system32\PSAPI.DLL
    ModLoad: 75680000 75691000   C:\Windows\system32\SAMLIB.dll
    ModLoad: 74320000 7432e000   c:\windows\system32\inetsrv\w3wphost.dll
    ModLoad: 75c30000 75cbd000   C:\Windows\system32\OLEAUT32.dll
    ModLoad: 73940000 73992000   c:\windows\system32\inetsrv\nativerd.dll
    ModLoad: 74570000 7459f000   C:\Windows\system32\XmlLite.dll
    ModLoad: 73880000 738b0000   c:\windows\system32\inetsrv\IISRES.DLL
    ModLoad: 75010000 7504b000   C:\Windows\system32\rsaenh.dll
    ModLoad: 79000000 79046000   C:\Windows\system32\mscoree.dll
    ModLoad: 76330000 76388000   C:\Windows\system32\SHLWAPI.dll
    ModLoad: 747e0000 7497e000   C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc\comctl32.dll
    ModLoad: 79e70000 7a3ff000   C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
    ModLoad: 72df0000 72e8b000   C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.1434_none_d08b6002442c891f\MSVCR80.dll
    ModLoad: 76140000 761c4000   C:\Windows\system32\CLBCatQ.DLL
    ModLoad: 73760000 73790000   C:\Windows\system32\mlang.dll
    ModLoad: 72220000 72251000   C:\Windows\system32\inetsrv\iiscore.dll
    ModLoad: 731c0000 731c7000   c:\windows\system32\inetsrv\W3TP.dll
    ModLoad: 73fa0000 73fa9000   c:\windows\system32\inetsrv\w3dt.dll
    ModLoad: 73a00000 73a0b000   C:\Windows\system32\HTTPAPI.dll
    ModLoad: 75410000 7544a000   C:\Windows\system32\slc.dll
    ModLoad: 722f0000 72318000   C:\Windows\system32\faultrep.dll
    ModLoad: 75000000 75008000   C:\Windows\system32\VERSION.dll
    ModLoad: 74ee0000 74eef000   C:\Windows\system32\NLAapi.dll
    ModLoad: 75600000 75619000   C:\Windows\system32\IPHLPAPI.DLL
    ModLoad: 753d0000 75405000   C:\Windows\system32\dhcpcsvc.DLL
    ModLoad: 756a0000 756cc000   C:\Windows\system32\DNSAPI.dll
    ModLoad: 755f0000 755f7000   C:\Windows\system32\WINNSI.DLL
    ModLoad: 753a0000 753c1000   C:\Windows\system32\dhcpcsvc6.DLL
    ModLoad: 75210000 7524b000   C:\Windows\System32\mswsock.dll
    ModLoad: 73580000 73588000   C:\Windows\System32\winrnr.dll
    ModLoad: 73570000 7357f000   C:\Windows\system32\napinsp.dll
    ModLoad: 74ed0000 74ed5000   C:\Windows\System32\wshtcpip.dll
    ModLoad: 75280000 75285000   C:\Windows\System32\wship6.dll
    ModLoad: 73810000 73816000   C:\Windows\system32\rasadhlp.dll
    ModLoad: 764c0000 76fcf000   C:\Windows\system32\SHELL32.dll
    ModLoad: 72c60000 72c66000   C:\Windows\System32\inetsrv\cachuri.dll
    ModLoad: 72400000 72408000   C:\Windows\System32\inetsrv\cachfile.dll
    ModLoad: 723c0000 723c6000   C:\Windows\System32\inetsrv\cachtokn.dll
    ModLoad: 72350000 7235e000   C:\Windows\System32\inetsrv\cachhttp.dll
    ModLoad: 722e0000 722ee000   C:\Windows\System32\inetsrv\compstat.dll
    ModLoad: 722d0000 722d8000   C:\Windows\System32\inetsrv\defdoc.dll
    ModLoad: 722c0000 722c9000   C:\Windows\System32\inetsrv\dirlist.dll
    ModLoad: 722b0000 722b8000   C:\Windows\System32\inetsrv\protsup.dll
    ModLoad: 721b0000 721b9000   C:\Windows\System32\inetsrv\redirect.dll
    ModLoad: 71b90000 71b9b000   C:\Windows\System32\inetsrv\iis_ssi.dll
    ModLoad: 71b80000 71b8d000   C:\Windows\System32\inetsrv\static.dll
    ModLoad: 71760000 7176b000   C:\Windows\System32\inetsrv\authanon.dll
    ModLoad: 71740000 7174b000   C:\Windows\System32\inetsrv\modrqflt.dll
    ModLoad: 71730000 71739000   C:\Windows\System32\inetsrv\logcust.dll
    ModLoad: 71700000 7170d000   C:\Windows\System32\inetsrv\custerr.dll
    ModLoad: 71690000 71698000   C:\Windows\System32\inetsrv\loghttp.dll
    ModLoad: 71610000 71617000   C:\Windows\System32\inetsrv\iisetw.dll
    ModLoad: 70800000 70825000   C:\Windows\System32\inetsrv\iisfreb.dll
    ModLoad: 70d40000 70d47000   C:\Windows\System32\inetsrv\iisreqs.dll
    ModLoad: 738b0000 738b7000   C:\Windows\system32\WSOCK32.dll
    ModLoad: 70a40000 70a5d000   C:\Windows\System32\inetsrv\isapi.dll
    ModLoad: 70850000 70861000   C:\Windows\System32\inetsrv\filter.dll
    ModLoad: 70d30000 70d3d000   C:\Windows\System32\inetsrv\cgi.dll
    ModLoad: 707e0000 707f1000   C:\Windows\System32\inetsrv\iisfcgi.dll
    ModLoad: 70a70000 70a78000   C:\Windows\System32\inetsrv\validcfg.dll
    ModLoad: 6a2a0000 6a30c000   C:\Windows\Microsoft.NET\Framework\v2.0.50727\webengine.dll
    ModLoad: 60060000 60067000   C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll
    ModLoad: 70a60000 70a6a000   C:\Windows\system32\inetsrv\gzip.dll
    ModLoad: 6ea80000 6eae1000   \\?\C:\Windows\system32\inetsrv\asp.dll
    ModLoad: 74d50000 74d64000   C:\Windows\system32\ATL.DLL
    ModLoad: 70910000 70a3f000   C:\Windows\system32\comsvcs.dll
    ModLoad: 75970000 759cf000   C:\Windows\system32\SXS.DLL
    ModLoad: 70300000 70369000   C:\Windows\system32\vbscript.dll
    ModLoad: 6e330000 6e3dd000   C:\Program Files\Common Files\System\ado\msado15.dll
    ModLoad: 70450000 7046f000   C:\Windows\system32\MSDART.DLL
    ModLoad: 6e280000 6e329000   C:\Program Files\Common Files\System\Ole DB\oledb32.dll
    ModLoad: 74020000 740a5000   C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.6001.18000_none_886786f450a74a05\COMCTL32.dll
    ModLoad: 760c0000 76133000   C:\Windows\system32\COMDLG32.dll
    ModLoad: 761d0000 762a0000   C:\Windows\system32\WININET.dll
    ModLoad: 764b0000 764b3000   C:\Windows\system32\Normaliz.dll
    ModLoad: 76390000 763d5000   C:\Windows\system32\iertutil.dll
    ModLoad: 6ff60000 6ff77000   C:\Program Files\Common Files\System\Ole DB\OLEDB32R.DLL
    ModLoad: 6ea10000 6ea7e000   C:\Program Files\Common Files\System\Ole DB\msdasql.dll
    ModLoad: 70430000 70449000   C:\Program Files\Common Files\System\Ole DB\MSDATL3.dll
    ModLoad: 73290000 732f5000   C:\Windows\system32\ODBC32.dll
    ModLoad: 73250000 73288000   C:\Windows\system32\odbcint.dll
    ModLoad: 707d0000 707df000   C:\Program Files\Common Files\System\Ole DB\MSDASQLR.DLL
    ModLoad: 10000000 10242000   C:\Program Files\MySQL\Connector ODBC 5.1\myodbc5.dll
    ModLoad: 702f0000 70300000   C:\Program Files\Common Files\System\ado\msadrh15.dll
    (bb8.cf8): Break instruction exception - code 80000003 (first chance)
    eax=7ffda000 ebx=00000000 ecx=00000000 edx=7740d094 esi=00000000 edi=00000000
    eip=773c7dfe esp=0275f8c4 ebp=0275f8f0 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\ntdll.dll -
    ntdll!DbgBreakPoint:
    773c7dfe cc              int     3
    0:027> g
    (bb8.c1c): Access violation - code c0000005 (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=00000000 ebx=00000000 ecx=00efb410 edx=00000022 esi=0134c7e0 edi=00000000
    eip=774ba11d esp=01a2cdb0 ebp=01a2cdb0 iopl=0         nv up ei pl nz na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\msvcrt.dll -
    msvcrt!wcschr+0xc:
    774ba11d 0fb708          movzx   ecx,word ptr [eax]       ds:0023:00000000=????
    0:006> g
    Info - ReportFault called
    eax=000000c0 ebx=00000003 ecx=00000000 edx=00000000 esi=00000002 edi=00326b50
    eip=773d9a94 esp=0264fe24 ebp=0264ff54 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    ntdll!KiFastSystemCallRet:
    773d9a94 c3              ret
    0:028> g
           ^ No runnable debuggees error in 'g'

    I have no idea how to read this.  If anyone can give me some hints, I would appreciate it.

    Basically, here's what I did.  I ran WinDBG, then attached to the process.  It loaded up the top portion of the log.  I then tried to run the CGI program, but nothing seemed to be happening.  I figured out that I needed to hit "Go" in the debugger, which I did. This appears to have caused an Access Violation error.  I then hit Go again, and the second bit of information came up "ReportFault called".  I then hit Go again, and got the "No runnable debuggees".

    I'm familiar with Access Violation, but I'm running it the same way I'm running it from the command prompt. Why would it cause an AV when running from a browser, and not from the command prompt?

    Thanks,
    Jesse

  • Re: Various errors w/ CGI app

    Oct 13, 2008 08:56 PM|anilr|LINK

    Typing "kb" at the access violation will give you the stack trace - further investigation would depend on who is passing the bad arguments to msvcrt!wcschr

    Anil Ruia
    Software Design Engineer
    IIS Core Server
  • Re: Various errors w/ CGI app

    Oct 14, 2008 08:15 AM|VorlonShadow|LINK

    OK.  Here's the output from that.  I hit "g" to first get the Access violation, then I type "kb" to get the stack trace.  Here it is:

    0:028> g
    (c1c.1654): Access violation - code c0000005 (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=00000000 ebx=00000000 ecx=0105a4b0 edx=00000022 esi=018165c8 edi=00000000
    eip=774ba11d esp=01b6cb6c ebp=01b6cb6c iopl=0         nv up ei pl nz na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\msvcrt.dll -
    msvcrt!wcschr+0xc:
    774ba11d 0fb708          movzx   ecx,word ptr [eax]       ds:0023:00000000=????


    0:008> kb
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\System32\inetsrv\cgi.dll -
    ChildEBP RetAddr  Args to Child             
    WARNING: Stack unwind information not available. Following frames may be wrong.
    01b6cb6c 746c6a9b 00000000 00000022 01fcfff4 msvcrt!wcschr+0xc
    01b6f41c 746c456e 0105cac8 00000100 0105a494 cgi!RegisterModule+0x2483
    01b6f438 746c45c1 00000080 00000000 018165c8 cgi+0x456e
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\inetsrv\iiscore.dll -
    01b6f454 74a57035 018165c8 01816620 018165cc cgi+0x45c1
    01b6f468 74a53696 0105a494 018165c8 00000000 iiscore+0x7035
    01b6f4e0 74a5aa4c 00000000 00000000 00000000 iiscore+0x3696
    01b6f528 74a56583 00000000 00000000 00000000 iiscore+0xaa4c
    01b6f54c 74a5211c 00000000 00000000 00000000 iiscore+0x6583
    01b6f7b4 74a54eef 00000000 00000000 00000000 iiscore+0x211c
    01b6f7d4 74a5c6b8 018165cc 00000000 0104c0e0 iiscore+0x4eef
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for c:\windows\system32\inetsrv\w3dt.dll -
    01b6f7ec 74ac13b3 01815b70 01815b70 74ac1330 iiscore+0xc6b8
    01b6f804 74ac11da 00000485 00000000 01815b74 w3dt!UlAtqGetContextProperty+0x43
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for c:\windows\system32\inetsrv\W3TP.dll -
    01b6f818 731c2611 00000000 00000485 01815b74 w3dt+0x11da
    01b6f850 731c2812 00000000 0104c3f8 731c0000 W3TP!THREAD_POOL::PostCompletion+0xdf
    01b6f864 731c1e85 0104c0e0 00000000 00000000 W3TP!OverrideThreadPoolConfigWithRegistry+0x14a
    01b6f87c 772e4911 0104c3f8 01b6f8c8 773be4b6 W3TP+0x1e85
    01b6f888 773be4b6 0104c3f8 547923c5 00000000 kernel32!BaseThreadInitThunk+0x12
    01b6f8c8 773be489 731c1e4c 0104c3f8 ffffffff ntdll!RtlInitializeExceptionChain+0x63
    01b6f8e0 00000000 731c1e4c 0104c3f8 00000000 ntdll!RtlInitializeExceptionChain+0x36 

    Again, I really have no idea how to read this.  All these numbers don't mean a thing to me.  As for "who is passing the bad arguments to msvcrt!wcschr",  how do I tell that?  all I do is execute the following in my browser: http://www.mysite.com/bin/WebCerts.exe  and hit the enter key (replace with my actual site, of course).  the .exe is set up to recognize that no parameters are passed, and should throw up an HTML message stating that certain parameters have not been passed.  Again, this is exactly what you see when you type the WebCerts.exe from a command prompt.

    Any help you can offer is greatly appreciated.

    Thanks,
    Jesse

  • Re: Various errors w/ CGI app

    Oct 14, 2008 11:11 AM|anilr|LINK

    You don't have symbol path to microsoft's public symbol server setup correctly - can you type ".dump /ma <file-name>" in the debugger to create a dump file - zip that file and e-mail it to me at anil (dot) ruia (at) microsoft (dot) com ?

    Anil Ruia
    Software Design Engineer
    IIS Core Server
  • Re: Various errors w/ CGI app

    Oct 14, 2008 01:01 PM|VorlonShadow|LINK

     I thought I replied to this, but I don't see it.  I've done as you stated, and e-mailed you a link to download the .zip file.

    Thanks,
    Jesse

  • Re: Various errors w/ CGI app

    Oct 16, 2008 07:03 PM|anilr|LINK

    You need to remove the aspnet_filter ISAPI filter from the ISAPI filter list - the asp.net ISAPI filter blocks any path under /bin/ which is blocking request to your url /dlg/bpamem/bin/WebCerts.exe

    Anil Ruia
    Software Design Engineer
    IIS Core Server
  • Re: Various errors w/ CGI app

    Oct 16, 2008 09:46 PM|VorlonShadow|LINK

     Thanks for your help.  I've done that, now I'm back to another error message that I used to get frequently:

    HTTP Error 502.2 - Bad Gateway

    The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "".

    I'm not sure exactly what this means, but at this point, it would not seem to be an IIS problem any more, so I suppose I need to figure out now why it's not seeing the headers that are being sent.  Does this appear to be a possible IIS issue, or something else?

    BTW, I went ahead and installed this on our WS03 server, and it's working perfectly.

    Jesse

  • Re: Various errors w/ CGI app

    Oct 21, 2008 03:58 PM|anilr|LINK

    If you type ".childdbg 1" in the debugger attached to w3wp - you will be able to debug your CGI process from within the same debugger window - also, you can debug at the source level by using windbg and setting the correct source path.

    Anil Ruia
    Software Design Engineer
    IIS Core Server
  • Re: Various errors w/ CGI app

    Oct 22, 2008 01:10 PM|VorlonShadow|LINK

    I don't know what happened, but I just tried this again after several days (if not weeks), and it worked perfectly.  I passed no parameters, and I got the proper error message back.  I passed valid parameters, and it reacted as it should.  I don't know what changed, but its working now.

    Thanks so much for your help on this.

    Jesse