Showing posts with label Exception from HRESULT: 0x80131904. Show all posts
Showing posts with label Exception from HRESULT: 0x80131904. Show all posts

22 February, 2013

Cannot Publish Access Database to Sharepoint 2010 Server


Happy Friday to all of you :)

Worked for almost 10 hours to resolve this issue that I am going to explained in detail manner.

Okay, here we go…

Problem Description: We have published an Access 2010 database to SharePoint 2010 site. The publish was successful but received an error

Error Messages:
Message#1:
Exception message: Exception from HRESULT: 0x80131904

Message#2:
The server was unable to process the request due to an internal error. For more information about the error, either turns on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

Message#3:
I get this error in the event viewer:
Log Name:      Application
Source:        Microsoft-SharePoint Products-Access Services
Date:          22/2/2013 10:03:43 AM
Event ID:      3
Task Category: Data Layer

Message#4:
An error has occurred. Please try again.

If I review the series of error message then it’s not completely clear where its dragging out and in which direction.

Troubleshooting done on this issue:
1.    Manage Services on Server – Access Database Service is started

2.    Manage Services Applications – Review the access Settings

3.    Manage Web Applications – Make sure application is associated with the Access Service

4.    Make sure all the features are activated
o   Central Admin --- System Settings --- Manage Farm Features --- Access Services Farm Feature
o   Central Admin --- Manage Web Applications --- Select Web Application hosting the Access Services Site --- Manage Web Application Features --- SharePoint Server Enterprise Web application features
o   Site Collection --- Site Settings -> SharePoint Server Enterprise Site Collection features
o   Site Collection --- manage Site Settings --- SharePoint Server Enterprise Site features

Microsoft Theory:
If Access Services is activated on an Application Server, then you will also need to turn on the Microsoft SharePoint Foundation Web application Service, thus turning that machine into a WFE/APP server. Problem with this approach is that it could affect your licensing agreement because licensing depends on the number of WFE’s your farm has. Hence, the workaround for this issue is to enable the Microsoft SharePoint Foundation Web Application service on the server running Access Database Services.

As per this, we have made the changes and started the access service on the same server where Microsoft SharePoint Foundation Web application Service is running.

5.    Make the changes in web.config file so that the error should be more clear and accurate one.  Changes includes: callstack=True and customerror=off
6.    Re-provision the access, session state, security token service applications

Resolution:
We have provided access to the account associated with Access Services the dbo permission for the content database in SQL Server for the particular site collection for which I was trying to add a Web Database.

If you have any queries/questions regarding the above mentioned information then please let me know.

Thank you.