<?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 Power BI March 2018 Not Functional in Report Server</title>
    <link>https://community.fabric.microsoft.com/t5/Report-Server/Power-BI-March-2018-Not-Functional/m-p/422896#M5763</link>
    <description>&lt;P&gt;I've run through this process in a test environment and can't seem to complete the upgrade to PBI RS from the March 2018 release.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm starting from an SSRS 2016 server.&amp;nbsp; Ran through the upgrade process to the PowerBI RS October 2017 release.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From there everything seems to work fine.&amp;nbsp; I can browse the folders, run reports, no problem.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I attempt to install the PBIRS March 2018 release, it seems to go through just fine but the report server is not browsable.&amp;nbsp; All we get is a notice "Something went wrong.&amp;nbsp; Please try again later".&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've attempted this process several times.&amp;nbsp; It leaves me in exactly the same spot every time.&amp;nbsp; As far as I can tell, the March 2018 release of PBI Report Server is a bust.&lt;/P&gt;</description>
    <pubDate>Tue, 22 May 2018 16:59:25 GMT</pubDate>
    <dc:creator>zumaval</dc:creator>
    <dc:date>2018-05-22T16:59:25Z</dc:date>
    <item>
      <title>Power BI March 2018 Not Functional</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/Power-BI-March-2018-Not-Functional/m-p/422896#M5763</link>
      <description>&lt;P&gt;I've run through this process in a test environment and can't seem to complete the upgrade to PBI RS from the March 2018 release.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm starting from an SSRS 2016 server.&amp;nbsp; Ran through the upgrade process to the PowerBI RS October 2017 release.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From there everything seems to work fine.&amp;nbsp; I can browse the folders, run reports, no problem.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I attempt to install the PBIRS March 2018 release, it seems to go through just fine but the report server is not browsable.&amp;nbsp; All we get is a notice "Something went wrong.&amp;nbsp; Please try again later".&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've attempted this process several times.&amp;nbsp; It leaves me in exactly the same spot every time.&amp;nbsp; As far as I can tell, the March 2018 release of PBI Report Server is a bust.&lt;/P&gt;</description>
      <pubDate>Tue, 22 May 2018 16:59:25 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/Power-BI-March-2018-Not-Functional/m-p/422896#M5763</guid>
      <dc:creator>zumaval</dc:creator>
      <dc:date>2018-05-22T16:59:25Z</dc:date>
    </item>
    <item>
      <title>Re: Power BI March 2018 Not Functional</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/Power-BI-March-2018-Not-Functional/m-p/423077#M5768</link>
      <description>&lt;P&gt;Some more information. I did a seperate install on a fresh database to see if I was missing anything and there were 80+ objects missing.&amp;nbsp; Mostly stored procedures, some tables.&amp;nbsp; Either way, I think that the server worked after the Oct 2017 install was superficial only.&amp;nbsp; I had only attempted to run SSRS paginated reports and no PBI reports. My guess is it wasn't really working with the old version either.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 May 2018 21:40:37 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/Power-BI-March-2018-Not-Functional/m-p/423077#M5768</guid>
      <dc:creator>zumaval</dc:creator>
      <dc:date>2018-05-22T21:40:37Z</dc:date>
    </item>
  </channel>
</rss>

