SSAS instance required for March 2018 PBIRS

[Bokkiem]

Hi,

 when we have tried to install the March version of Report Server, we get this error...

"The description for Event ID 38 from source MSOLAP$PBIRS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."

Has anyone else had this issue?

With the October 2017 Report Server, an SSAS instance wasn't required. is this due to the addition of the Quick Calcs in the latest version.

Thanks in advance,

Emma

[Jon-Heide]

No, SSAS is not required to use any edition of PowerBI report server. PowerBI report servers after October includes an internal instance of SSAS running. You can check the setup logs, or server logs for more detailed information on the error. 

[fantus]

First, that's not a helpful response as there is no additional data in the error logs. That's part of the problem--this installation of power bi seems to leave out the necessary event id codes for the event viewer to tell us exactly what is happening with the error. perhaps you can tell us what Event ID 38 is exactly, since the software itself doesn't elucidate on that?

This is all that is shown for this error in the event log:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="MSOLAP$PBIRS" /> 
  <EventID Qualifiers="49441">38</EventID> 
  <Level>2</Level> 
  <Task>289</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2018-06-05T14:29:47.000000000Z" /> 
  <EventRecordID>95748</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>[redacted]</Computer> 
  <Security /> 
  </System>
  <EventData /> 
  </Event>

This error is raised immediately after the service is started, and only then.

What is event ID 38? Why didn't the PBIRS installation add the event data to the server? (There were no problems indicated in the installation).

[Bokkiem]

Hi Microsoft,

Please can we have  details on a solution for this?

We are still using the October 2017 version of Report server and facing isues every day with slicers and refreshes.

Thanks

[fantus]

That's not a helpful response as there is no further information in any of the logs about this error. How do we fix/resolve this error?