May 4th, 2011 Published by
Leave a comment

How to Fix a Common SharePoint 2010 OData Error

OData capabilities are appearing all over the place in recent Microsoft products like SharePoint Server 2010, Excel 2010 (using SQL PowerPivot), Windows Azure Storage, SQL Server 2008 R2 and others.

According to Microsoft, OData “… applies web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores.”.

Recently I was working with OData for a Fpweb.net SharePoint Server 2010 hosting client, and encountered the following error:

"Could not load type 
'System.Data.Services.Providers.IDataServiceUpdateProvider' 
from assembly 'System.Data.Services, Version=3.5.0.0, Culture=neutral, 
PublicKeyToken=b77a5c561934e089'."


So what the heck does that mean?!?!
This error indicates that there is a missing assembly (System.Data.Services) on the SharePoint 2010 Web server which is required for processing the OData requests from ListData.svc.

How can I fix this SharePoint Ninja-Style?!?!
Good question, grasshoppa… To remedy this error you will need to install the ADO.Net Data Services Update for .NET Framework 3.5 SP1 (x64). 

Important Notes About Installing the Update:

  • Notice that there are different versions for different operating systems.
  • Be aware that the installer will ask you to reboot after the installation completes.

How do I know if I fixed the OData Error?

Browse to http://[yourdomain]/_vti_bin/ListData.svc. If your XML SharePoint data is returned, you’ve done it!

WINNING! As always, please hit me with your questions/comments/success stories in the comments area below!

About Andy Milsark

Andy Milsark has written 36 post in this blog.

Andy, a proud new daddy, enjoys learning as much as humanly possible about SharePoint, PowerShell, and Private Cloud Automation. When he needs a break from battling SharePoint, he can be found throwing around weights at the local Crossfit gym. Follow Andy on Google+

VN:F [1.9.22_1171]
Rating: 9.5/10 (2 votes cast)
May 4th, 2011 3:55 pm CDT
Published by Andy Milsark in Engineering & Development, MOSS 2010, SQL Server 2008
Tags: , , , , , , , , , Andy Milsark, Milshark

 
  1. Derek Watson
    May 4th, 2011 at 16:12 | #1
    Reply | Quote

    Great post, Andy!

  2. Andy Milsark
    May 4th, 2011 at 16:13 | #2
    Reply | Quote

    @Derek Watson
    Thank you sir!

  3. Mircea
    June 4th, 2011 at 12:03 | #3
    Reply | Quote

    Cool! That’s a clever way of looinkg at it!

  4. Michael
    June 13th, 2012 at 09:31 | #4
    Reply | Quote

    I have to ask, why does this change “all of a sudden,” I’ve had users running REST queries without an issue and then out of nowhere this error is generated. I haven’t installed any patches or anything.

    Weird.

  5. Andy Milsark
    June 22nd, 2012 at 10:33 | #5
    Reply | Quote

    @Michael
    Michael, I haven’t heard of any specific patch or update that may have broken this recently. Maybe one of your web servers doesn’t have the same patch level as the rest?

  6. Dan Kline
    December 12th, 2012 at 20:40 | #6
    Reply | Quote

    I’m experiencing an unusual issue. When I try to use the ListData.svc it hangs forever. The browser thinks it’s still downloading, but the progress bar never advances past the half way mark. Have you ever experienced this behavior or do you have any idea how to troubleshoot it?

  7. Andy
    December 13th, 2012 at 19:06 | #7
    Reply | Quote

    @Dan Kline
    Hi Dan.

    I have not seen this behavior. Have you tried an IISRESET to clear out the webserver’s memory?

  1. May 4th, 2011 at 17:08 | #1
    How to Fix a Common SharePoint 2010 OData Error | Translogistics