This forum has been moved here:
Helicon Tech Community Forum

ISAPI_Rewrite 3.0 (Forum Locked Forum Locked)
 Helicon Tech : ISAPI_Rewrite 3.0
Subject Topic: iis 7.5 shared configuration and rewrite
Author
Message |
brentnlisa
Newbie


Joined: 13 September 2011
Location: United States
Posts: 2
Posted: 13 September 2011 at 9:25am

We have been using Isapi Rewrite 3 and recently migrated to
new servers with IIS 7.5. We really like the shared
configuration for the ability to make IIS changes on a
single machine and it replicate to all other servers
calling the shared configuration. The problem is when you
turn shared configuration on, the .htaccess file is no
longer used. Is there a solution for running helicon with
shared configuration?
Back to Top
 
Guests
Guest


Joined: 01 October 2003
Online Status: Online
Posts: -160
Posted: 13 September 2011 at 9:34am

Hello,

Please, specify what you're doing for shared configuration, its type.

Regards
Andrew
Back to Top
 
brentnlisa
Newbie


Joined: 13 September 2011
Location: United States
Posts: 2
Posted: 13 September 2011 at 10:10am

IIS 7.5 Shared Configuration stores all the IIS Settings
from the master server. Any and all changes to the
master/primary server IIS configuration, is then
replicated
to the rest of the servers calling their configuration
from
the stored location designated by the primary.

Adding/changing/removing sites, adding/removing virtual
directories from sites, changing site configurations
etc..., it all is stored on a share that the other
servers pull the data from.

It stores it in 3 files. configEncKey.key for security,
applicationHost.config which is coded in xml, and
administration.config in xml

Edited by brentnlisa - 13 September 2011 at 10:15am
Back to Top
 
Guests
Guest


Joined: 01 October 2003
Online Status: Online
Posts: -160
Posted: 14 September 2011 at 4:49am

This issue is the exact copy of the one we've been recently investigating.
Below is the extract from one of our customers who has successfully solved it. He had only the first server working, other(copies) did not respond to any changes made to ISAPI_Rewrite.

Quote:
Based on our investigation, it didn't even seem to load the Isapi filter, but it did not error, and the process ran the page, just not the Isapi filter.

It was mentioned that there was an error from aspnet and it was unable to see the private bytes. That was attributed to the fact the IIS_WPG group was copied from another server, and therefore not
recognized in the AdminACL property on the servers that had copied the metabase.

The working NLB1 metabase was re-copied to NLB2.

Metabase explorer <http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17275> was used; to check AdminACL - and you found it in a few different places without the local IIS_WPG group.
You removed the unknown SPID from the list and then added the local IIS_WPG group.

The correct IIS_WPG group was added to these levels, with the appropriate permissions - and after that the Isapi filter seemed to be running.

The permissions are:
1) Server level - read
2) Mainsite\filters - (read/write)
3) W3svc\filters -(read/write)
4) Appools - (QueryUnsecureProperty)

Like I was telling you, this is very likely never an issue if you’re not running in an IIS6 web farm environment and not using IISSYNC to copy metabase settings across servers. However, if that is the
case, then this issue will almost certainly exist unless the administrator is explicitly guarding against it. In fact, Microsoft no longer recommends using the IISSYNC command because of these very
issues.

Here’s a screencast of me using MetabaseExplorer to examine the permissions that are listed above.
http://screencast.com/t/nykPuQx8F1Qq


Regards
Andrew
Back to Top
 

Sorry, you can NOT post a reply.
This forum has been locked by a forum administrator.

Printable version Printable version