Forum Discussion
Certificate Chain Not Trusted Error affecting PBI only, can't switch credentials to Windows.
Hi, I'm getting the following error when connecting to a SQL server running on an Azure VM. Microsoft SQL: A connection was successfully established with the server, but then an error occurred du...
I have encountered the same issue. There are two solutions (workarounds)
1) Roll-back to Dec 2023 (Micrsoft support has confirmed this to me)
2) I was able to bypass the error by inserting a space before the port# in connection string (connecting to SQL):
old connection: SV944007\CR1001,27692
modified conneciton: SV944007\CR1001, 27692
Note - if you have an alreay published old connection string, it wont be recognized in the Gateway. You have to create a new gateway connection with the modified connection string.
please try this and confirm if this works