Forum Discussion
Advocate IIIAdding the file path to the gateway cluster!
Advocate IIIHi Anonymous,
yes you were right and I fixed that thing, yet no luck. I changed the source (even though I was on the local machine) to the detailed path and it worked inside the PBID and then published. The connection is fine through the personal gateway, however if I wanted to add the path to the enterprise gateway, there the problem arises.
As you can see below the connection is going good with the personal one.
Then I tried to add that path to enterprise.
File path is correct this time.
I tested that path by browsing from the server and it asked for my local credential and then the file got opened.
I can't figure out why this is popping up no matter what method I use.
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: | e8c466f8-becf-47e3-bd32-7ec0191515b1 |
| Request ID: | 518ba00b-914b-6ae0-f1b7-2b42afd5bdbb |
| Cluster URI: | https://wabi-us-east2-redirect.analysis.windows.net |
| Status code: | 400 |
| Error Code: | DMTS_PublishDatasourceToClusterErrorCode |
| Time: | Fri Aug 03 2018 10:50:57 GMT-0400 (Eastern Daylight Time) |
| Version: | 13.0.6109.175 |
| SAE-PBDevelopment: | Invalid connection credentials. |
| Underlying error code: | -2147467259 |
| Underlying error message: | The credentials provided for the File source are invalid. (Source at \\netapp2.company.local\home$\user\workhours.xlsx.) |
| DM_ErrorDetailNameCode_UnderlyingHResult: | -2147467259 |
| Microsoft.Data.Mashup.CredentialError.DataSourceKind: | File |
| Microsoft.Data.Mashup.CredentialError.DataSourcePath: | \\netapp2.company.local\home$\user\workhours.xlsx |
| Microsoft.Data.Mashup.CredentialError.Reason: | AccessUnauthorized |
| Microsoft.Data.Mashup.MashupSecurityException.DataSources: | [{"kind":"File","path":"\\\\netapp2.company.local\\home$\\user\\workhours.xlsx"}] |
| Microsoft.Data.Mashup.MashupSecurityException.Reason: | AccessUnauthorized |
Hello,
I Just got success after getting the same error and hope this helps. Please note I use a mapped drive to access my data so it may be slighllty different but worth a shot. There were two problems:
1. The username and password I was usuing. For me, I needed to use the credentials used to get on to the server I was using as those are the windows credentials that server uses. Originally I was trying to use my actual windows log in and getting frustrated.
2. You have to use your UNC (universal naming convention) as your file path, not the drive name AND it has to be the same on your actual power BI desktop file before you can connect it via the online power BI service.
Here is how you get your UTC :
Go to search in bottom left of desktop, type "run" and hit enter
type "cmd" hit enter
type "net use" hit enter
you will get \\and anything after those charaters is you UTC
Once you have your UTC:
Open your actual power Bi desktop file - go to file, options and settings, data source settings.
Click on each local file and replace the drive portion of your file path with your UTC.
Make sure to refresh and then save and publish your power bi file.
After it publishes you can log back on to the power BI service and go to your scheduled refesh. Under the gatway you will see the connections included in the data set. Now you can add each one to the gatway cluster just make sure you use the corrected username and password.