This article explains how to handle the issues with server load.

Errors while loading server information

SharePoint Server Information

Problem

While trying to load SharePoint farm settings with SPDocKit I received:

Error occurred while loading server ‘ServerName’.

Solution

In order to allow SPDocKit to successfully gather all the information about your SharePoint farm servers, the following permissions are necessary:

  • Local Administrator on the server
  • Windows Update service up and running

For more information on how to add the SPDocKit user to the Local Administrators group and how to start Windows Update service, read the following article.

Affected reports

  • Adding SPDocKit user accounts to the Local Administrator group on the server is needed for WMI remote access and to get information about Windows updates. In case you can’t give that kind of permissions due to security requirements, see lower for what you can grant instead this. The following reports will not be available:
    • Farm Explorer -> Servers in Farm -> Processors Info
    • Farm Explorer -> Servers in Farm -> Programs List
    • Farm Explorer -> Servers in Farm -> Available Windows Updates
    • Farm Explorer -> Servers in Farm -> Disks List
    • Farm Explorer -> Servers in Farm -> Local Admins
    • Best Practices -> Hardware Requirements -> Free Disk Space
    • Best Practices -> Hardware Requirements -> RAM
    • Best Practices -> Servers -> Hotfixes per Server Role -> all reports
  • To retrieve a list of available Windows updates please make sure that the Windows Update service is up and running. If the service is disabled or not running the following reports will not be available:
    • Farm Explorer -> Servers in Farm -> Available Windows Updates
    • Best Practices -> Updates -> Servers -> Windows Updates

SQL Server Information

Problem

While trying to create a SPDocKit snapshot, I received the following warning:

Loaded Server ‘ServerName’.

Solution

In order to allow SPDocKit to successfully gather all the information about your SQL servers the following permissions are necessary:

  • Sysadmin server role

In case that you can’t give those permissions due to security requirements, there are some alternatives available. More information on how to grant the required permissions is available here.

Problem

While trying to create a SPDocKit snapshot, I received the following warning:

Unable to load database permissions for ‘DatabaseName’.

Solution

In order to allow SPDocKit to successfully gather all the database permissions the following permissions are necessary:

  • db_owner database role on each of the affected databases.

To eliminate this warning you either have to grant the necessary permissions to SPDocKit accounts or turn off the load Database Permissions option.

If you wish to turn off the load Database Permissions option, do the following:

  1. Select Configuration from the left navigation bar on the Backstage Screen and then click the Options button.
  2. On the SPDocKit Options dialog select Snapshot Options.
  3. Under the Security section uncheck Database Permissions.

If you wish to grant the necessary permissions to the SPDocKit accounts, follow this link.

Affected reports

Sysadmin database role is needed to run system extended stored procedures on the Master system database. Without the Sysadmin role, the following reports will not be available:

  • Farm Explorer -> SQL -> Always On reports

The Public server role is needed to fetch the real SQL server name. This permission is necessary to connect to the SQL server and perform some basic T-SQL queries. Also when you add an account to the SQL server, public role is automatically granted. If you are not granted this role, the following reports will not be available:

  • Farm Explorer -> SQL -> SQL Aliases
  • Best Practices -> Databases -> SQL Aliases

Dbcreator role and VIEW SERVER STATE permission is necessary in order to load SQL server configuration data. Following reports will not be available:

  • Farm Explorer -> SQL -> all reports
  • Best Practices -> Databases -> Database Files
  • Best Practices -> Databases -> Max Degree of Parallelism
  • Best Practices -> Databases -> SharePoint Database Autogrowth
  • Best Practices -> Databases -> TempDB -> all reports

Dbaccess permission is necessary in order to load information about the model database. In case this permission is not granted, the following reports will not be available:

  • Best Practices -> Databases -> ModelDB -> ModelDB Files Autogrowth
  • Best Practices -> Databases -> ModelDB -> ModelDB Files Initial Size
  • Best Practices -> Databases -> ModelDB -> ModelDB Recovery Model

Db_owner database role on each of the affected databases is necessary in order to allow SPDocKit to successfully gather all the database permissions. In case this permission is not granted, the following report will not be available:

  • Farm Explorer -> SQL -> Database Permissions

Project Server

Problem

While trying to load Project server site settings with SPDocKit I received:

The HTTP request is unauthorized with client authentication scheme 'Ntlm'. The authentication header received from the server was 'NTLM'.

Solution

In order to allow SPDocKit to successfully gather all the information about your Project server sites the following permissions are necessary:

  • SPDocKit account needs to be a member of the Project Server Administrators group on each of the Project server sites

Take the steps described in the following article to grant the required permissions.

Affected reports

The mentioned permissions on your Project server sites are optional, but depending on them some or all information about your Project server sites configuration reports will not be available in SPDocKit. Without the above-mentioned permissions, the following reports will not be available:

  • Farm Explorer -> Project Server -> all reports

Learn more