Forum Discussion
Unable to Set-DataGatewayInstaller with PrincipalObjectIds from app
Hi robzib ,
Please check:
- If your gateway has been updated to the lasted version or there are Inconsistent versions between gateway members in a cluster. Many issues can surface when the gateway version is out of date.
- To test if the gateway has access to all the required ports, run the network ports test.
- You might encounter installation failures if the antivirus software on the installation machine is out of date.
- You might encounter installation failure when anitivirus software, like McAfee Endpoint Defender, is enabled. Configure your antivirus software to ignore the gateway process.
For more details, please refer to:
Troubleshoot the on-premises data gateway | Microsoft Learn
Best Regards,
Jianbo Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you for your suggestion, but my issue is not with gateway install. I've spent some time today to go through my implementation that used to work, and I managed to pinpoint the issue. It turns out that It's no longer possible to PostDatasetUser with type App and use service principal identifier. If you go to bind-to-gateway-in-group documentation there is an info block stating "Add the API caller principal as a data source user on the gateway." but when I try to do that I get an error. If you go to post-dataset-user documentation, under limitation it's stated that "Adding permissions to service principals (app principalType) isn't supported".
Not sure what to do because I can't call BindToGateway without adding my principal as user. This used to work because I have Azure tenant used for proof of concept and code that no longer works on another tenant.