Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
josef78
Memorable Member
Memorable Member

Issue: Power BI RS May 2023 release - Child Process [Portal] Died

Hello all,

After upgrade to Power BI RS May 2023 (15.0.1112.48) on production enviroment and load, I have numerous issues with RSPortal.exe process.

Power BI portal sometimes drops some requests and is unavailable for a while in the day, and it gets worse over time (until I restart the entire service). 

 

In RSHostingService log I found many (every few minutes under load) warning like this:

Child Process [Portal] Died. Check the log for further information

 Sometimes followed with message:

Immediate restart of process Portal

Or after some delay (when service is unavaliable) followed with message like:

Throttled restart of process by 670 761,67ms: Portal

 

In RSPortal log I not found nothing interesting, except sometimes repeating message:

Received a request with an unmatched or no authentication scheme.

 

I not found any of these messages in log before May 2023 version. I think this can be a critical problem on large environments.


Please anyone, do you have any similar problems?

Thanks for the help.

 

2 ACCEPTED SOLUTIONS
v-alipat
Employee
Employee

Hi all! 

@josef78 , @YusufCakar 

 

Thank you for reporting the problem. 

We are looking into it now, and here is a possible workaround for your situation: 

 

Navigate to RSPortal.exe.config file (Typically located at "C:\Program Files\Microsoft Power BI Report Server\PBIRS\Portal") 

Find there an element <system.diagnostics>, and remove it 
(Remove this piece: )

  <system.diagnostics>
    <trace autoflush="true" />
    <sources>
      <source name="System.Net.HttpListener">
        <listeners>
          <add name="System.Net.HttpListener" />
        </listeners>
      </source>
    </sources>
    <sharedListeners>
      <add name="System.Net.HttpListener" type="Microsoft.BIServer.HostingEnvironment.HttpListenerLogger, Microsoft.BIServer.HostingEnvironment" />
    </sharedListeners>
    <switches>
      <add name="System.Net.HttpListener" value="Verbose" />
    </switches>
  </system.diagnostics>

 

Could you please try this out, and let us know if this actually helps? 

Looking forward to hear back from you, while we continue our investigation. 

 

Thanks,

Alexandra 

View solution in original post

Hello all! 

 

The fix for this problem will be included in the next release of PBIRS. 

It is still not determined if there will be a QFE to May release, or if it will be a part of September release. 

 

Thanks,

Alexandra 

View solution in original post

28 REPLIES 28

Hello @v-alipat ,

I can confirm, that this workaround is working great. There no mentioned errors and no outages.

 

Please what are next steps? New fixed version will be released?

 

Thank you much,

Josef

Hello all! 

 

The fix for this problem will be included in the next release of PBIRS. 

It is still not determined if there will be a QFE to May release, or if it will be a part of September release. 

 

Thanks,

Alexandra 

YusufCakar
Frequent Visitor

Hello everyone,

I am getting the same error in Power BI Report Server may 2023 update.

Can you support?

Enjoy your work.

Hello

The official ticket is the right way to go.

 

But any more information about this problem or workaround and other cases where this problem occurs can help or increase the priority.

I don't know of any solution at this time, other than rolling back (almost impossible) or restarting PBIRS periodically.


@YusufCakar wrote:

Hello everyone,

I am getting the same error in Power BI Report Server may 2023 update.

Can you support?

Enjoy your work.


As mentioned above. I think an official support ticket is the best approach here. This is not expected behaviour.

Hello,

Clean install on new server. But the problem was not solved.

No user access this error keeps repeating.

It's like a vicious circle.

Service Unavailable when not restarted
We are getting HTTP Error 503. The service is unavailable.

logs:

023-06-20 16:21:30.1468|INFO|8|Catalog max connection pool size: 100
...
2023-06-20 16:22:03.0907|WARN|25|Child Process [Portal] Died. Check the log for further information
2023-06-20 16:22:03.1063|INFO|25|Immediate restart of process Portal
2023-06-20 16:22:03.1063|INFO|25|Launching Process : Portal
2023-06-20 16:22:03.1063|INFO|25|Starting Process: C:\Program Files\Microsoft Power BI Report Server\PBIRS\Portal\RSPortal.exe
2023-06-20 16:22:10.5279|INFO|7|Catalog max connection pool size: 100
2023-06-20 16:22:20.5902|INFO|18|Catalog max connection pool size: 100
...
2023-06-20 16:23:48.7633|WARN|32|Child Process [Portal] Died. Check the log for further information
2023-06-20 16:23:48.7633|INFO|32|Immediate restart of process Portal
2023-06-20 16:23:48.7789|INFO|32|Launching Process : Portal
2023-06-20 16:23:48.7789|INFO|32|Starting Process: C:\Program Files\Microsoft Power BI Report Server\PBIRS\Portal\RSPortal.exe
...
2023-06-20 16:24:52.0314|INFO|18|Catalog max connection pool size: 100
2023-06-20 16:25:02.1734|INFO|7|Catalog max connection pool size: 100
2023-06-20 16:25:12.3299|INFO|18|Catalog max connection pool size: 100
2023-06-20 16:25:22.4863|INFO|7|Catalog max connection pool size: 100
2023-06-20 16:25:32.5802|INFO|18|Catalog max connection pool size: 100
...
Child Process [Portal] Died. Check the log for further information
...

d_gosbell
Super User
Super User

@josef78 - I have not seen any other reports of an issue like this on the forum. It is probably best to raise a support ticket, it sounds like it might be a load related issue and if the logs do not hold any clues it might need a more focussed investigation

Hello,

Thank you, yes, I will rise the ticket. So far, I've tried to investigate this issue to see if it's an infrastructure issue, or a specific workload, or an application error.

I think it's an app bug. It has affected both of my environments, but is dependent on the load and how long the service has been running (since the last reboot).
On lightly loaded environments (my test) this is not a critical problem (several connection failures per week). On very busy enviroments, this is a critical problem (random connection failures and restarts of this process at any time, and massive outages of availability after several hours of heavy traffic).

Also I'm trying find any workaround, but currently only option is hard restart of PBIRS services some times per day.

 

 

Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

Power BI Carousel June 2024

Power BI Monthly Update - June 2024

Check out the June 2024 Power BI update to learn about new features.

PBI_Carousel_NL_June

Fabric Community Update - June 2024

Get the latest Fabric updates from Build 2024, key Skills Challenge voucher deadlines, top blogs, forum posts, and product ideas.

RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.