No umbraco document matches the url 'http://xxxxxx.local/isapirewrite.aspx?path=/home/'
I have an interesting error on 2 machines here, it's pretty much a default umbraco 4.7 install that is throwing this error when directoryUrls are switched ON. Other rewrites in the urlRewriting.config don't work either.
The site works fine when I open it up in IIS Express (using Web Matrix).
What I find curious is that it's looking for /isapirewrite.aspx apparently and I can't find any reference to isapirewrite in the umbraco source code.
I Googled loads but couldn't find this problem related to Umbraco. I did think I should maybe repair the handler mappings for asp.net (http://support.microsoft.com/kb/325093) but that didn't work either. I also uninstalled/reinstalled IIS.
The machines are both (slightly older) 32 bit Windows 7 machines that have been used for other types of websites than Umbraco (I don't know much of their history).
Anybody have any ideas what might be wrong and why it's looking for isapirewrite.aspx?
Check to see if Helicon Isapi rewrite app has been installed and if not used anywhere else, remove it. Had issues with other sites using that library before.
Did you install ISAPI Rewrite via Web PI for another site on the same machine? It looks like the machine-level config has been updated to automatically pass requests through ISAPI Rewrite. Suggest checking the HTTP Handlers at server level to see if there's anything listed - if so, remove it, and re-apply at specific site level.
Edit: ISAPI Rewrite requires a .ini file to function. Check to see if one is present in the site, if so, remove it and it should switch it off.
No umbraco document matches the url 'http://xxxxxx.local/isapirewrite.aspx?path=/home/'
I have an interesting error on 2 machines here, it's pretty much a default umbraco 4.7 install that is throwing this error when directoryUrls are switched ON. Other rewrites in the urlRewriting.config don't work either.
The site works fine when I open it up in IIS Express (using Web Matrix).
What I find curious is that it's looking for /isapirewrite.aspx apparently and I can't find any reference to isapirewrite in the umbraco source code.
I Googled loads but couldn't find this problem related to Umbraco. I did think I should maybe repair the handler mappings for asp.net (http://support.microsoft.com/kb/325093) but that didn't work either. I also uninstalled/reinstalled IIS.
The machines are both (slightly older) 32 bit Windows 7 machines that have been used for other types of websites than Umbraco (I don't know much of their history).
Anybody have any ideas what might be wrong and why it's looking for isapirewrite.aspx?
Check to see if Helicon Isapi rewrite app has been installed and if not used anywhere else, remove it. Had issues with other sites using that library before.
Did you install ISAPI Rewrite via Web PI for another site on the same machine? It looks like the machine-level config has been updated to automatically pass requests through ISAPI Rewrite. Suggest checking the HTTP Handlers at server level to see if there's anything listed - if so, remove it, and re-apply at specific site level.
Edit: ISAPI Rewrite requires a .ini file to function. Check to see if one is present in the site, if so, remove it and it should switch it off.
HTH,
Benjamin
I'd check to see if you have an ISAPI rewrite module registered in IIS for that site. If so, disable it.
Matt
@Simon / Benjamin Doesn't look like Helicon is installed (at least I can't find it in add/remove programs)
@Matt In which section should I look? In The Modules section Isapi and Rewrite modules are of type Native..
Hey Sebasiaan,
Have you checked in the ISAPI Filters section to see if anything is registered?
http://cheeso.members.winisp.net/Iirf21Help/html/153e7d87-ace3-4fd1-bead-86bd248f6087.htm (Step 3)
Cheers
Matt
@Matt BINGO!!
This has only been bugging me for 2 hours now lol.. Thanks, found a custom ISAPI rewrite version that was just wildly applied to the whole of IIS.
ARGH! I just marked my comment as the solution, where's the UNDO!?? :-(
Woo hoo! my first accepted answer in like ages =)
Haha, typical =)
At least I didn't get extra karma out of it.. ;-)
is working on a reply...