SharePoint 2016, Sharepoint 2013, Sharepoint 2010, Windows Server 2012, Sql Server 2012,2014,IIS, Active Directory,User Profile Service, Managed MetaData Service, Search Service, Topology, Web Application, IIS, Site collection, List, Library, PowerShell, office web app, Windows Authentication, NTLM, Kerberos, Saml, ADFS, Active Directory Import, MIM, Issue with Opening an Access Services App in SharePoint 2013 – SharePoint

Issue with Opening an Access Services App in SharePoint 2013

Scenario:

Just think about, you configured Access Services and then install the app which will use the Access Service. Now you trying to open the App home page and get the following error on page:

“Sorry, we could not Load this App. We weren’t able to load the app’s homepage. Please let your administrators know about this.”

TECHNICAL DETAILS

Correlation ID: id

“Now if you search for the Correlation id in the ULS Logs and found the below error:

11/29/2013 17:32:09.29 w3wp.exe (0x1C84)                       0x0938  Access Services

Database Connection Management af34v

Exception An error occurred reading application properties while opening a command scope. Microsoft.Office.Access.Services.VersioningException: Sorry, the server doesn’t recognize the version of the app you are trying to open.     at Microsoft.Office.Access.Services.Database.ApplicationDatabaseUpgrader.GetSystemSchemaUpgradeStatus(Version systemSchemaVersion)

And

11/29/2013 17:32:09.30 w3wp.exe (0x1C84)                       0x0938  Access Services

Database Connection Management ahi5g

Exception Exception occurred opening application database connection. Microsoft.Office.Access.Services.VersioningException: Sorry, the server doesn’t recognize the version of the app you are trying to open.     at Microsoft.Office.Access.Services.Database.ApplicationDatabaseUpgrader.GetSystemSchemaUpgradeStatus(Version systemSchemaVersion).

 

Reason:

  • So far I could not find the reason for this error

 

Solution:

  • I did not install the March PU to my SharePoint 2013 Farm. So easy fix, just install the March PU and let this error go away.
  • March PU is mandatory, due to a change in the package configuration introduced after SharePoint 2013 RTM the March Public update is a mandatory requirement in order to install subsequent SharePoint 2013 Updates

 

Other Resources:

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *