topic Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019) in Report Server

Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

Anonymous — Fri, 04 Oct 2019 06:28:53 GMT

Hi all,

We have installed the Power BI Report Server (Developer) Edition on our test machine (15.0.1102.597). The machine is running SQL Server 2016 Developer Edition. Calling the Report Server Web Service URLs works properly. However, when calling the Web Portal URL, we are getting an 503 error.

The RSHostingService LogFile contains the following information:

################

################

Does anyone have an idea what to do against the dying RSPortal process? It worked properly with an older version of Power BI report server. I also tried assigning another Web Portal Virtual Directory and another Port. No success. Restarts did not work either.

Thank you for any help,

kind regards,

Patrick Wolf

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

mturcotte_epq — Fri, 04 Oct 2019 13:15:50 GMT

Could you share the most recent log files found under C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles ?

This could help us help you...

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

kztina — Sun, 06 Oct 2019 18:32:14 GMT

Hi all,

Today, after upgrade working version 15.0.1102.299 (January 2019)

We've got exactly the same problem.

Tried to remove and install, to repair , to change SERVICE ACCOUNT, WEB PORTAL URL - didn't help.

LOGS:

RSPortal

---------

RSHostingService

--------------------

...

-------------------------------------------

RUNS ON WINDOWS SERVER 2016

Microsoft SQL Server 2016 (SP2-CU7)

------------------------------------------

Maybe this version does not work at all?

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

d_gosbell — Mon, 07 Oct 2019 06:30:49 GMT

kztina wrote:

Maybe this version does not work at all?

No, it's running OK on my local machine (with the exception of some of the custom visual slicers, but MS are working on a fix for that). The logs don't appear to give us much to go on. Have you tried checking the Application log in Windows Event viewer to see if there are any errors related to Report Server in there?

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

Anonymous — Mon, 07 Oct 2019 06:48:58 GMT

Here is the content of the RSHostingService Logfile after a recent restart of the service:

#########################

####################################

And this is the content of the RSPortal Logfile

#######################################

#######################################

I found this error (and several others) in the Windows Application Log at the time of the service restart:

The description for Event ID 25 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.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

msmdsrvi.rll
1031"

#######################################

Kind regards,

Patrick

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

d_gosbell — Mon, 07 Oct 2019 23:41:24 GMT

That event from MSOLAP$PBIRS is not crticial. I've seen that on other servers and I do not think it would not be causing the portal process to die.

You may have to consider raising an official support ticket with Microsoft for this.

One other thing you could try would be to turn on verbose logging for PBIRS

PBI Report Server enable verbose log

Enabling verbose logging in Power BI Report Server is exactly same as how it was done in SQL Server Reporting Services. Here is how you can do that:

1) Open <install directory>\PBIRS\ReportServer\bin\ReportingServicesService.exe.config

2) Under <system.diagnostics>, there is a switch called "DefaultTraceSwitch". Change the value to "4".

3) Under <RStrace>, there is a configuration called "Components". Change the value to "all:4".

Once you've done this I think you'll need to stop and start report server from the config manager. Maybe this will provide some extra information in the logs about why the RSPortal process dies.

PS. you will want to remember to reset the logging level back to the default level once you are finished as the verbose logging will use a lot of extra disk space.

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

Anonymous — Tue, 08 Oct 2019 05:34:57 GMT

Hi,

thanks for the Logging trick. I changed the configuration file and restarted the server.

May I ask: How do I open an official support ticket with Microsoft regarding Power BI Server?

