Enterprise mode gateway: the parameter is incorrect

[marcosh]

Hello,

I'm in the process of replacing a personal mode gateway for an enterprise mode gateway, but I keep running into the same error: The parameter is incorrect, status code 400. I've restarted my enterprise mode gateway and made sure that it's running with the latest updates (January 2025) I've also tried to connnect to multiple SQL servers with different authentication methods but my issue persists... I've also checked the status of my enterprise mode gateway and is online and should ready to go, is just when I try to add a new connection to this gateway it keeps failing. I've also verified my credentials for these databases, I don't know what else I could be missing, maybe I should start looking configurations files at this point as I'm running out of ideas...

Any help is appreciated,

[v-mdharahman]

Hi @marcosh,

Thanks for reaching out to the Microsoft fabric community forum.

It looks like you are facing issues with your gateway where you want to replace your personal gateway with an enterprise mode gateway. As you mentioned you have already done couple of troubleshooting steps but still faces the same issue. I would like to suggest few more things to verify. 

*Make sure that the enterprise gateway has proper network access to the SQL servers.

*You can also check the gateway logs for more detailed error messages for better understanding of the problem.

*Lastly try to clear your PowerBi cache data and redo your steps.

Coming to the Signature Mismatch issue, you can check authentication settings. Try switching between Windows Authentication and Basic Authentication to see if the error persists. Clear the gateway cache and restart the gateway service. If the issue still persists then check the Gateway Log and look for timestamps that match your connection attempts to see what exactly is failing.

I would also take a moment to thank @GilbertQ, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

[marcosh]

Hi @v-mdharahman ,

I ended up deleting that gateway and creating a new one that worked just fine since the beggining. I suspect that the issue arrised from the monthly updates from Microsoft on gateways, towards the end of January I stop getting refreshes in my semantic models, have anyone every encounter an issue like such?

I'd like to get to the root of the problem to find a concrete solution so that I don't have to be deleting my gateways and creating new ones every month.

Thanks to @GilbertQ as well, for the future responses I'd suggest not to formulate answers as a question, it can confuse the user even more.

Thanks again,

Marcos

[v-mdharahman · Accepted solution]

Hi @marcosh,

If the issue started after a Microsoft update, it's possible that something in the gateway’s internal configurations got corrupted or became incompatible with your setup. Others have also faced issues after gateway updates, like there have been cases where updates caused authentication failures, SSL/TLS mismatches, or even refresh failures in Power BI. 

The things you can do to find a concrete solution of the root cause is like you can monitor Gateway logs before and after their updates to get a better understanding of what and where things are going wrong. You can also check PowerBI Service refresh history for error messages and PowerBI Gateway logs for authentication or connection failures.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

[marcosh]

Part of the problem is that I'm not quite sure what parameters is refering to, is that the authentication method or the privacy level? Are you suggesting to use the default parameters for those options? Could you clarify that a little bit more. I can sign into the gateway and view the detailed logs, but that hasn't been very useful either, there's a signature missmatch which seems to be along the lines of the issue but again I'm not sure how can I edit these parameters.

Thank you for the response,

[GilbertQ]

Hi @marcosh 

What happens if you had to create a new sql server gateway connection without a parameter where it's just using the default values to your sql server? Also, if you can log into the gateway server, open up sql server management studio and see if you can connect from the gateway server to the sql server.

[marcosh]

@GilbertQ Could you clarify please!