More IIS 7 Questions

Jul 23, 2009 at 2:50 PM

Hi Cheeso;

 

Been trying to get IIRF working on IIS7/vista 32bit, and not having much luck.

I followed the instructions located in this thread (http://iirf.codeplex.com/Thread/View.aspx?ThreadId=39685) for installing dll into IIS, and restarted server.

Isapirewrite.dll and .ini files are in same directory (not in web path), and both files are accessible to IUSR for read / execute. Run test apps in bin directory are run, they cannot find the .dll. I'm assuming the apps attempt to use via http request, rather than a straight load.

I looked at http://blogs.msdn.com/david.wang/archive/2005/06/21/HOWTO_Diagnose_and_Fix_Common_ISAPI_Filter_Installation_Failures.aspx and looked in event log, and have not found any errors related to W3SVC anywhere.

Obviously, Im missing something, so any thoughts greatly appreciated.

thanks

-avi

Coordinator
Jul 23, 2009 at 3:24 PM

Best instructions that I know of, for installing IIRF, are in the .chm doc, which is available on the downloads page.

If you get the latest version of IIRF (either v1.2.16 or v2.0) there is a new feature that allows you to query the status of the filter through a browser request.  It requires the use of the StatusUrl directive in the ini file.

I don't know what you mean by "Run test apps in bin directory are run, they cannot find the .dll. I'm assuming the apps attempt to use via http request, rather than a straight load."  The test applications are just applications.  They load the IIRF dll at runtime in a standard way.  The DLL needs to be on the path or in the home directory, or in the same directory as the EXE, in order for the EXE to find the DLL. 

What message do you get exactly, when "they cannot find the .dll" happens?  How do you run these things?  You need to be running them from the command line - is that how you do it?  Double-clicking on the EXE within Explorer will not work.

 

Jul 25, 2009 at 12:58 AM

Cheeso;

Thanks for that.

I didnt realize that the tester loaded the dll, but thought that it made an http request back to "localhost", rather than loading the dll. After ensuring path is set, all tools are working. setting the directive showed that IIRF was working all along.

Thanks for the help!

 

-avi