You are currently offline, waiting for your internet to reconnect

[SDP 3][792dcf9b-14e5-4b78-b9ed-ca7e77318ce8] Access 2013 Baseline for SharePoint 2013 Diagnostic (SPAccessServices2013)

This Access 2013 baseline for SharePoint 2013 (SPAcessServices2013) diagnostic is designed to detect problematic baseline conditions that may exist for Access 2013 running on Microsoft SharePoint Server 2013.

Important The problematic conditions are checked only on the server on which this manifest is executed. To make sure that you have maximum coverage, we recommend that you run SPAccessServices2013 on each computer in the Microsoft SharePoint farm.

This article explains the operation of this diagnostic package.

Required permissions

The rules in the diagnostic package leverage the SharePoint Windows PowerShell snap-in to get information about your farm. Therefore, the account that is used to run the diagnostic package must either be the farm account or have been given the required permissions through the Add-SPShellAdmin command. Note that the farm account is the account under which the timer service and central administration site's application pool are running.

Some rules in this diagnostic package also must have local server administrative privileges to leverage remote and local administrative tools and also to access secure system locations such as the registry. The following table can be used to reference the permissions that are required for each rule.
Permission codeDescriptionRequired permission
1Use SharePoint Windows PowerShell Cmdlets to interact with the SharePoint farm.Farm Administrator
2Run queries against SharePoint databases.Farm Administrator
3Access server administrative tools.Server Administrator
4Access files and other resources on the server.Server Administrator
More information
This article describes the information that may be collected from a computer when you run SPSearch2010 package.
DescriptionFile Name
This is the actual results of the SPAccessServices2013 manifest. This is what is displayed back to the user to indicate that status of each rule that is executedResultReport.xml
This is an xlst transform that formats the results in the ResultReport.xml file. It contains no customer data.Results.xsl
This file contains debug information that may be generated during the execution of the manifest. It also contains timings on each of the rules that are run. It may contain customer data; however, every attempt has been made to minimize the amount.SPAccessServices2013.O.debugreport.xml
This file contains additional debug information for the manifest execution. It may contain customer data; however, every attempt has been made to minimize the amount.Stdout.log
This file contains the environmental information for each computer in the farm. The information that is captured includes the following:
  • Computer name
  • Operating system name
  • Last reboot/uptime
  • Computer model
  • Processors
  • Computer domain
  • Role
  • Operating system language
  • Time zone
  • Total RAM
  • Drives (total and free space available)
This file contains SQL Server information from the SQL instance that hosts the SharePoint Configuration database. The information that is captured includes the following:
  • ProductVersion
  • ProductLevel
  • Edition
  • ServerName
  • InstanceName
  • MaxDegreeOfParallelism
  • LastUpdateDate
  • IsClustered
  • IsFullTextInstalled
  • IntegratedSecurity

Access Services

Rule IDTitleRequired permissionsDescription
0D083700-9E7D-454C-9C65-CA85FFE33C81Check if SQL Server 2012 Native Client is installed4
64D41BD1-637D-C0DE-DE07-5E0E4F789B2FCheck if Access Services service instance is started1
8C07662E-E2D9-4100-A322-E588B2ABB2E7Check if SharePoint Administration service is started1
9C1AF7F0-C672-4356-B16B-6209CDDFD78DCheck if App Prefix is configured for hosted apps1
A8A775F6-49CE-4812-B3BD-87DD4E9ECA59Check if Secure Store encryption key is generated1
C3F8786F-6579-C0DE-DE07-5120BBC095E7Check if Secure Store service instance is started1
CDAD1EE8-ACCC-411B-AB20-E41BAF6F2475Check if App Domain is configured for hosted apps1
D93EE64F-B1F3-45E4-B76D-CF5A921F2C89Check if Load User Profile Property is enabled for Access Services App Pool4
FFE7E279-3FB0-48A5-BF67-DD1FB5DAF7A7Check if Access Database Service 2010 service instance is started1
D99E7B35-7784-C0DE-DE07-757D758A268DCheck if App Management service instance is started1
853D0F41-8B26-45FF-8A4E-881A37F918A9Check if Subscription Settings service instance is started1
B4BF847D-21DF-4A7F-8EB7-0A3839440FA6Check if SQL Server 2012 DacFramework.msi is installed1, 4
11920692-45BD-4FB3-B8DC-DE26B813CB95Check if SQL Server 2012 component, SQLLocalDB is installed4
09307337-2513-4335-84E1-89A1D5C2E674Check if SQL Server 2012 Transact-SQL ScriptDom is installed4
C48EFD7C-27DD-4B5F-987F-90E372434327Check if System CLR Types for SQL Server 2012 is installed4
B10424F1-8AFB-4DB8-B12B-0A84098FEC66Access Services Application Database server name1

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 2858697 - Last Review: 08/28/2013 21:12:00 - Revision: 12.0

Access Services in Microsoft SharePoint Server 2013

  • kbprosharepoint kbdiagnostics KB2858697