Hi @Bhaskar_D.
It is usually related to three main factors: credentials, gateway configuration, or data source accessibility.
1. Verify the Authentication Type
- For SharePoint On-Premises, the gateway supports Windows Authentication (Kerberos/NTLM).
- Ensure that:
- You are using domain credentials (e.g., DOMAIN\username).
- The account has read permissions on the SharePoint library or list.
- If using HTTPS, confirm that the certificate is trusted.
2. Test Connectivity from the Gateway Server
- On the server where the On-Premises Data Gateway is installed:
- Open a browser and attempt to access the SharePoint site using the same credentials.
- If additional authentication is required (e.g., NTLM combined with MFA), this may cause the failure.
- You can also run:
Test-NetConnection <SHAREPOINT_URL> -Port 443
to confirm that there are no network blocks.
3. Adjust Timeout
- The error mentions a timeout, which can occur if the list or library is very large.
- In Power BI Service, you cannot directly increase the timeout, but you can:
- Reduce the data volume (apply filters in Power Query).
- Ensure the Gateway is updated to the latest version.
4. Check Gateway Configuration
- In Power BI Service:
- Navigate to Settings > Gateways > Connections.
- Confirm that the Gateway is online and that the connection is assigned to the dataset.
- If using Kerberos Constrained Delegation, verify that it is correctly configured in Active Directory.
Official Documentation for Reference
Practical Suggestion:
Start by testing with a dedicated service account (without MFA) and confirm that the Gateway can authenticate directly to SharePoint. If this works, the issue is likely related to credentials or advanced authentication.
If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.
Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.
