Can't open or publish reports on PBI Report Server May 2023

[abounou]

Hello everyone,

I have an issue with Power BI Report Server (May 2023), I can't open reports published on the report server, Reports connected to an SSAS cube using live connection are working but every report that is using an import connection wether it's a SQL Server, Excel or an online service connection is not working. I get the following error when opening the reports

Also when I try to publish reports to the report server I get the following error

 When I checked the logs for the RSpowerBI logs, I found the following ERROR :

5 12:18:49.3004|ERROR|10|GetPbixReportMetadataAsync RSPortal returned error code ServiceUnavailable for catalogItem 16cb1220-6a9b-457a-b163-906adf64d43e. Check Portal logs.| RequestID = efaa1c3d-fd33-280e-3334-213a10c39108 ClientSessionID = de0d36b8-3888-d627-2c83-1a3fd9221706 
2023-07-05 12:18:49.3004|ERROR|14|GetPbixReportMetadataAsync RSPortal returned error code ServiceUnavailable for catalogItem 16cb1220-6a9b-457a-b163-906adf64d43e. Check Portal logs.| RequestID = e97930ba-9fe7-e7ba-567e-a06a3d91479c ClientSessionID = de0d36b8-3888-d627-2c83-1a3fd9221706 
2023-07-05 12:18:49.3004|ERROR|18|GetDataSource ERROR for catalogItem=16cb1220-6a9b-457a-b163-906adf64d43e, Exception=Service Unavailable, ElapsedMs=81| RequestID = e97930ba-9fe7-e7ba-567e-a06a3d91479c ClientSessionID = de0d36b8-3888-d627-2c83-1a3fd9221706 
2023-07-05 12:18:49.3004|ERROR|5|GetDataSource ERROR for catalogItem=16cb1220-6a9b-457a-b163-906adf64d43e, Exception=Service Unavailable, ElapsedMs=81| RequestID = efaa1c3d-fd33-280e-3334-213a10c39108 ClientSessionID = de0d36b8-3888-d627-2c83-1a3fd9221706 
2023-07-05 12:18:49.3004|ERROR|18|Failure in querydata catalogObjectId=16cb1220-6a9b-457a-b163-906adf64d43e, requestId=efaa1c3d-fd33-280e-3334-213a10c39108, clientSessionId=de0d36b8-3888-d627-2c83-1a3fd9221706| RequestID = efaa1c3d-fd33-280e-3334-213a10c39108 ClientSessionID = de0d36b8-3888-d627-2c83-1a3fd9221706 Microsoft.PowerBI.ReportServer.WebApi.Catalog.CatalogAccessException: Service Unavailable

 As for the RSportal logs, I found the following ERROR :

2023-07-05 12:23:47.3754|ERROR|59|library|Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ICT Roadmaps/BI Roadmap' cannot be found.;| RequestID = s_beb5be04-9b17-43b3-b00b-87932e973f89 
2023-07-05 12:23:54.9067|ERROR|27|The remote server returned an error: (400) Bad Request.| RequestID = s_beb5be04-9b17-43b3-b00b-87932e973f89 

 The report mentionned in the error does exist, I managed to download it from RS and open it in PowerBI Desktop for RS. Also both the Report Server and Power BI Desktop for RS are of the same version (May 2023).
I've tried the follwing but no results :
 * Running the Report.exe and repair the installation.
 * Restaring SQL Server instance as well as restarting the Report Server.
 * Restarting the host machine.
 * I ran the command : netsh http show urlacl and the entry https://+:443/PowerBI/ exists.
Can anyone help with this issue please?

[josef78 · Accepted solution]

If I understand, problem with loading model from MSSQL storage to internal AS instance, or with connection report to internal AS instance. Please, first check ExectutionLog3 view for ItemAction with value "ASModelStream", if failing or not.

Additionally check Power BI RS configuration manager, especially if using correct service account and database credentials (best practices is use same domain service account for both)

[josef78 · Accepted solution]

If I understand, problem with loading model from MSSQL storage to internal AS instance, or with connection report to internal AS instance. Please, first check ExectutionLog3 view for ItemAction with value "ASModelStream", if failing or not.

Additionally check Power BI RS configuration manager, especially if using correct service account and database credentials (best practices is use same domain service account for both)

[abounou · Accepted solution]

You are right, I checked the RS configuration and we were using the default service account which was lacking some permissions. We have created a new service account with the proper permissions and problem has been resolved.