« Previous Next »

• 06-29-2009, 12:42 PM

  fhsdavid Joined on 06-29-2009, 3:45 PM Posts 1

  Rewrite module disappears when Shared Configuration is enabled. Reply Contact Hello.. I'm hosting our sites on a small web farm and use the Shared Configuration feature to sych up IIS. We have a hardware load balancer where an SSL certificate is installed. We have an issue where the default 302 redirect functionality is redirecting to http (instead of https) if the url does not end in a slash. For example:  https://www.thedomain.com/Demo1 is getting redirected to http://www.thedomain.com/demo1/  I can solve this issue using the URL Rewrite Module but I cannot get it installed and have shared hosting enabled at the same time. I disabled shared hosting to install the module, and I've installed it on all the web servers. But as soon as I re-enable shared hosting the module disappears from IIS. Additionally, any site that has had a rule written for it  (written while shared config was disabled) now throws a 505.19 Internal Server Error saying it doesn't recognize the elements that were added to the web config.  Any thoughts? Thanks

  Tags: URL Rewrite ModuleShared Configuration

• 06-29-2009, 1:14 PM

  In reply to

  anilr Joined on 05-23-2006, 10:13 PM Redmond, WA Posts 2,343

  Re: Rewrite module disappears when Shared Configuration is enabled. Reply Contact You have to re-export your applicationhost.config to the shared configuration location after installing url-rewrite - best way would be to remove each server from shared configuration, install url-rewrite, for the first server export configuration to new shared location, for the other, just point them to the new location after installing url-rewrite. Anil Ruia Senior Software Design Engineer IIS Core Server

• 06-29-2009, 1:24 PM

  In reply to

  CarlosAg Joined on 02-19-2003, 2:23 AM Posts 335

  Re: Rewrite module disappears when Shared Configuration is enabled. Reply Contact The fact that you are getting a 500.19 means that something failed to install correctly since it looks like the Schema is not getting updated correctly in the local server (windir\system32\inetsrv\config\schema) I would recommend installing again and follow a procedure like: a.       Take 1 server and copy the shared configuration files into the local system32\inetsrv\config directory (ApplicationHost.config and Administration.config) to ensure you have the most recent version locally.b.      Disable shared configuration of that server by modifying the "enabled" attribute in the inetsrv\config\redirection.config file.c.       Install the module in the server locally.d.      Repeat a-c until all the servers have been updated. e.      Copy the system32\inetsrv\config\ (administration.config and applicationHost.config) files from one of the machines and overwrite the ones in the shared configuration which should now include the module. f.        Go through every server again, and modify the "enabled" attribute in redirection.config from that server to true.