Since auto-generated disco and wsdl are unaware of the SharePoint service URL virtualization, results returned by web service become unreliable. Simple test 1. Go to 12isapi and copy mx, px and px to 12templatelayouts 2. Imagine what would happen if you have different access permissions for each site level? Or what if your web service logic is heavily dependent on the running site context? Note, you can always check if your custom web service has maintained correct URL virutalization by viewing its Service Description.
Jan 7, 2009. Why you should only deploy web service to 12isapi vti_bin)?. He followed the instructions from msdn article Walkthrough: Creating a Custom Web Service. Mcts SharePoint 2010, 2007 mcpd Enterprise Application. Nov 4, 2011. I m new to web services and i ve been trying to create a custom one using this tutorial: px. \"Everything looks fine except.\" - he said, at this stage I knew what the problem was and his description of the problem confirmed it. "Everything looks fine except the web service function call returns an incorrect and unexpected result". Apr 25, 2011. How to Create an asmx Web Service on SharePoint 2010, Using Visual Studio 2010. Next, we will be creating the web service. Right click on.
Correct soap path. Incorrect soap path. If you are new to SharePoint or like to know more about how SharePoint handles http requests (SPRequestModule) and SharePoint architecture/infrastructure. I recommand you to read these two articles from msdn and TechNet For WSS 3.0 (SharePoint Server 2007) - Inside Sharepoint Building Your SharePoint Infrastructure For SharePoint Portal Server 2003 - Architectural Overview. Because _vti_bin (12isapi) virtual folder has been configured to serve requests differently compared to other virtual folders in the SharePoint site. Every web service request made to this directory will be parsed by px and px files in 12isapi.