Add Sharepoint List Data Source to Gateway

[Anonymous]

Hello, my team has a gateway setup that refreshes a variety of datasources (mostly sql serverbased). I've added more than a few data sources by specifying the server, database, entering credentials and so on. The problem I have now is when I attempt to enter a sharepoint list as a new source, I'm receiving a credential error (see below). 

I've reviewed what I could between these asks, but they don't seem quite relevant:

https://community.powerbi.com/t5/Service/PowerBI-linked-to-SharePoint-Lists-require-a-Personal-Gatew...

https://community.powerbi.com/t5/Desktop/SharePoint-List-Access-to-resource-is-forbidden/m-p/51475#M...

https://community.powerbi.com/t5/Integrations-with-Files-and/SharePoint-Online-List-Data-Source-Conn...

https://community.powerbi.com/t5/Desktop/When-connecting-to-a-Sharepoint-Online-List-some-columns-ar...

https://community.powerbi.com/t5/Desktop/Connecting-to-a-SharePoint-List-Office-365-error/m-p/10075#...

My end goal is to have the sharepoint site accesible by our gateway(which lives on our server) so that we don't have to have our personal credentials needed when the scheduled refresh kicks off. Right now, the report owner is using her personal credential set for the sharepoint site and the gateway credentials for the other sources (all sql). 

While creating the source, I'm using -

Type: Sharepoint, Sharepoint URL: ....., Authentication Method: Windows, Username/Password have been validated to have ownership level access, Privacy Level: Organizational.

Here's the error:

Unable to connect: We encountered an error while trying to connect to . Details: "We could not register this data source for any gateway instances within this cluster. Please find more details below about specific errors for each gateway instance."Hide details

Activity ID:	c77c08e7-ea48-345a-fd92-5e8e73bee28d
Request ID:	f06b03c2-1137-f157-dc9a-bdfa7c987836
Cluster URI:	https://df-msit-scus-redirect.analysis.windows.net
Status code:	400
Error Code:	DMTS_PublishDatasourceToClusterErrorCode
Time:	Mon Jul 09 2018 15:57:17 GMT-0700 (Pacific Daylight Time)
Version:	13.0.5933.146

IFM Azure:	Invalid connection credentials.
Underlying error code:	-2147467259
Underlying error message:	The credentials provided for the SharePoint source are invalid. (Source at https://microsoft.sharepoint.com/teams/IFMWEB/Lists/hierarchy/Building%20List.aspx.)
DM_ErrorDetailNameCode_UnderlyingHResult:	-2147467259
Microsoft.Data.Mashup.CredentialError.DataSourceKind:	SharePoint
Microsoft.Data.Mashup.CredentialError.DataSourcePath:	https://microsoft.sharepoint.com/teams/IFMWEB/Lists/hierarchy/Building%20List.aspx
Microsoft.Data.Mashup.CredentialError.Reason:	AccessForbidden
Microsoft.Data.Mashup.MashupSecurityException.DataSources:	[{"kind":"SharePoint","path":"https://microsoft.sharepoint.com/teams/IFMWEB/Lists/hierarchy/Building%20List.aspx"}]
Microsoft.Data.Mashup.MashupSecurityException.Reason:	AccessForbidden

[Anonymous]

Has this issue been resolved? I am experiencing the exact same problem.

I was able to add a "Sharepoint List" as a datasource on the Power Bi desktop application but there is no option for a "Sharepoint List" when setting up the gateway datasource settings. I only see a "Sharepoint" datasource and when trying to add this I receive the same error @Anonymous received.

[Anonymous]

Update: 

The issue it appears that I've ran into is actually that the service seems to limit the number of servers a report can use a single gateway for if you're not an admin over the gateway. 

Regular users can only select the gateway if they have one sql server in the data sources. 

It sounds like this is not intended behavior and may be fixed in an update but I have no ETA based on talking with support. 

[WesL]

This randomly happens to us and we can't figure out why.  

[Anonymous]

It seems like it may not be possible unless you have the premium version. We're using the lower tier. 

[WesL]

We are PRO and have been using it for over a year but got hit with the same random error.  Just found out our issue appears to be part of a widespread issue that MSFT is aware of.