Forum Discussion
Issues regarding power bi report server
Apologies for this change not being mentioned....I forgot to add this to the changelog and release notes (and will be fixing that today).
The May release has a expected change on the AS side of things which will require customer actions to keep some existing scenarios working. As part of a push for security customers will have to explictly include “Encrypt=True;TrustServerCertificate=True” as part of the connection string or apply the “PBI_SQL_TRUSTED_SERVERS” environment variable to their server to Power BI Report Server machine.
Good afternoon,
To make this workaround to be effective it has to be:
setx PBI_SQL_TRUSTED_SERVERS [DDBB Server Name]
It is not enough to introduce the variable, but also include the server name.
Now it works fine!!!
I'll confirm the details and update the respected docs but I think any value works (the presense of the environment var is all that it cares about). Running the command from a cmd prompt with admin rights will work:
setx PBI_SQL_TRUSTED_SERVERS 1
I've solved using a tips from medium.com .
My connection string use:
serverName\Instance,1234
I've used the "*" as a jolly to trust every server... it's not a beatiful idea, especially for safety, but it works .... (for the moment)
So the setup was:
setx PBI_SQL_TRUSTED_SERVERS * /M