Dataflow Gateway Connection Issue

[Mat42]

Our Power BI system has been going haywire for the past few weeks, and I honestly don't understand what's happening.

I have a member of staff who is working with a dataflow (that they created) and is having problems refreshing it. The database has a gateway connection set up, which is live and working.

They created the dataflow perfectly fine, but when it came to refreshing it, PBI dropped this error:

All well and good, there's obviously an error somewhere.

However, nothing we do is fixing the issue. As mentioned above, gateway connection is up and running. If I (as a PBI admin) connect to the dataflow, it refreshes fine (both manually and automatically), but it does not work for this staff member. I've run through every 'fix' I can think of: refreshing credentials, removing and relinking the data source, ensuring that the database is up, running, and accessible and that this staff member has access, ensuring that this staff member has access to use the gateway connection etc. Nothing is working.

Also, bizarrely, when I sent them the steps to unlink/relink the data source to see if that worked, the error they received is this:

But, we aren't creating a gateway connection, we're using one that already exists and that this staff member has access to!! I've never come across this error before. Why would it acvt as though a new connection is being created? The connection name is pre-populated in the 'Edit Connection' window, I can see it in their screenshot.

Can anyone give me any idea of what's happening? As a final note, we're not connecting via OAuth2, but using the 'Basic' 'Authentication kind' with a username and password specifically for the database. When I say that it works for me, I mean that it works for me using those credentials, and the staff member is also using those credentials.

[v-venuppu]

Hi @Mat42 ,

I hope this information is helpful.If this answers your question, please accept it as a solution,so other community members with similar problems can find a solution faster.

Thank you.

[v-venuppu]

Hi @Mat42 ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-venuppu]

Hi @Mat42 ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @collinq for the prompt response.

I want to check if you had the opportunity to review the information provided and resolve the issue.If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[collinq · Accepted solution]

HI @Mat42 ,

In reading your explanation it appears that you done pretty much everything I would recommend.  Since you are using the same credentials I am thinking that is at the user level of the PC / browser / location / firewall involved.  Since the error kind of changes I would suggest doing a network trace.  Something like Fiddler.  We can asume that it is not the gateway or connection to the data source as that would either work for everybody or nobody.  And, since the same credentials work for one person they should work for another.

The test would be for the user to turn on the tracking in Fiddler, try to get the data and then see where the block occurred.  That should point you to the culprit.

My thinking is that where the user is located and/or some setting on their machine is what is keeping just them from getting to the data.