The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have a Report which used local Files in an network connection via Gateway on a server. Worked fine.
Now we moved the Server into a DMZ and i get credential errors in Power BI Service.
The old Gatewayconnection Credentials give the Error:
DM_GWPipeline_Gateway_MashupDataAccessError
When I try to add new Connection to Gateway i get:
IT Operation Gateway: The credentials provided for the File source are invalid or IT Operations Gateway: The user name or password is incorrect
Which credentials do i have to use, credentials from Server in DEZ, Credentials from the network connection?
Refreshing with Power BI Desktop on DMZ Server and publish to Service works.
Solved! Go to Solution.
Hi , @LuITS
According to you description, you need to give different/additional credentials to enter network envirement on the "DMZ" compter.
I think this may be the cause of the problem, for the cloud to connect to your data source, you need an on-premises data gateway to communicate with the data source, but you need to make sure that the network environment where the data gateway is installed can access the network environment of your data source.
For example, if your computer needs to have a VPN enabled to access the target network, then you need to always have your VPN turned on to ensure network connectivity, and there is currently no place in the gateway to provide credentials to access the network.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hi , @LuITS
According to your description, you change the server environment and then the Gatewayconnection Credentials give the Error.
For this , you need to check this:
(1)You need to make sure that your gateway is installed in the correct location, and do you need to install the gateway on a computer that can connect to your existing data source network environment .
(2)When you publish to a service, for example, if you connect to a local data file, the credentials you enter require credentials that can access the data source on the computer where the gateway is located.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Thanks for your answer.
To (1)
First part: is given because i can refresh local data (for example data located on desktop) on the "DMZ" computer
Second part: I can access the data source network enviroment with "DMZ" computer while i create my reports in Power BI desktop on the "DMZ" computer. But i had to give different/additional credentials to enter network envirement first (I guess these credentials give the error?)
Thanks for your time
Hi , @LuITS
According to you description, you need to give different/additional credentials to enter network envirement on the "DMZ" compter.
I think this may be the cause of the problem, for the cloud to connect to your data source, you need an on-premises data gateway to communicate with the data source, but you need to make sure that the network environment where the data gateway is installed can access the network environment of your data source.
For example, if your computer needs to have a VPN enabled to access the target network, then you need to always have your VPN turned on to ensure network connectivity, and there is currently no place in the gateway to provide credentials to access the network.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly