Issues with On-premise Gateway - Received error payload from gateway service with ID 328575

You may find that the issue here is to do with you having a later version of the data gateway app once you've gone back to install it again with a service account. Recent versions changed how the gateway service handles SQL connections in particular, requiring them to be defined as "trusted" prior to allowing them to be used.

On the server with the gateway installed, browse to C:\Program Files\On-premises data gateway and find the appropriate gateway config file, which will be Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config in your case. Make a backup of the file before you change anything.

Edit the file in a notepad window run as administrator, or use Notepad++ or equivalent, and find the entry in the XML with the tag SqlTrustedServers, which by default will look like this:

      <setting name="SqlTrustedServers" serializeAs="String">
        <value />
      </setting>

and amend it to include the values of your server hostnames, like this:

      <setting name="SqlTrustedServers" serializeAs="String">
        <value>SQLserver.domain.com,SQLcluster*.domain.local</value>
      </setting>

You can see that you can specify a comma separated list with the hostnames of your servers as used in the gateway config in MS Fabric or PowerBI connections, and can also use wildcards to reflect some or all of the hostname.

You could even trust all SQL connections through the agent like this:

      <setting name="SqlTrustedServers" serializeAs="String">
        <value>*</value>
      </setting>

but I'd not recommend it if you can avoid it, you introduce a range of risks and attack vectors.

Restart the gateway service on the machine it runs on, which is called On-premises data gateway service and then refresh the status in Fabric and if this was your cause, you should see them immediately come online.

Hi  Phoenix529,
Thank you for reaching out to the Microsoft Fabric Forum Community.

From your description, it appears that although you're On-Premises Data Gateway is online, the specific connections using the gateway are displaying as offline, even though data refreshes are successful. 

• Go to Manage Gateways in Power BI Service, select SQL_SERVER, and ensure all data sources are mapped to the new service account with updated credentials. Incorrect mappings may cause connection issues even if the gateway appears online. 
• If the issue continues, reinstall the On-Premises Data Gateway using the service account to ensure correct registration and permissions. After reinstalling, reconfigure the data sources and test the connection. 

Please refer to the solved links for more details: 

Solved: Received error payload from gateway - Microsoft Fabric Community 

Solved: Received error payload from gateway service with I... - Microsoft Fabric Community 

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you.

We have been facing the similar issues with payload errors. We also added the SQL servers names into Gateway config file as per the recent recommendation by MSFT. **Issues seems to specific while configuring the connection with Windows Authentication, however with SQL/Basic login the connections are able to show online. Not sure this might be involve some OS level support to ensure to no issues with Window Authentication from the gateway server. We are using 2016 Windows Server OS. still wating for the concrete resolution form Microsoft. 

Hi Phoenix529,

Could you please confirm if the issue was resolved after raising a support case? If so, we’d appreciate it if you could share the solution to help others in the community. As we haven’t heard back, we’re closing this thread. For any further issues, please raise a new thread in the Microsoft Fabric Community Forum — we’ll be happy to assist.

Thank you for being part of the Microsoft Fabric Community.