Previous Next

• 04-22-2008, 3:05 PM

  gregsohl Joined on 04-22-2008, 1:12 PM Posts 2 gregsohl

  No such interface supported - error accessing an ISAPI extension DLL Reply Contact When attempting to access an ISAPI extension DLL, I get back the following error: Server Application Error The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance. There is a corresponding entry in the system event log: Event Type:    Warning Event Source:    W3SVC Event Category:    None Event ID:    36 Date:        4/21/2008 Time:        11:39:32 AM User:        N/A Computer:    ASDWWW Description: The server failed to load application '/LM/W3SVC/1/Root/MyApp/core'.  The error was 'No such interface supported The web site's log file shows the request with a 500 level return code. I used FileMonNT (yes I know ProcessMon is available) to check file activity. The DLL itself never gets accessed. I'm not certain how to diagnose this further. I've reviewed the information at http://classicasp.aspfaq.com/general/what-is-event-id-36-and-how-can-i-get-iis-running-again.html That seemed interesting but not exactly applicable. This is running on Windows Server 2000, IIS 5.0. This server was migrated recently using a disk-level copy system (Double-Take), and accessing this DLL hasn't worked since. Everything else works including JSP, ColdFusion, PHP and pure HTML. Its the only issue I has following the server move. I would appreciate any ideas or assistance. Thanks. Greg

  Tags: HTTPIIS 5

• 04-22-2008, 4:24 PM

  In reply to

  gregsohl Joined on 04-22-2008, 1:12 PM Posts 2 gregsohl

  Re: No such interface supported - error accessing an ISAPI extension DLL Reply Contact  I just read http://support.microsoft.com/?id=309051. Item 6 said: 6. As a last resort, you can re-create the IIS packages. To do this, follow these steps: a. Browse to Component Services and delete the following packages:NOTE: To delete the packages, you must first open the properties of the package, click the Advanced tab, and then click to clear the Disable Deletion check box. • IIS In-Process Applications • IIS Out-of-Process Pooled Applications • IIS Utilities I checked on the server and these components are missing. The old server has them registered. Could this be the problem? Are there any risks with following the instructions for registering them? Greg