Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago

Power BI Service: Data Gateway: Connection Error: Unable to connect to data source {0}

Hello All,

I'm a new to Power BI and learning through the courses available with Udemy. I was trying to create a dataflow in Power BI Service. For the same I have downloaded and configured On Premise Data Gateway.
However when I'm creating a dataflow and trying to connect to the CSV file at my local machine, it gives below error:


An exception occurred: Access to the path 'C:\Users\James\Test123.csv' is denied. (Session ID: 82f13b8e-d2bd-4cb4-8dbd-8ee1f21eb7b9)

 

Also checked Settings > Manage Gateway, there I found below Error Details - 

 

 

Tried all below Options:

1. ReInstalling the Gateway wih updated and latest version (Gateway is already UP and Running)

2. Changing Privacy Level for data sources of gateways to all the 3 options (Public, Private and Organizational)

3. Checked all the local files. They all have full control to all the users.

 

Please let me know what step I'm missing out.

4 Replies

  • Please provide more details - is this a personal gateway or an enterprise/standard gateway?  Generally you don't want to put data sources on your PC because a standard gateway doesn't know how to get to these files (especially when your PC is switched off 🙂  )

    • Anonymous's avatar
      Anonymous
      Not applicable

      Its a standard gateway. Yes, I agree to that, but this is for practice purpose. Once I get it I know that it would be some DB on some on-prem/cloud server.

      • lbendlin's avatar
        lbendlin
        Icon for Super User rankSuper User

        These data sources are not comparable. Test it with "some DB on some on-prem/cloud server." . Note that "some" cloud servers do not require gateways if they are visible to the Azure service.

  • nitishsh91's avatar
    nitishsh91
    Icon for Solution Supplier rankSolution Supplier

    Hi Anonymous 

     

    Instead of using C drive local path, try to use a network path with an account which has got access on path too otherwise just try using on-premises database/api directly.