<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: MAJ version PBIRS JAN 2025 to MAY 2025 in Report Server</title>
    <link>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4804402#M41720</link>
    <description>&lt;P&gt;After upgrading PBIRS from Jan 2025 to May 2025, encrypted connection strings in Power BI reports may break publishing and scheduling. RDL reports are unaffected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How to Fix:&lt;/P&gt;&lt;P&gt;Set this environment variable on the server:&lt;BR /&gt;PBIRS_EnableLegacyConnectionStringHandling = True&lt;BR /&gt;Then restart the PBIRS service.&lt;/P&gt;</description>
    <pubDate>Fri, 22 Aug 2025 03:56:38 GMT</pubDate>
    <dc:creator>Shahid12523</dc:creator>
    <dc:date>2025-08-22T03:56:38Z</dc:date>
    <item>
      <title>MAJ version PBIRS JAN 2025 to MAY 2025</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4803538#M41711</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;after migrate PBIRS version Jan 2025 to May 2025, i have an issue on the connection strings of PBI reports (encrypted caracters) and i can't publish new PBI reports with connection string and schedule. I precise the issue don't happen on data sources of RDL reports.&lt;/P&gt;&lt;P&gt;Can we help me ?&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 10:36:27 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4803538#M41711</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-08-21T10:36:27Z</dc:date>
    </item>
    <item>
      <title>Re: MAJ version PBIRS JAN 2025 to MAY 2025</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4804156#M41716</link>
      <description>&lt;P&gt;Hi Samuelhvgf,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;We appreciate your inquiry submitted through the Microsoft Fabric Community Forum.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Based on my understanding, the May 2025 PBIRS release introduced stricter security enforcement for Power BI report connections. SQL and Analysis Services servers must now be explicitly trusted (PBI_SQL_TRUSTED_SERVERS) and present a valid TLS certificate. This change explains why PBIX reports fail while RDL reports, which use a different credential handling mechanism, continue to function. In some instances, if encryption keys were not restored correctly or if the PBIRS service account was changed during the upgrade, stored credentials may also become invalid.&lt;/P&gt;
&lt;P&gt;Please follow the steps below, which may help to resolve the issue:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Publish reports using the matching Power BI Desktop version for May 2025 Optimized for PBIRS.&lt;/LI&gt;
&lt;LI&gt;Ensure that SQL/AS servers use valid TLS certificates and that the FQDN in the connection string matches the certificate.&lt;/LI&gt;
&lt;LI&gt;If credentials remain invalid, restore the encryption keys via Report Server Configuration Manager: navigate to Encryption Keys and then select Restore.&lt;/LI&gt;
&lt;LI&gt;In the PBIRS portal, go to Manage and next to Data Sources, re-enter the stored credentials, and test the connection.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;For additional information, please refer to the following documentation:&lt;BR /&gt;&lt;A href="https://learn.microsoft.com/en-us/power-bi/report-server/data-sources" target="_blank"&gt;Power BI report data sources in Power BI Report Server - Power BI | Microsoft Learn&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;We hope the information provided helps to resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric Community.&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 19:35:55 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4804156#M41716</guid>
      <dc:creator>v-pnaroju-msft</dc:creator>
      <dc:date>2025-08-21T19:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: MAJ version PBIRS JAN 2025 to MAY 2025</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4804402#M41720</link>
      <description>&lt;P&gt;After upgrading PBIRS from Jan 2025 to May 2025, encrypted connection strings in Power BI reports may break publishing and scheduling. RDL reports are unaffected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How to Fix:&lt;/P&gt;&lt;P&gt;Set this environment variable on the server:&lt;BR /&gt;PBIRS_EnableLegacyConnectionStringHandling = True&lt;BR /&gt;Then restart the PBIRS service.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Aug 2025 03:56:38 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4804402#M41720</guid>
      <dc:creator>Shahid12523</dc:creator>
      <dc:date>2025-08-22T03:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: MAJ version PBIRS JAN 2025 to MAY 2025</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4807177#M41749</link>
      <description>&lt;P&gt;Hi Samuelhvgf,&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We would like to follow up and see whether the details we shared have resolved your problem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If you need any more assistance, please feel free to connect with the Microsoft Fabric community.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Aug 2025 17:39:26 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4807177#M41749</guid>
      <dc:creator>v-pnaroju-msft</dc:creator>
      <dc:date>2025-08-25T17:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: MAJ version PBIRS JAN 2025 to MAY 2025</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4810519#M41762</link>
      <description>&lt;P&gt;Hi Samuelhvgf,&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Aug 2025 14:33:40 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4810519#M41762</guid>
      <dc:creator>v-pnaroju-msft</dc:creator>
      <dc:date>2025-08-28T14:33:40Z</dc:date>
    </item>
    <item>
      <title>Re: MAJ version PBIRS JAN 2025 to MAY 2025</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4812581#M41770</link>
      <description>&lt;P&gt;Hi Samuelhvgf,&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We wanted to see if the information we gave helped fix your problem. If you need more help, please feel free to contact the Microsoft Fabric community.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 31 Aug 2025 17:21:10 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/MAJ-version-PBIRS-JAN-2025-to-MAY-2025/m-p/4812581#M41770</guid>
      <dc:creator>v-pnaroju-msft</dc:creator>
      <dc:date>2025-08-31T17:21:10Z</dc:date>
    </item>
  </channel>
</rss>

