The script that do this are iis7connect.bat and iis7remove.bat, which
can be used to add and remove the required IIS configs. If you run these
from powershell, you can see if any part of the process is throwing an
error and what may be causing the default document part to fail.
If you want to configure the default document manually, I wrote about
how to do that here:
http://groups.google.com/group/railo/browse_thread/thread/8706a5a4b025f393
Let us know how it goes.
-Jordan
If the isapi_redirect.dll is actually getting run, there should be a log
file of the error it's getting in c:\railo\tomcat\logs\isapi_redirect.log.
If no log file exists, that means that the isapi_redirect.dll is not
being executed and that there's a problem with the IIS hand-off. Turn on
debugging error messages in IIS and see if that yields additional
information, and you could also check Windows Event Viewer to see if IIS
is throwing any errors that it's not displaying.
If all else fails, please tell me what IIS modules you have installed
and I can attempt to duplicate the problem in a dev environment to come
up with a fix.
-Jordan
--
Warm regards,
Jordan Michaels
Vivio Technologies
http://www.viviotech.net/
509.593.4207 x 1001
> All Handler Mappings
> http://i53.tinypic.com/mwwdxl.jpg
Did you add the cfc and cfm entries by hand? The batch files don't add
those so I'm wondering where they came from.
Also check the uriworkermap.properties file (in c:\railo\tomcat\conf\)
and see where the "/" entry is mapped. It should be mapped to the
default ajp13 worker. If it's not, then that would explain why the
connector isn't picking it up after the handler mapping is passing off
to it.
-Jordan
--