I've used the Walkthrough: Creating a Custom ASP.NET Web Service from MSDN to create my cusom WCF Service and deploy to my Sharepoint 2010 server.

http://myserver/_vti_bin/randomchatwebservice.asmx seems to work fine and it shows service methods. But I get "The webpage cannot be found" when I try to reach http://myserver/_vti_bin/randomchatwebservice.asmx?wsdl or http://myserver/_vti_bin/randomchatwebservice.asmx?disco.

I have RandomChatWebServicedisco.aspx and RandomChatWebServicewsdl in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and spdisco.aspx file has

<contractRef
  ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(
         spWeb.Url + "/_vti_bin/RandomChatWebService.asmx?wsdl"),
         Response.Output); %>
  docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(
            spWeb.Url + "/_vti_bin/RandomChatWebService.asmx"),
            Response.Output); %>
  xmlns="http://schemas.xmlsoap.org/disco/scl/" />
<discoveryRef
   ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(
          spWeb.Url + "/_vti_bin/RandomChatWebService.asmx?disco"),
          Response.Output); %>
  xmlns="http://schemas.xmlsoap.org/disco/" />

definitions. What seems to be wrong?

link|improve this question
1  
if you answered yourself to the question, please don't edit your post, but add an answer. You will be able to mark as answer in few days, and the question will appear solved in the pages of the site – Steve B Jul 13 '11 at 11:49
guys did anyone find a solution for the above? – user4679 Sep 7 '11 at 11:03
feedback

2 Answers

@Melih Öztürk posted a solution to his own question:

contactRef part of the WSDL file seems to be not well-formed. I changed it and problem solved.

I'm posting this as a community wiki since this question seems to be abandoned. If anyone has more information, feel free to add it!

link|improve this answer
please explian what u did..even i am facing same issue.. – jenny Dec 19 '11 at 10:27
Sorry, I don't have any more information. The only lead that @Melih posted was to check the WSDL. – Kit Menke Dec 25 '11 at 16:58
feedback

My recommendation is to deploy the custom web service to the Layouts (_layouts) folder rather than the ISAPI (_vti_bin) folder. All the issues with the disco and wsdl generation go away.

I posted a walkthough for this on my blog, Walkthrough: Creating a Custom ASP.NET (ASMX) Web Service in SharePoint 2010

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

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