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!!!
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.
Hi Petebro
Thank you for this workaround but it means for my organization (we use PBIRS on-premise) that we have to change the “PBI_SQL_TRUSTED_SERVERS” environment variable and reboot the server everytime a new SQL Server is used as a DirectQuery data source of a Power BI Report.
Could you tell me if there is a wildcard value (e.g "*") for this environment variable that means that all the SQLServers are trusted?
Thanx in advance for your answer.
Have an amazing day!