Comments on: URL Case-Sensitivity on WCF Web Services Published from BizTalk 2006 R2 to IIS http://www.tfabraham.com/blog/2008/03/url-case-sensitivity-on-wcf-web-services-published-from-biztalk-2006-r2-to-iis/ Visual Studio, .NET, BizTalk Server, SQL Server and more... Thu, 15 Jul 2010 12:21:08 +0000 hourly 1 http://wordpress.org/?v=3.0 By: sixeyed http://www.tfabraham.com/blog/2008/03/url-case-sensitivity-on-wcf-web-services-published-from-biztalk-2006-r2-to-iis/comment-page-1/#comment-3 sixeyed Tue, 19 May 2009 04:42:29 +0000 http://www.tfabraham.com/blog/?p=113#comment-3 Found the same result with a different issue, the IIS metabase had the app root in uppercase (c:\windows\system32\inetsrv\metabase.xml in Win2003). Changed from this: <IIsWebVirtualDir Location ="/LM/W3SVC/1/ROOT/App.Service.Name" AppFriendlyName="App.Service.Name"" AppRoot="/LM/W3SVC/1/ROOT/APP.SERVICE.NAME" to this: <IIsWebVirtualDir Location ="/LM/W3SVC/1/ROOT/App.Service.Name" AppFriendlyName="App.Service.Name"" AppRoot="/LM/W3SVC/1/ROOT/App.Service.Name" , ran IISRESET and all well. Found the same result with a different issue, the IIS metabase had the app root in uppercase (c:\windows\system32\inetsrv\metabase.xml in Win2003). Changed from this:

Location =”/LM/W3SVC/1/ROOT/App.Service.Name”

AppFriendlyName=”App.Service.Name”"

AppRoot=”/LM/W3SVC/1/ROOT/APP.SERVICE.NAME”

to this:

Location =”/LM/W3SVC/1/ROOT/App.Service.Name”

AppFriendlyName=”App.Service.Name”"

AppRoot=”/LM/W3SVC/1/ROOT/App.Service.Name”

, ran IISRESET and all well.

]]> By: Elton http://www.tfabraham.com/blog/2008/03/url-case-sensitivity-on-wcf-web-services-published-from-biztalk-2006-r2-to-iis/comment-page-1/#comment-158 Elton Wed, 05 Nov 2008 12:20:42 +0000 http://www.tfabraham.com/blog/?p=113#comment-158 Certainly did, thanks Thomas - I hadn't thought to check the ASP.NET cache. Worth noting that if you modify the Receive Location (in desparation) to use the wrong case , you'll be able to navigate to the .svc file - but likely to have further issues with downstream code expecting the original case. Certainly did, thanks Thomas – I hadn’t thought to check the ASP.NET cache. Worth noting that if you modify the Receive Location (in desparation) to use the wrong case , you’ll be able to navigate to the .svc file – but likely to have further issues with downstream code expecting the original case.

]]>