IIS6 Svr 2003 ISAPI Extension DLL - Specified Procedure ca..

External Since: Sep 03, 2003 Posts: 2

I am working on a C++ extension DLL created in VC6 and used under IIS6 and
2003 Server. When I debug into the ISAPI extension DLL, the DLLMain's gets
called for DLL Attach action (true returned) but no other exposed functions
such GetExtensionVersion or HTTPExtensionProc is called by the system (for
the breakpoints never get hit). The message printed to the page is:

"The specified procedure cannot be found"

Before I got the debugging session working It was calling the other
functions, for I had a log file with reports of those actions. So either I
have changed a setting which may cause the ISAPI dll to fail or I have
changed a build parameter in VC6.

Note just running the extension w/o the debugger or in release mode has the
same message displayed.

Any thoughts would be helpful...

advTHANKSance

-OmegaMan

External Since: Sep 03, 2003 Posts: 115

Hi OmegaMan,

For some reason GetExtensionVersion and/or HttpExtensionProc have not
actually been exported from the dll. Check to ensure that you have a .def
file that's included in the project that exports them (and check the case of
HttpExtensionProc, ie. not HTTPExtensionProc).

Thank you,
-Wade A. Hilmo,
-Microsoft

PS: If you have any other questions on this or any other ISAPI issue,
please feel free to post to
microsoft.public.platformsdk.internet.server.isapi-dev, which exists for
that purpose.

"OmegaMan" <omegaman.DeleteThis@pcisys.net> wrote in message
news:#hQcaFmcDHA.456@TK2MSFTNGP10.phx.gbl...
> I am working on a C++ extension DLL created in VC6 and used under IIS6 and
> 2003 Server. When I debug into the ISAPI extension DLL, the DLLMain's gets
> called for DLL Attach action (true returned) but no other exposed
functions
> such GetExtensionVersion or HTTPExtensionProc is called by the system (for
> the breakpoints never get hit). The message printed to the page is:
>
> "The specified procedure cannot be found"
>
> Before I got the debugging session working It was calling the other
> functions, for I had a log file with reports of those actions. So either I
> have changed a setting which may cause the ISAPI dll to fail or I have
> changed a build parameter in VC6.
>
> Note just running the extension w/o the debugger or in release mode has
the
> same message displayed.
>
> Any thoughts would be helpful...
>
> advTHANKSance
>
> -OmegaMan
>
>
>