On-premises data gateway does not work on Windows Server 2022

[MThornicroft]

I'm having an issue with running the 'HTTP with Microsoft Entra ID (preauthorized)' connector. The on-premises data gateway is set up and running on a Windows Server 2022. We have an on-premises data gateway is on a Windows Server 2019 that works perfectly fine on a different VM, but this one doesn't seem to work.

When I run my flow, as soon as it gets to the connector with a basic GET command, I receive the following error:

Action 'User_Login' failed: { "error": { "code": 500, "source": "uk-001.azure-apim.net", "clientRequestId": "xxx", "message": "BadGateway", "innerError": { "status": 500, "message": "Received error payload from gateway service with ID 250860: Internal error: userName.\r\nclientRequestId: xxx", "error": { "message": "Received error payload from gateway service with ID 250860: Internal error: userName." }, "source": "gatewayconnector-ukw.azconn-ukw-001.p.azurewebsites.net" } } }

The error logs from the GatewayErrors.log file show the following:

DM.EnterpriseGateway Error: 0 : 2024-09-20T14:46:03.7854822Z DM.EnterpriseGateway e2c65b3d-cd36-474c-b31c-76874e8ad108 00000000-0000-0000-0000-000000000000 MDSR 00000000-0000-0000-0000-000000000000 94b98e5c-7c83-4256-9197-7ab195efe5fe 83cdf9a7-620b-4088-916a-a47d3970d9c9 4C1EF73E [DM.GatewayCore] Error processing request: [0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.RuntimeCheckFailedException: Internal error: userName
TemplateMessage: A runtime check error occurred:

GatewayPipelineErrorCode=DM_GWPipeline_Gateway_RuntimeCheckFailedError
GatewayVersion=
FailureMessage=
([0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.RuntimeCheckFailedException.StackTrace:)
at Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.Internal.RuntimeChecks.Fail(String message)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.ImpersonatorHelper.ParseUserName(String userName, String& domain, String& user)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayHttpWebProcessor.GetCredentialCache(String credential, IGatewayConfigurationStore configurationStore, Uri uri)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayHttpWebProcessor.AddProperties(Dictionary`2 properties, HttpClient httpclient, HttpClientHandler httpClientHandler, HttpRequestMessage httpRequest, GatewaySerializationContext responseContext)

Any ideas?

Thanks,
Matt

[sreetejreddy]

Is the gateway installed on a domain-connected server to enable Windows Authentication modes.

[Anonymous]

HI @MThornicroft 

There are some limitations and requirements for installing gateway, you can check if your environment is capable of installing standard gateway according to the documentation.

https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-install#requirements 

Best Regards,
Community Support Team _ Ailsa Tao

[MThornicroft]

@sreetejreddy Yes, we have installed it on an Azure VM which is connected to the same domain as the server that works.

[MThornicroft]

@Anonymous We had initially checked this prior to installation. Due to WS2019 leaving mainstream support in Jan 2024, we decided to use WS2022. The requirements state WS2019 as a minimum, not maximum. All other requirements have been followed and adhered to. Our VMs running the gateways are essentially identical apart from the difference in server OS.

[Anonymous]

Hi @MThornicroft 

Have you checked that the VM where Windows Server 2022 is installed is domain controller? If so, you need to change it to domain member or reapply for a domain member VM. because domain controller doesn't support installing gateway.

Best Regards,
Community Support Team _ Ailsa Tao

[MThornicroft]

Hi @Anonymous,

I figured out the issue just before you posted. The connection in Power Automate wasn't storing the credentials after it had been edited, therefore as soon as I added in the username and password for 'Windows' credentials it started working. This post can now be closed.

Thanks,
Matt