Classic ASP doesn't work once Ionic installed?

Topics: User Forum
Sep 7, 2007 at 4:51 PM
Edited Sep 7, 2007 at 4:54 PM
I'm testing Ionic on a Win 2003 server running SharePoint MOSS 2007. It seems to work perfectly for most things, but I'm having a problem with a legacy classic ASP app.

Not straight away, but soon after adding Ionic to the list of ISAPI filters for the website, all the classic ASP pages start to fail. They just return blank pages. If I remove Ionic from the ISAPI list they start working again immediately.

My Ionic INI file is very simple, with just a couple of test rules that don't look anything like those used by the classic ASP app. Can anyone shed any light on what might be happening and how I might fix it?

My INI file looks like this:

# IsapiRewrite4.ini

# sample ini file for the ISAPI rewriter.
#
# comment lines begin with #
#
# These are the currently supported directives for the ini file:
#
# IterationLimit
# MaxMatchCount
# RewriteRule
# RewriteLog
# RewriteLogLevel
# RewriteCond
#
#
# Check the examples below for how to use each one.
# See the Readme.txt for full explanation of the rules here.
#
#
# Wed, 07 Sep 2005 09:01

# Verbose logging - can be turned on for debugging when needed
#
# RewriteLog C:\inetpub\wwwroot\rewritelog
# RewriteLogLevel 5

RewriteRule ^/shorturl /schoolmanagement/pages/main.aspx [L]
RewriteRule ^/policies/? /schoolmanagement/schoolpolicies/pages/main.aspx [L]