As part of a recent deployment there were a number of WCF Web Services which were required to be deployed onto our target server.
We encounted a problem where the deployment seem to have installed correctly, but did not work when tested.
Checking the configuration settings validated our assesment of a correcly configured install so what went wrong?
Answer: URL matching is case-sensitive!
For what ever reason (which I am yet to determine) the BizTalk msi package which I had created, when run, created a virtual directory which did not preserve the same casing for the AppRoot address.
Upon researching this issue it seems to have two options to solve this issue:
- Change the AppRoot address in the c:\windows\system32\inetsrv\metabase.xml (in Windows Server 2003)
- Removing the virtual directory, clearing the ASP.NET Temporary Files cache, manuall re-creating the virtual directory again.
More information on this issue can be found here.