All my problems were due to a JRun 2.3.3 DLL floating around in the default scripts directory. So IIS was using this DLL (but writing in the log file in the directory with the JRun 3.0 DLL). So my conclusion is: Manual configuration of JRun 3.0 <-> IIS is as with JRun 2.3.3. Simply copy in the .ini and .dll file, add the .dll as an ISAPI filter and voila. /Morten ---------------------------------------------------------- I have now given up on the manual configuration of the IIS 4.0 <-> JRun connection and instead done as described in the ACG. 1) Installed JRun 3.0 on my JRun server 2) Added the JCP as described in the ACG 3) Installed JRun 3.0 on my IIS 4.0 server and used the wizard to make a connection to the JRun server. And now I have the exact same problem as with my manual install. The problem, to recap, is that when I access a .jsp page like http://www.myiis.dk/xsp/Language.jsp through the IIS I get an error: 404 Not Found /scripts/jrun.dll/xsp/Language.jsp: allaire.jrun.JRunServletException: The page /scripts/jrun.dll/xsp/Language.jsp could not be found. If I browse a non .jsp file like http://www.myiis.dk/xsp/Denmark.gif it works. It seems as if the filtering done in the jrun.dll goes wrong when it matches the *.jsp rule. The .gif files are as far as I can see matched by a /xsp rule. ANY ideas are welcome !!! /mbm ------------------------------------------------------------------------------ Archives: http://www.egroups.com/group/jrun-interest/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. ------------------------------------------------------------------------------ Archives: http://www.egroups.com/group/jrun-interest/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
