Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi guys,
so we this weird problem when trying to deploy a Power BI report from Power BI Desktop (October 2017) to Power BI Report Server after upgrading from the June release to the October release of both PBI Report Server and PBI Desktop.
The error message is the following when deploying from PBI Desktop: An error occured while attempting to save the report to Power BI Report Server
It seems we are not the only ones having this problem after looking at this forum. The thing is, after looking at the logs it seems that our problem is not the same as others are having. It seems related to the new AS "instance" that the report server is now hosting. You can see the error log that we get just after getting the error:
RSPowerBI... log:
2017-11-14 15:19:23.1209|INFO|31|Received request POST /api/reportpropertiesfromlocalfiles| RequestID = s_e9d2d26d-87ef-474f-98b6-e7d2ca0e73b5 2017-11-14 15:19:23.1209|INFO|31|CFG : EnableCustomVisuals = [True] (env) 2017-11-14 15:19:25.1678|ERROR|31|Failed to connect to AS| RequestID = s_e9d2d26d-87ef-474f-98b6-e7d2ca0e73b5 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 [::1]:5132 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) --- End of inner exception stack trace --- 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 --- 2017-11-14 15:19:25.1678|ERROR|31|Failure in reportproperties| RequestID = s_e9d2d26d-87ef-474f-98b6-e7d2ca0e73b5 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 [::1]:5132 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) --- End of inner exception stack trace --- 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 --- at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesFactory.CreateASWrapper(String serverAddress, Int32 port, TimeSpan timeout) at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesServer.<LoadDatabaseAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.ReportServer.WebApi.PBIX.DataModelDataSourceProvider.<RetrieveEmbeddedDataSourcesAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.ReportServer.WebApi.PbiApi.PbiApiController.<ShredWithModel>d__7b.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.ReportServer.WebApi.PbiApi.PbiApiController.<ShredFromPreshreddedFiles>d__51.MoveNext() 2017-11-14 15:19:25.1678|INFO|31|Sending response. Response code NT SERVICE\PowerBIReportServer 400, Elapsed time 0:00:02.0466683| RequestID = s_e9d2d26d-87ef-474f-98b6-e7d2ca0e73b5
Any suggestions to fix this?
I'm having the same issue with both methods.
I have the october release of the report server and the powerbi desktop app. Our logs are showing the same errors.
Which October version did you run? I tested on the latest October version 1.1.6530.30789, not reproduce the issue. Would you please test in this version again?
Best Regards,
Qiuyun Yu
I have this exact version of the PBIRS installed and get the exact same error described by the original post.
Any further insights would be appreciated.
Thanks,
Eric
Can you check the RSHostingService and msmdsrv logs in the PBIRS installation LogFiles folder and let me know if you see any errors? Also are you able to upload the report from the Report portal? Thanks!
I was just able to solve the issue by changing the Service Account in the Configuration Manager from Network Service to a local account with proper permissions by following the guidance on https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/configure-the-report-server-...
Thanks!
Hi guys,
sorry for the late response, I had to roll back to the June release because we needed to use that server actively. This rollback (uninstall then reinstall the June version) run without issues.
Then I tried to upgrade again to the October release with the same results as I show in my previous posts. The Report Server version is: 1.1.6530.30789.
@mgmeyer here you have some logs. The AS service definitely has some kind of issue. I'll try changing the Service Account as @emixon suggested, but even if it works it's not a proper solution IMHO.
RSHostingService:
2017-11-30 09:09:18.7560|INFO|29|Throttled restart of process by 3.598.796,88ms: AS 2017-11-30 09:09:19.9592|WARN|24|Child Process [AS] Died. Check the log for further information
msmdsrv.log (the same sequence I'm showing below repeats itself every hour it seems):
(30/11/2017 9:09:19) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210019) (30/11/2017 9:09:19) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210019) (30/11/2017 9:09:19) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A) (30/11/2017 9:09:19) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A) (30/11/2017 9:09:19) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A) (30/11/2017 9:09:19) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A) (30/11/2017 9:09:19) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A) (30/11/2017 9:09:19) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000B) (30/11/2017 9:09:19) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210019) (11/30/2017 9:09:19 AM) Message: The Vertipaq thread pool now has 2 minimum threads, 4 maximum threads, and a concurrency of -1. Its thread pool affinity mask is 0x000000000000000f. (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x4121000A) (11/30/2017 9:09:19 AM) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 286, Event ID: 0x411E0015) (11/30/2017 9:09:19 AM) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 286, Event ID: 0x411E000F) (11/30/2017 9:09:19 AM) Message: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 286, Event ID: 0x411E0016) (11/30/2017 9:09:19 AM) Message: The flight recorder snapshot definition file 'C:\Program Files\Microsoft Power BI Report Server\PBIRS\ASEngine\FlightRecorderSnapshotDef.xml' was not found, skipping initialization of snapshot activity. (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210021) (11/30/2017 9:09:19 AM) Message: The flight recorder was started. (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210005) (11/30/2017 9:09:19 AM) Message: Cannot start the server in Tabular mode as the needed privilege for memory locking is not held (SE_INC_WORKING_SET_NAME or SE_INC_BASE_PRIORITY_NAME, depending on your operating system version) (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210025) (11/30/2017 9:09:19 AM) Message: The service cannot be started: The following system error occurred: (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210000) (11/30/2017 9:09:19 AM) Message: Service stopped. (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210001)
Thanks!
Hi again guys,
I got it working.
If you open the PBI configuration manager, in the Service Account tab, the default is "Use built-in account" and in the dropdown list, the option is Virtual Service Account. The actual account used is "NT SERVICE\PowerBIReportServer".
As soon as I changed to "Use another account" and put there the details of an account that is administrator in that machine, everything started to work.
I saw a very similar issue when installing the Analysis Services instance during the SQL Server 2017 installation. The service wouldn't start until I changed from the default service account to an account with administrative privileges. Since it seems PBI report server (October 2017 version) and SQL Server 2017 share the same AS version, it makes sense that they share the same issues too.
IMHO changing the service account is a workaround, not a solution, for both report server and SQL Server 2017 AS. I don't know if you guys at Microsoft can tell us anything about this, but it would be really appreciated
Hi @jcabgz,
1. Please try to use Upload button in web portal to publish reports to see if the same error throws out.
2. Please restart the Power BI report server service.
Best Regards,
Qiuyun Yu
Hi Qiuyun,
Thanks for your answer. Here you have the info you requested:
1. I tried this and also got an error. The error message is different though: "There was an error uploading your .pbix file. Verify that the file has not been corrupted and that the file extension matches the format of the file.". A similar message pops up in the log files, like when deploying from PBI Desktop, related to AS:
2017-11-16 11:21:15.2343|INFO|235|Received request POST /api/reportpropertiesfromlocalfiles| RequestID = s_c821fe83-856a-44af-91b8-71dfa25531bd 2017-11-16 11:21:15.2343|INFO|235|CFG : EnableCustomVisuals = [True] (env) 2017-11-16 11:21:17.2531|ERROR|235|Failed to connect to AS| RequestID = s_c821fe83-856a-44af-91b8-71dfa25531bd 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 [::1]:5132 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) --- End of inner exception stack trace --- 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 --- 2017-11-16 11:21:17.2531|ERROR|235|Failure in reportproperties| RequestID = s_c821fe83-856a-44af-91b8-71dfa25531bd 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 [::1]:5132 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) --- End of inner exception stack trace --- 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 --- at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesFactory.CreateASWrapper(String serverAddress, Int32 port, TimeSpan timeout) at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesServer.<LoadDatabaseAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.ReportServer.WebApi.PBIX.DataModelDataSourceProvider.<RetrieveEmbeddedDataSourcesAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.ReportServer.WebApi.PbiApi.PbiApiController.<ShredWithModel>d__7b.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.ReportServer.WebApi.PbiApi.PbiApiController.<ShredFromPreshreddedFiles>d__51.MoveNext() 2017-11-16 11:21:17.2531|INFO|235|Sending response. Response code NT SERVICE\PowerBIReportServer 400, Elapsed time 0:00:02,0194142| RequestID = s_c821fe83-856a-44af-91b8-71dfa25531bd
2. Already tested this and it didn't work.
Thanks for your help!
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
3 | |
3 | |
1 | |
1 | |
1 |
User | Count |
---|---|
5 | |
5 | |
4 | |
4 | |
4 |