If you are unable to connect to your SharePoint site with ShareGate Desktop, there are a few things you can do to troubleshoot the issue:
1. Connect to your site in your browser, using the machine ShareGate Desktop is installed on, and using the same username and password.
Copy/paste the email address you are using from ShareGate Desktop directly into your browser, to ensure that there are no errors.
This step will ensure that:
- There is no networking issue preventing you from connecting.
- The address you provided is the right one.
- The username and password grant access to the site.
If you cannot connect with your browser, please contact your SharePoint or network administrator.
2. Verify your Alternate Access Mappings configuration.
In order for ShareGate Desktop to connect to your site, the address that you use within ShareGate Desktop must be listed in your Alternate Access Mappings configuration. This article will help you set this up correctly.
3. Using Multi-Factor Authentication? Create an app password.
Create an app password for Office 365 and use Other User on ShareGate Desktop to sign in, using these credentials.
Since there are several apps (including ShareGate Desktop) that don't support the use of phones to secure your account, an app password is needed. This is easy to create, and can be then be used as your primary authentication method to connect to your environment on ShareGate Desktop.
Note: The app password will not work if you're running operations on Office 365 Groups.
4. App password did not do the trick for Multi-Factor Authentication? Try renaming the userdata file.
Popular MFA providers like OKTA use a token to authenticate, and the token usually changes if you change credentials. So even if you are entering the correct information to sign in, the old token will still cause problems since it is stored in the userdata folder.
5. Connect to your site with SharePoint Designer.
ShareGate Desktop connects to SharePoint in a way that is very similar to SharePoint Designer, since both are client-side applications (as opposed to server-side).
If you cannot connect with SharePoint Designer, there is likely a configuration issue with the SharePoint server.
Here are a few things to verify:
- Client Integration is enabled.
- Web application configuration is correct.
- IIS configuration is correct.
6. Try all the authentication modes in ShareGate Desktop.
Depending on the way your SharePoint server is configured, it is possible that the default authentication mode in ShareGate Desktop will not work with your site. We recommend trying either Browser, Windows, or Manual.
For more information on this, please click here.
7. Reset IIS on the SharePoint server.
IIS (Internet Information Server) can sometimes get into a corrupted state and prevent connection to SharePoint. Running the "iisreset" command on your server will fix this situation.
Note: This solution will make the SharePoint server unresponsive for up to several minutes, so we recommend executing this outside of business hours if possible.
Things that can interfere with the connection process:
- Incorrectly configured filtering software (such as WebSense).
- If possible, disable the filtering software and attempt to connect again.
- Incorrectly configured reverse proxy site.
- If possible, try to connect directly to your SharePoint WFE without going through the reverse proxy or load balancer.
If these steps do not help you resolve your connection issue, please contact our team who will be happy to help.
8. Ensure the your SharePoint Tenant contains a root site collection.
It is possible that the absence of a root site collection in your environment is causing authentication errors, since ShareGate Desktop needs information from the root site collection to authenticate the user.