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.
Hi - hoping someone can help!
I've installed the standard on-premises data gateway on my PC and have created a gateway cluster called "WD Gateway." To create redundancy, I asked a few of my coworkers to install the on-premises gateway on their PCs. They are able to install, but when they select the option in the configuration to "Add to an existing gateway cluster", no options are listed. I've shared the gateway cluster with these users and they can see it listed in the 'Manage connections and gateways' section of the online service, but not in their on-premises gateway configuration.
Does anyone know why the gateway cluster isn't showing up, and how to resolve? Appreciate the help!!
Solved! Go to Solution.
Hi, @pitachip33
Thanks for the reply from @sergej_og , please allow me to provide addition:
First, it's important to make sure that all members involved in the gateway cluster have the same version of the on-premises data gateway installed. A gateway version mismatch can cause visibility issues.
Second, the issue may be related to permissions. Even if you've shared a gateway cluster with colleagues, make sure they've been added as administrators for the gateway. This step is critical for them to review and add to an existing gateway cluster.
Finally, if the above steps are done sequentially, but the problem persists, it could be a network-related issue. Ensure that there are no firewalls or network policies preventing gateways from communicating with each other or with the Power BI service.
How to Get Your Question Answered Quickly
Best Regards
Yongkang Hua
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, @pitachip33
Thanks for the reply from @sergej_og , please allow me to provide addition:
First, it's important to make sure that all members involved in the gateway cluster have the same version of the on-premises data gateway installed. A gateway version mismatch can cause visibility issues.
Second, the issue may be related to permissions. Even if you've shared a gateway cluster with colleagues, make sure they've been added as administrators for the gateway. This step is critical for them to review and add to an existing gateway cluster.
Finally, if the above steps are done sequentially, but the problem persists, it could be a network-related issue. Ensure that there are no firewalls or network policies preventing gateways from communicating with each other or with the Power BI service.
How to Get Your Question Answered Quickly
Best Regards
Yongkang Hua
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you @Anonymous ! The issue was I needed to add my coworkers as admins to the gateway cluster.
Hey @pitachip33 ,
I think your coworker should have the permission to install/regsister a gateway into your tenant.
You can set this permission in your tenant settings.
Sharing a gateway means they can use this gateway for adding new conncetions etc.
Have you set this setting?
Regards
User | Count |
---|---|
43 | |
16 | |
12 | |
11 | |
9 |
User | Count |
---|---|
50 | |
31 | |
22 | |
17 | |
15 |