Power BI Report Server September 2023: Cannot render PBIX

[Medina]

Hi Community,

After installing Power BI Report Server September 2023, we started getting the following error while trying to run our Power BI reports. Any ideas?

Error after installing September 2023

[Medina]

Hi,

Below is the info from the RSPowerBI log file. Thank you!

2023-10-06 08:59:57.9422|INFO|112|Sending response. Response code domain\username 500, Elapsed time 0:00:02.3326553| RequestID = 521e3e2f-e940-6a0d-1bc1-341cdf8bcf14 ClientSessionID = d023b467-0c4d-767b-b72e-0bf830007451
2023-10-06 09:00:06.4055|INFO|88|Received request GET /api/explore/reports/2772871c-4c20-4100-ba8e-fcaf3c9ab1e4/modelsAndExploration| RequestID = aadd6b12-5f9c-de5d-3465-682379760425 ClientSessionID = d023b467-0c4d-767b-b72e-0bf830007451
2023-10-06 09:00:08.7919|ERROR|112|Failed to connect to AS| RequestID = aadd6b12-5f9c-de5d-3465-682379760425 ClientSessionID = d023b467-0c4d-767b-b72e-0bf830007451 Microsoft.PowerBI.ReportServer.AsServer.AsConnectionException: Failed to connect to AS ---> Microsoft.AnalysisServices.ConnectionException: A connection cannot be made. Ensure that the server is running. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:5132
at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(IConnectivityOwner owner, ConnectionInfo connectionInfo)
--- End of inner exception stack trace ---
at Microsoft.AnalysisServices.XmlaClient.OpenConnectionAndCheckIfSessionTokenNeeded(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.XmlaClient.OpenConnection(ConnectionInfo connectionInfo, Boolean& isSessionTokenNeeded)
at Microsoft.AnalysisServices.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
at Microsoft.AnalysisServices.Core.Server.Connect(String connectionString, String sessionId, ObjectExpansion expansionType)
at Microsoft.AnalysisServices.Core.Server.Connect(String connectionString)
at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesFactory.CreateASWrapper(String serverAddress, Int32 port, TimeSpan timeout)
--- End of inner exception stack trace ---
2023-10-06 09:00:08.7919|INFO|32|Sending response. Response code domain\username 500, Elapsed time 0:00:02.3870728| RequestID = aadd6b12-5f9c-de5d-3465-682379760425 ClientSessionID = d023b467-0c4d-767b-b72e-0bf830007451
2023-10-06 09:00:25.3749|INFO|107|Received request GET /api/explore/reports/2772871c-4c20-4100-ba8e-fcaf3c9ab1e4/modelsAndExploration| RequestID = db6d34d8-e2f6-012f-634e-e6ad4656d898 ClientSessionID = d023b467-0c4d-767b-b72e-0bf830007451
2023-10-06 09:00:27.7424|ERROR|109|Failed to connect to AS| RequestID = db6d34d8-e2f6-012f-634e-e6ad4656d898 ClientSessionID = d023b467-0c4d-767b-b72e-0bf830007451 Microsoft.PowerBI.ReportServer.AsServer.AsConnectionException: Failed to connect to AS ---> Microsoft.AnalysisServices.ConnectionException: A connection cannot be made. Ensure that the server is running. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:5132
at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(IConnectivityOwner owner, ConnectionInfo connectionInfo)
--- End of inner exception stack trace ---
at Microsoft.AnalysisServices.XmlaClient.OpenConnectionAndCheckIfSessionTokenNeeded(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.XmlaClient.OpenConnection(ConnectionInfo connectionInfo, Boolean& isSessionTokenNeeded)
at Microsoft.AnalysisServices.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
at Microsoft.AnalysisServices.Core.Server.Connect(String connectionString, String sessionId, ObjectExpansion expansionType)
at Microsoft.AnalysisServices.Core.Server.Connect(String connectionString)
at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesFactory.CreateASWrapper(String serverAddress, Int32 port, TimeSpan timeout)
--- End of inner exception stack trace ---
2023-10-06 09:00:27.7424|INFO|98|Sending response. Response code domain\username 500, Elapsed time 0:00:02.353554| RequestID = db6d34d8-e2f6-012f-634e-e6ad4656d898 ClientSessionID = d023b467-0c4d-767b-b72e-0bf830007451
2023-10-06 09:00:27.8966|INFO|107|Received request GET /libs/styles/InfoNav-Sprites.png| RequestID = s_46c97384-44a1-4473-890a-c06f8d544336

[v-alipat]

@Medina hi again, 

Until a permanent fix in RS is provided, you can try out a workaround suggested in this thread to unblock yourself: 
https://community.fabric.microsoft.com/t5/Report-Server/Microsoft-PowerBI-ReportServer-AsServer-AsCo... 

Thanks,

Alexandra 

[v-alipat]

Thanks @Medina ! 

I checked with collegues, and was informed that there were some other complains also pointing to some problems in Analysis Services. These are being investigated now. 

We can't be sure if what you see is the same issue. It would greatly help if you contact Power BI Support, and open a case with them, to share more details, also they would possibly come up with a workaround for you. 

https://support.fabric.microsoft.com/en-US/support 

Thanks,

Alexandra 

[v-alipat]

Hi @Medina 

Could you please share more details on your case, so that we can try to replicate / investigate it? 

For example, what type of data source connection does your report have? 

Is it DQ / Live connection? To what source? 

When was the report created?

Which version of Report Server did you have previously, and did it work there? 

Did your upgrade go smoothly? 

Could you please check the logs in your server machine and see if you can share anything from there? (kindly remove any sensitive info) 

Thanks,

Alexandra 

[Medina]

Hi v-alipat,

Here is the information:

• Server type: Test server
• Previous version: May 2023 and It worked fine.
• Data Source Connection: Import. Connecting to SQL Server
• When was the report created: I do not remember, but it was uploaded to the server on 04/25/2023
• Did your upgrade go smoothly? It did go smoothly. The paginated reports run fine.

From RSPortal log file

2023-10-02 13:55:16.4203|INFO|48|Received request GET /api/v2.0/System/Properties| RequestID = s_7a7d67e9-954a-4584-a3f6-e6762e2f93c0
2023-10-02 13:55:16.4203|INFO|26|Received request GET /assets/img/fi/pbirs/favicon.ico| RequestID = s_a89de641-fac6-4469-82fb-7d4213b6226c
2023-10-02 13:55:16.4672|INFO|36|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0349678| RequestID = s_7a7d67e9-954a-4584-a3f6-e6762e2f93c0
2023-10-02 13:55:16.4828|INFO|48|Received request GET /assets/img/fi/pbirs/favicon.ico| RequestID = s_f7966a9e-aaaa-487b-bde1-6951afef2600
2023-10-02 13:55:16.4985|INFO|48|Received request GET /api/v2.0/CatalogItems(Path='/')| RequestID = s_91e43226-4c60-4d0b-8bb8-ea32089f7e77
2023-10-02 13:55:16.4985|INFO|72|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0076477| RequestID = s_91e43226-4c60-4d0b-8bb8-ea32089f7e77
2023-10-02 13:55:20.5142|INFO|48|Received request GET /api/v2.0/CatalogItems(Path='/Report%20Monitor')/AllowedActions| RequestID = s_c774549c-fe7a-48d7-ab42-91ec384b7c67
2023-10-02 13:55:20.5142|INFO|26|Received request GET /api/v2.0/System/Properties| RequestID = s_42513388-a795-48ac-9e4c-611d225dc188
2023-10-02 13:55:20.5142|INFO|57|Received request GET /assets/img/fi/pbirs/favicon.ico| RequestID = s_ecd49914-d907-4d5d-82d1-60f01970ad23
2023-10-02 13:55:20.5142|INFO|36|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0086265| RequestID = s_c774549c-fe7a-48d7-ab42-91ec384b7c67
2023-10-02 13:55:20.5298|INFO|17|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0170396| RequestID = s_42513388-a795-48ac-9e4c-611d225dc188
2023-10-02 13:55:20.5455|INFO|26|Received request GET /assets/img/fi/pbirs/favicon.ico| RequestID = s_7795fefc-ca7f-45bf-85df-9bb76e0b9146
2023-10-02 13:55:20.5455|INFO|48|Received request GET /api/v2.0/CatalogItems(Path='/Report%20Monitor')| RequestID = s_34b34e08-38cb-4cb8-90ba-7d7835687a3c
2023-10-02 13:55:20.5611|INFO|36|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0078993| RequestID = s_34b34e08-38cb-4cb8-90ba-7d7835687a3c
2023-10-02 13:55:20.6705|INFO|48|Received request GET /api/v2.0/catalogitems(1fb5cf1f-0078-4f2c-8b9c-0fb66e3a784d)/Model.Folder/catalogitems/| RequestID = s_b61864e6-0aa7-41e5-93a0-f41da05b25ff
2023-10-02 13:55:20.8736|INFO|36|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.1963981| RequestID = s_b61864e6-0aa7-41e5-93a0-f41da05b25ff
2023-10-02 13:55:27.3113|INFO|26|Received request GET /api/v2.0/CatalogItems(Path='/Report%20Monitor/Hello%20World')| RequestID = s_6e98b079-54e4-4212-95fc-8527fc1cfe7a
2023-10-02 13:55:27.3113|INFO|48|Received request GET /api/v2.0/PowerBIReports(Path='/Report%20Monitor/Hello%20World')/AllowedActions| RequestID = s_698d3253-6aa6-4a66-9a61-45b83ef145c1
2023-10-02 13:55:27.3269|INFO|49|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0155961| RequestID = s_6e98b079-54e4-4212-95fc-8527fc1cfe7a
2023-10-02 13:55:27.3269|INFO|72|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0178083| RequestID = s_698d3253-6aa6-4a66-9a61-45b83ef145c1
2023-10-02 13:55:27.4675|INFO|26|Received request GET /assets/img/fi/pbirs/favicon.ico| RequestID = s_936fdc44-08be-42e5-881c-b2cf51522d5e
2023-10-02 13:55:27.4675|INFO|48|Received request GET /api/v2.0/CatalogItems(Path='/Report%20Monitor/Hello%20World')/AllowedActions| RequestID = s_3069a190-1a1b-4434-a924-72406c64edb1
2023-10-02 13:55:27.4831|INFO|72|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0132872| RequestID = s_3069a190-1a1b-4434-a924-72406c64edb1
2023-10-02 13:55:27.5300|INFO|48|Received request GET /api/v2.0/CatalogItems(Path='/Report%20Monitor/Hello%20World')/AllowedActions| RequestID = s_6233465e-97bd-4ccf-af52-ce0e64f0e382
2023-10-02 13:55:27.5300|INFO|26|Received request GET /api/v2.0/System/WebPortalRelativeUrl| RequestID = s_351fafca-850b-4012-9f27-857be7156ce0
2023-10-02 13:55:27.5300|INFO|57|Received request GET /assets/img/fi/pbirs/favicon.ico| RequestID = s_41576c06-27fc-43d1-8ffa-644640b48cf5
2023-10-02 13:55:27.5300|INFO|26|Fetched ProductVersion 1.18.8668.33514| RequestID = s_351fafca-850b-4012-9f27-857be7156ce0
2023-10-02 13:55:27.5300|INFO|23|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0022451| RequestID = s_351fafca-850b-4012-9f27-857be7156ce0
2023-10-02 13:55:27.5457|INFO|72|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0143634| RequestID = s_6233465e-97bd-4ccf-af52-ce0e64f0e382
2023-10-02 13:55:35.1419|INFO|49|Sending response. Response code Domain\username 200, Elapsed time 0:01:25.8744429| RequestID = s_4044bf44-8bb1-48df-b958-e5c73efaf2ee
2023-10-02 13:57:10.2659|INFO|82|Received request GET /api/v2.0/System/Properties| RequestID = s_9e826afd-8233-4572-9e87-f66fc586da42
2023-10-02 13:57:10.2659|WARN|41|Received a request with an unmatched or no authentication scheme. 401
2023-10-02 13:57:10.2659|INFO|37|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0055657| RequestID = s_9e826afd-8233-4572-9e87-f66fc586da42
2023-10-02 13:57:10.3284|INFO|82|Received request GET /api/v2.0/CatalogItems(Path='/')| RequestID = s_23d47949-4818-4b40-bbb0-b173b8bd8f65
2023-10-02 13:57:10.3284|INFO|41|Received request GET /assets/img/fi/pbirs/favicon.ico| RequestID = s_01ec4374-ff2e-4f64-86f8-e19495336b8d
2023-10-02 13:57:10.3284|INFO|73|Sending response. Response code Domain\username 200, Elapsed time 0:00:00.0089298| RequestID = s_23d47949-4818-4b40-bbb0-b173b8bd8f65
2023-10-02 13:57:10.4378|INFO|82|Received request GET /assets/img/fi/pbirs/favicon.ico| RequestID = s_2e564098-9db6-4de6-8479-e90ec15cd922

[v-alipat]

Thanks @Medina 

The log you shared doesn't show the error, you likely need to look into RSPowerBI log instead of RSPortal.

Can you please check there? 

And we are not able to reproduce the problem locally so far. 

If you want, you may share the logs of the error if they are located in RSPowerBI log, and we will try to see if there are any hints about what's happening. However, the most efficiant way in your case would be to reach out to Power BI Support, and creating a ticket. 

https://support.fabric.microsoft.com/en-US/support/ 

Thanks,

Alexandra Ipatova