Here is the extended output of RSHostingService Logfile after the restart. From my point of view, there is no additional helpful information included :(

##########################################

#################################################

The RSPortal Logfile has not changed:

#################################################

###################################################

There is a new PowerBI logfile with some errors regarding ExtendedEvents logging. I don't think it is the cause of my problem

###################################################

2019-10-08 07:25:04.9450|INFO|1|File Logger created: C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPowerBI_2019_10_08_07_25_04.log - level Trace, will roll at 32 Mb, process id 10556
2019-10-08 07:25:04.9919|INFO|1|Do not dump on: Microsoft.PowerBI.ReportServer.WebApi.Catalog.CatalogAccessException,System.Threading.ThreadAbortException,System.OutOfMemoryException,System.ObjectDisposedException,System.IO.IOException,System.IO.FileLoadException,System.AppDomainUnloadedException,System.Net.Http.HttpRequestException,System.Net.HttpListenerException,System.OperationCanceledException,System.InvalidOperationException
2019-10-08 07:25:04.9919|TRACE|1|Setting unhandled exception handler
2019-10-08 07:25:04.9919|INFO|1|Provider name
2019-10-08 07:25:04.9919|INFO|1|Container name Microsoft SQL Server Reporting Services Key Container 2010
2019-10-08 07:25:04.9919|INFO|1|Setting Symmetric Key
2019-10-08 07:25:05.0075|INFO|1|Setting up Hosted Process State
2019-10-08 07:25:05.0075|DEBUG|1|Attempting to read Configuration from file C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\rsreportserver.config -> C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\rsreportserver.config
2019-10-08 07:25:05.0544|TRACE|5|Start XEventLogger
2019-10-08 07:25:05.4317|INFO|1|The web server needs to run elevated
2019-10-08 07:25:05.4317|INFO|1|Web Server is running.
2019-10-08 07:25:07.0587|INFO|4|Attempting to connect to Analysis Services XEvent logging...
2019-10-08 07:25:07.3100|ERROR|4|Error creating Analysis Services XEvent traceMicrosoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Failed to complete the command. XEvent is not initialized.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.Execute(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteXmlReader()
at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesXEventLogger.TryCreatingAndSubscribingToXEventsTrace()
2019-10-08 07:25:09.3160|INFO|7|Attempting to connect to Analysis Services XEvent logging...
2019-10-08 07:25:09.3160|ERROR|7|Error creating Analysis Services XEvent traceMicrosoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Failed to complete the command. XEvent is not initialized.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.Execute(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteXmlReader()
at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesXEventLogger.TryCreatingAndSubscribingToXEventsTrace()

[...]
Message:Either the trace with the ID of 'PBIRSTrace' does not exist in the server with the ID of 'BI_WIN2016_DEV\PBIRS', or the user does not have permissions to access the object.

###################################################################

Kind regards

Patrick

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

Anonymous — Tue, 08 Oct 2019 05:35:43 GMT

Hi,

thanks for the Logging trick. I changed the configuration file and restarted the server.

May I ask: How do I open an official support ticket with Microsoft regarding Power BI Server?

Here is the extended output of RSHostingService Logfile after the restart. From my point of view, there is no additional helpful information included :(

##########################################

#################################################

The RSPortal Logfile has not changed:

#################################################

###################################################

There is a new PowerBI logfile with some errors regarding ExtendedEvents logging. I don't think it is the cause of my problem

###################################################

2019-10-08 07:25:04.9450|INFO|1|File Logger created: C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPowerBI_2019_10_08_07_25_04.log - level Trace, will roll at 32 Mb, process id 10556
2019-10-08 07:25:04.9919|INFO|1|Do not dump on: Microsoft.PowerBI.ReportServer.WebApi.Catalog.CatalogAccessException,System.Threading.ThreadAbortException,System.OutOfMemoryException,System.ObjectDisposedException,System.IO.IOException,System.IO.FileLoadException,System.AppDomainUnloadedException,System.Net.Http.HttpRequestException,System.Net.HttpListenerException,System.OperationCanceledException,System.InvalidOperationException
2019-10-08 07:25:04.9919|TRACE|1|Setting unhandled exception handler
2019-10-08 07:25:04.9919|INFO|1|Provider name
2019-10-08 07:25:04.9919|INFO|1|Container name Microsoft SQL Server Reporting Services Key Container 2010
2019-10-08 07:25:04.9919|INFO|1|Setting Symmetric Key
2019-10-08 07:25:05.0075|INFO|1|Setting up Hosted Process State
2019-10-08 07:25:05.0075|DEBUG|1|Attempting to read Configuration from file C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\rsreportserver.config -> C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\rsreportserver.config
2019-10-08 07:25:05.0544|TRACE|5|Start XEventLogger
2019-10-08 07:25:05.4317|INFO|1|The web server needs to run elevated
2019-10-08 07:25:05.4317|INFO|1|Web Server is running.
2019-10-08 07:25:07.0587|INFO|4|Attempting to connect to Analysis Services XEvent logging...
2019-10-08 07:25:07.3100|ERROR|4|Error creating Analysis Services XEvent traceMicrosoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Failed to complete the command. XEvent is not initialized.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.Execute(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteXmlReader()
at Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesXEventLogger.TryCreatingAndSubscribingToXEventsTrace()
[...]
Message:Either the trace with the ID of 'PBIRSTrace' does not exist in the server with the ID of 'BI_WIN2016_DEV\PBIRS', or the user does not have permissions to access the object.

###################################################################

Kind regards

Patrick

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

Anonymous — Tue, 08 Oct 2019 05:43:39 GMT

I just found the official Microsoft Support page. However, I need to be a Power BI Pro User in order to raise a ticket. We are using Power BI Report Server as part of our SQL Server 2016 licensing. Thus, I am no Pro User and I am not able to create the ticket. Perhaps someone else with the same problem may help here?

https://powerbi.microsoft.com/de-de/support/

Thanks,

Patrick Wolf

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

d_gosbell — Tue, 08 Oct 2019 22:03:14 GMT

Anonymous wrote:

I just found the official Microsoft Support page. However, I need to be a Power BI Pro User in order to raise a ticket. We are using Power BI Report Server as part of our SQL Server 2016 licensing. Thus, I am no Pro User and I am not able to create the ticket. Perhaps someone else with the same problem may help here?

https://powerbi.microsoft.com/de-de/support/

Thanks,

Patrick Wolf

Technically if you are publishing pbix files to Power BI Report Server you still need a Pro license. It's only the read-only users that don't need pro licenses. Although I don't think this is overly well publicised. There have been prior questions about the need for a pro license on this forum (see https://community.powerbi.com/t5/Report-Server/Power-BI-Report-Server-Do-I-need-a-Pro-License/td-p/221142)

And in the fine print at the bottom of this page: https://powerbi.microsoft.com/en-us/pricing/ you will fine the following:

A Power BI Pro license is required to:

Distribute content to other users, and for peer-to-peer sharing and collaboration.

Publish content to Power BI Premium.

Receive content from other users unless the user is associated with dedicated capacity in Power BI Premium.

Publish content to Power BI Report Server.

At my company also have our PBIRS covered by Enterprise license with SA and as part of that we also have a certain amount of support hours available, but maybe that's just the way our Enterprise Aggreement with Microsoft is structured. Can you maybe check with your IT department to see if you have a Microsoft Account manager who could assist here?

Unfortunately I think this issue is possibly beyond something that volunteers like myself on the forums can assist with and you probably need the help of a dedicate support engineer.

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

SIA — Wed, 09 Oct 2019 04:44:22 GMT

Hello! I have same issue with september update. I tested it yesterday for some hours, tried to install on test enviroment without any previous installations, also tried to upgrade previous version, tried to play with configuration. It didnt work, RSPortal died in all cases.

So, the only way for me now is to downgrade to previous version of PBI RS, from may 2019. If you want, i can share it for you: https://yadi.sk/d/p_2VOu1_DzAjXQ , but I am afraid that it is not english version, but russian.

Sterkhov Igor

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

fbeekvel — Thu, 10 Oct 2019 14:33:32 GMT

I just upgraded one of our Report Servers to the september release and got the same "child process (RSPortal) died" error.

Even uninstalling and reinstalling results in the same error. Wondering what the problem could be. The logs aren't really helpful.

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

rpatkar — Thu, 10 Oct 2019 18:43:43 GMT

We have not been able to repro the issue yet in the team.

Can you please share following details -

1. OS used

2. SQL version used

3. .Net Fx version available on machine

I understand there is not much information in the portal process log. Do you have any useful information in the ReportingServicesService log file?

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

Anonymous — Fri, 11 Oct 2019 06:21:21 GMT

Hi rpatkar,

Thank you very much for looking into the problem.

Here are some information from the ReportingServicesService log when using the verbose log mode of Power BI Report Server. The log file does not contain any error messages, only INFO messages. I did not find any useful infos in the file regarding our problem.

########################

<Header>
<Product>Report Server Version 2018.0150.1102.597 ((BI_Server_Main).190924-2255)</Product>
<Locale>German (Germany)</Locale>
<TimeZone>W. Europe Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft Power BI Report Server\PBIRS\Logfiles\ReportingServicesService_2019_10_10_00_07_07.log</Path>
<SystemName>BI_WIN2016_DEV</SystemName>
<OSName>Microsoft Windows NT 6.2.9200</OSName>
<OSVersion>6.2.9200</OSVersion>
<ProcessID>4504</ProcessID>
<Virtualization>Hypervisor</Virtualization>
</Header>

########################

We are using this SQL Server 2016 version:

########################

Microsoft SQL Server 2016 (SP1-CU8) (KB4077064) - 13.0.4474.0 (X64) Feb 24 2018 13:53:17 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)

########################

The RSHostingService Log contains only this information (child process died)

########################

########################

There are different .Net versions installed on the machine. I found v3.0.30729.4926, v3.5.30729.4926 and v4.0. The .Net Version 4.0 has version number 4.6.01586

Do you need any further information?

Kind regards

Patrick Wolf

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

All41S — Fri, 11 Oct 2019 08:56:31 GMT

Hi All,

try this - maybe it helps you - for me it fixed the issue.

ISSUE

After upgrading to the latest release of PBI RS, from May 2019 to September 2019, the Web Portal address is returning an HTTP 503 error

CAUSE/Analysis

Our latest’s release of Power BI Report server (September 2019) uses a more recent .NET Framework requirements and we advise a minimum of version 4.7

Action Plan

Please upgrade the .NET Framework to an 4.7 or newer version (.NET Framework Runtime)

https://dotnet.microsoft.com/download

Restart the Server
Check if the PBI Report Server is now accessible to the Web Portal

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

Anonymous — Fri, 11 Oct 2019 11:20:18 GMT

Awesome, that worked for me. Installed .Net 4.8 on the server and now the 503 error is gone.

Thanks!!!

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

fbeekvel — Fri, 11 Oct 2019 12:54:51 GMT

Yes! Updating the .NET Framework did the trick. Awesome!

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

messerjc — Fri, 11 Oct 2019 19:47:35 GMT

Any chance the installer will be updated to check for this prior to installing/upgrading? We're holding off for a few weeks precisely for issues like this, and if this is now a known issue I'm sure many of us would be more comfortable proceeding once an update has been released.

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

SIA — Tue, 15 Oct 2019 08:10:46 GMT

Big thanks, that works!

Re: Getting 503 error, child process (RSPortal) died (Report Server Sept Edition 2019)

kztina — Wed, 16 Oct 2019 08:28:12 GMT

Hi all,

Installation .NET Framework 4.8 solved problems for Power BI Report Server September 2019.

Thanks a lot!