SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've used the "Walkthrough: Creating and Implementing a Custom WCF Service in SharePoint Foundation" from MSDN to create my cusom WCF Service and deploy to my Sharepoint 2010 server.

The wsp is globally deployed and when I access the service in the browser using the url: http://myserver/_vti_bin/Revert.svc/MEX everything seems ok. The problem is when I need to access the service on another webapplication on the server: This gives me a "HTTP 400 Bad Request" error. This webapplication was created on port 81, so I can access the service by using the url: http://myserver:81/_vti_bin/Revert.svc/MEX.

I've set up AAM and also added the binding for port 80 in the IIS Management Console. I can use the builtin services like "listdata.svc" using the url, but not my custom wcf service. Does anyone know why?

Best Regards ElinK

share|improve this question

Have you added the host name in the binding settings in the IIS Management Console? If not the WCF service can not identify the correct urls.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.