(NOTE: This post only relates to SharePoint Server 2010, sometimes referred to as the Enterprise version of SharePoint. )
SharePoint Server 2010 allows web databases to be created in MS Access, then published to a SharePoint Server site. Access Services running on the SharePoint Server site powers the database in the browser.
I’ve been having problems getting reports to display correctly in the browser, in 3 environments. Here’s what was needed to solve the problem. Maybe this will help someone else.
1. VM environment
In my own virtual machine, I had to turn on ASP.Net session state (not to be confused with State Service). This post by Mark Arend showed me what I needed to do. His explanation made it very easy, and my reports started working correctly.
2. Hosted SharePoint environment
I have a commercially hosted SharePoint Server 2010 environment that I use for development and testing. Reports were not working in that environment. Here’s the error message I was receiving:
"Dataset default" reporting error
They turned on session state, and the reports were still not working. But now, the error message was slightly different:
"ADS" error
I googled the error message and found this post by Jonathan Masts that led to a technet article that explained how “To install the Reporting Services Add-in for Connected Mode”. My host provider followed step 3 of that section of the article (modify the rsreportserver.config file to add the ADS extension) and voila! my reports worked like a charm! I’m guessing that ADS stands for Access Data Services.
3. Client environment
I’m doing some development work for a client, and I’m getting the same “ADS” error I was getting in the hosted environment after they turned on session state. Hopefully, this post will provide the fix needed to get the reports working in that environment as well.
Happy SharePointing!
Keith Hudson
.