NB! This Wiki is based on a previously released white note paper outlining Access Services 2013.
Access Services in SharePoint Server 2013 allows people to host Access databases in SharePoint within the context of an Access app. Access apps for SharePoint are new in SharePoint Server 2013 and you will build them using the Access 2013 desktop client.
You can create, edit, and update linked Access 2013 databases and then view them directly from the app.
You can use Access Services 2010 to view and edit a web database that was created using Access 2010 and SharePoint 2010, and you can republish them to SharePoint Server 2013. You can't create a web database using Access Services 2010 in SharePoint 2013, but
you can import Access 2010 web databases into an Access app.
Access apps are SharePoint apps, therefore for Access Services to run Access app, SharePoint Server 2013 needs to be configured as a SharePoint app server. In addition, Access Services requires SQL Server 2012 to run.
Each Access app creates its own database on SQL Server. In SharePoint Server 2013, SQL Server 2012 is the only version of SQL Server that can serve as the SharePoint Server 2013 application database server for Access Services. . For installing SQL Server
2012, refer to the article
Installation for SQL Server 2012 .
The following configuration example is based on a previously released white paper, and describes a single on-premises Farm setup where the Service Applications and the Configuration Database are stored on the same database server that Access Services uses
as its application database server.
To open the SQL Server Security Logins table, open SQL Server Management Studio for the SQL instance. Expand the Server Objects. Under Security, select Logins.
Expand Logins and locate the SharePoint Service Account. Then right-click the account name and select
Properties . Select Server Roles .
If you have installed SQL Server 2012 using Windows Authentication Mode you need to change the mode as follows:
To set the Enable Contained Databases property:
You must enable TCP/IP and Named Pipes protocols in the SQL Server Network Configuration. Open SQL Server Configuration Manager and select
Protocols for MSSQLSERVER to enable both protocols. By default, SQL Server enables TCP/IP during installation of SQL Server. If the TCP/IP status is not
Enabled, enable it when you enable Named Pipes.
After you have installed SQL Server, you must set the following ports to communicate through Windows Firewall:
To set the ports, take the following steps:
When you are done the entries, TCP 1433,
TCP 1434 and UDP 1434 will be listed in your
Inbound Rules dialog.
In order for Access Services to function properly, it is recommended that you install the following SQL Server 2012 Feature Pack components on the SharePoint Server 2013 computer:
You can download the
Microsoft SQL Server 2012 Feature Pack components from the Microsoft Download Center. You will also need to configure the Load User Profile Setting in IIS, as described below.
IIS Application Pool Load User Profile Setting
A change to the IIS Application Pool for Access Services is necessary for you to be able to open linked SharePoint tables. You must set the Load User Profile setting to true because ADS requires a user profile to load LocalDB. A restart of the server is
necessary after you change the setting:
The SQL Server 2012 Feature Pack components are needed for various essential features of Access 2013. LocalDB and the Load User Profile setting are needed for reading from external SharePoint lists, and the Native Client is needed for loading saved app packages.
If you have not already done so, you will likely want to set up backups of your SQL databases. Even if Access Services uses the same instance SQL Server 2012 as SharePoint Server 2013, simply configuring SharePoint backup will not back up Access data; you
will need to configure SQL Server backup. If you are unfamiliar with setting up SQL database backups, refer to the TechNet article
Backup and Restore of SQL Server Databases.
Before you start configuring Access Services, make sure that SharePoint 2013 is properly installed and that you have configured it for SharePoint apps.
If you haven't configured your SharePoint installation for SharePoint apps, follow the directions in the TechNet article
Configure an environment for apps for SharePoint 2013. As the article states, you must set up a Domain Name Services (DNS) domain name to provide a host name for installed apps.
You must also create a DNS record so that the domain name will resolve correctly.
When you have configured SharePoint 2013 for SharePoint apps, follow these basic steps to configure Access services:
When the above steps have been completed, you should be ready to create a new Access Custom web app from your Office 2013 client.
After having enabled SharePoint 2013 for apps, you must configure your SharePoint farm.
The Welcome screen appears and asks how you want to configure your SharePoint farm
Access Service requires a minimum of the following services:
You must create a SharePoint site collection to manage your Access apps. After SharePoint 2013 Server finishes the services, it prompts you to create a site collection. If it does not, go to Central Administration and select
Create Site collection under Application Management.
Setting Permissions on the site
Generating Secure Store Security Service key
Access Services requires the Secure Store Service to be started and enabled. Access Services requires you to generate a Secure Store Service security key for it to run properly.
Set the key for the Secure Store Service Account by following these steps:
Create SQL Server 2012 Application Database Server
If you have already installed SharePoint 2013 using a SQL Server 2008 R2 database, you must assign a separate SQL Server 2012 application database server for Access Services.
To create the server, open Central Administration.
In order to create an Access App, you need to have Office 2013 installed on a computer running on Windows 7 or Windows 8.
To create an app, do as follows:
To further build up your app with tables or schema, or to get an overview of alternate ways to create or download Access Apps, please refer to the following blog post from the Office 2013 Access Team:
Could anyone tell me why the "Configure SQL Server 2012" header doesn't show up in the TOC ?
I removed Bjoern H Rapp from the tags
There is a bug in TOC - it can not currently process 0 (and some other characters). So, for such cases we need to manually adjust name anchor in HTML view
Gokan Ozcifci edited Revision 38. Comment: Tag
Hello, this process is fine for SharePoint 2013 running on premise, and for SQL Server 2012 and Access 2013 running on premise. But, if the user is subscribing to SharePoint Online, Office 365, the user loses control of the SQL Server backend, which ends up somewhere in Azure. The user will not have the ability to back up the SQL Server table created for the SharePoint 2013 App. This can be a very big problem for the user. The only workaround I could find was to display the App content in "Datasheet" view, copy, and then paste to a Excel spreadsheet for local access via a local Access 2013 database. A better solution would be to simply publish the Access 2013 database as a list in SharePoint Online.