WCF Service hosted in IIS6 gets 404 in Production

Question

I have built a simple WCF Service and deployed it to IIS6, and I'm noticing that it works in my Dev and Staging environments, but not Production. Every time I try to hit the service metadata link, I get a 404 page.

I've checked IIS config everywhere I can think of and they're identical, so the only difference I can think of is that the Production environment is load balanced.

Does anyone know of any issues with running a WCF service behind a load balancer, and how can I get around that? Am I on the wrong track, is there another common problem I should look into?

Answer 1

You need to setup wild card mapping on IIS6. This link seems like a good step by step guide.

Try reading up on the differences between the integrated pipeline vs classic pipeline on IIS7