Troubleshooting SharePoint connectivity
This article contains information on all known connectivity problems related to SharePoint servers (both SharePoint Online and its on-premises version) as well as possible solutions.
- Problems with configuring a connection to SharePoint Online
- Problems with configuring a connection to on-premises SharePoint server
- Other known SharePoint connectivity problems
When configuring a connection to SharePoint Online, in the last step of the SharePoint Server connection wizard the program tries to enumerate SharePoint site collections and connect to one of them. If the program fails to perform any of these actions, it will display failure notifications, as shown in Fig. 1. below:
The examples below show the most common error messages:
Failed to connect to SharePoint using account '<admin_account>'. Make sure that you have entered the account credentials and server URLs correctly.
In case you get this message, double-check the details entered in the Server address and Admin's credentials steps of the connection wizard and try again. If multi-factor authentication is enabled for the provided admin account, make sure to use the app password instead of the regular Office 365 account password. Make also sure that the admin account is assigned specific roles allowing access to SharePoint content (Keep in mind that the propagation of admin rights in Office 365 usually takes some time). Finally, check your internet connection.
It is also possible that the support for non-modern (legacy) authentication protocols is disabled in your tenant. Enabling it may also solve the problem. Read more below
Exception: For security reasons DTD is prohibited in this XML document.
This problem is most likely caused by the DNS assistance service (also known as DNS hijacking or DNS redirection) used by your Internet Service Provider (ISP). Suggestions on how to troubleshoot this problem can be found in this Knowledge Base article.
When configuring a connection to the on-premises SharePoint server, in the last step of the SharePoint Server connection wizard the program tries to enumerate site collections with PowerShell and connect to any SharePoint site collections and Admin service. If the program fails to perform any of these actions, it will display failure notifications, as shown in Fig. 2. below:
The examples below show the most common error messages:
Failed to connect to SharePoint using account '<admin_account>'. Make sure you have entered the account credentials and server URLs correctly.
In case you get this message, double-check the details entered in the Server address and Admin's credentials steps of the connection wizard and try again. Make also sure that the admin account has all the necessary roles and permissions assigned. Finally, check your internet connection.
Failed to connect to Central Administration service. Make sure that you have entered its URL correctly.
Go back to the Server address step of the wizard and check if the URL address entered in the Central Administration URL field is correct. Keep in mind that it is filled automatically based on the entered SharePoint Server URL; however, you need to provide the port number manually.
Below are some of the most common error that may appear when configuring various jobs in CodeTwo Backup.
The term 'Get-UnifiedGroup' is not recognized as the name of a cmdlet, function, script file, or operable program.
You may get this error while configuring a SharePoint backup job and trying to list team sites. Try to reconfigure your connection to SharePoint Online. Make also sure that the admin account used to connect to your SharePoint server is assigned at least the SharePoint administrator role (learn more).
Keep in mind that the propagation of admin rights in Office 365 usually takes some time. The attempt to list SharePoint sites immediately after assigning the appropriate role may fail (you’ll get the same error message). Try configuring a backup job later.
Cannot contact web site '<site URL>' or the web site does not support SharePoint Online credentials.
You may receive this error in the SharePoint restore job wizard while attempting to create a new site collection or map users, groups, or permission levels. This happens when the use of non-modern (legacy) authentication protocols in disabled in your SharePoint Online environment. When disabled, the -Credential parameter used by CodeTwo Backup to connect to SharePoint Online via PowerShell is blocked. To fix this, you need to enable the support for non-modern authentication protocols either by using:
It may take up to 24 hours for changes to take effect.
- Open the SharePoint Online Management Shell command prompt.
- Connect to your SharePoint Online by using the following command:
Connect-SPOService -Url https://<organization>-admin.sharepoint.comwhere <organization> is the organization (tenant) name set in Office 365.
- Run the following cmdlet:
Set-SPOsite -LegacyAuthProtocolsEnabled $True
- Log in to Office 365 and click Admin to open Microsoft 365 admin center (Office 365 admin center).
- In the left pane, expand Admin centers and click SharePoint (Fig. 2.).
- In the SharePoint admin center, click access control from the menu on the left, and under Apps that don't use modern authentication settings select Allow (Fig. 3.).
- Click OK to save changes.
Failed to list <SharePoint object> from the target server. Make sure that you properly defined the SharePoint connection and that the administrator's account used in the connection has sufficient access rights.
The <SharePoint object> may refer to site collections, team sites, or OneDrive sites. This error usually appears when listing SharePoint objects in the backup or restore jobs. Try reconfiguring the connection to your SharePoint server.
Double-check also if the admin account used to establish the connection to your SharePoint server has all the necessary roles and permissions assigned.
Access denied. You do not have permission to perform this action or access this resource.
This error may occur while restoring SharePoint lists to SharePoint Online. To fix this problem, you need to allow custom script in your SharePoint Online tenant. Find out how to do so here.