I created a program that updates list items using the Lists web services. It works on my machine and other machine, but it does not work on the SharePoint build machine where it will become an automated process. I do not have access to test on the SharePoint build machine, I must send my programs to the administrator and he tries it.

Is the build machine capable of running web services?

  • 1
    Can you elaborate on the build machine? Is it running IIS? Is it in the SharePoint farm?
    – Dave Wise
    Commented Apr 12, 2011 at 20:14
  • I tried to say the actual single machine that is running SharePoint, IIS, Windows Server, SQL Server, and everything. We have a single machine farm.
    – sange
    Commented Apr 12, 2011 at 20:19
  • 1
    Do you have an actual error message?
    – Dave Wise
    Commented Apr 12, 2011 at 20:30
  • Sorry sange but I've had to downvote because of the lack of details and info in your question. Without some clues to go on then none of the answers can be little more than guesses.
    – Ryan
    Commented Apr 13, 2011 at 11:52

3 Answers 3


Have you disable the loopback check, so that the build server can make connections to itself

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1" -PropertyType dword


  • It was the loopback setting. We set this on the test machine and it worked so we will be redoing the program to not need the loopback setting.
    – sange
    Commented Apr 13, 2011 at 13:49
  • 1
    Eh? You can't redo the program to not need the loopback setting if you're relying on NT Authentication. Its a fundamental part to get NT authentication working.
    – Ryan
    Commented Apr 13, 2011 at 16:18

If WSS or MOSS is installed, then the machine is capable or running web services.

Assuming that your build machine does have SharePoint installed, then is there a web application / site collection created on it? Are you accessing the web services using a URL? If so, does the URL of that site collection exist on the build machine?

If you have code that runs against the list web service for example, your code will try to access http://sitecollection/_vti_bin/lists.asmx

If the site collection doesn't exist, then your code won't run.

If that doesn't answer your question, could you please give more details on the build machine?

  • Not true. I have worked on several projects where the build machine did not even have IIS installed, let alone SharePoint. All required SharePoint DLLs were copied to a specific folder on the machine and then used in the build.
    – Dave Wise
    Commented Apr 12, 2011 at 20:25
  • Yeah, it's not really what I meant to say. If WSS/MOSS is installed, then the web services can run is more like it. Edited my answer thanks! Commented Apr 12, 2011 at 20:30
  • You don't need the SharePoint DLLs at all if you are only using SharePoint web services.
    – Kit Menke
    Commented Apr 12, 2011 at 20:38
  • Well yes you do if it's SharePoint code. Your visual studio project will reference at least Microsoft.SharePoint.dll If that file isn't on the build machine your project won't build... Commented Apr 12, 2011 at 23:23
  • I think we are just talking about two different things. In order to talk to the SharePoint web services (ex: msdn.microsoft.com/en-us/library/…), you do NOT need SharePoint DLLs; you're just creating a service reference and communicating via SOAP. If you use the SharePoint API (ex: SPSite, SPWeb), then you do need the DLL.
    – Kit Menke
    Commented Apr 13, 2011 at 20:14

Things to check:

  • The build machine needs .NET installed (at least the version you targeted in Visual Studio)
  • Validate permissions: The account that is running the app on the build machine needs to have access to the list and the site it is updating (sounds like at least Contribute rights)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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