Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hello everyone,
One of our 3 Power BI Report Servers crash randomly multiple times per week.
It always throw the same error.
Find below a snippet of the log file "RSPowerBI" stored in PBIRS/LogFiles/ directory:
2020-09-03 11:28:29.2895|ERROR|15|Error getting next eventSystem.ApplicationException: Could not impersonate the user. LogonUser returned error code 8.
à Microsoft.BIServer.HostingEnvironment.ImpersonationContext..ctor(AccountCredentials accountCredentials)
à Microsoft.BIServer.HostingEnvironment.ImpersonationContext.EnterUserContext(AccountCredentials accountCredentials)
à Microsoft.BIServer.Configuration.Catalog.CatalogAccessFactory.NewConnection()
à Microsoft.BIServer.Configuration.Catalog.CatalogAccessFactory.<QueryFirstOrDefaultAsync>d__5`1.MoveNext()
I also had a look at the Windows events and there is always a .NET Runtime error thrown (sorry for the french):
Application : RSHostingService.exe
Version du Framework : v4.0.30319
Description : le processus a été arrêté en raison d'une exception non gérée.
Informations sur l'exception : System.OutOfMemoryException
à NLog.MessageTemplates.TemplateEnumerator.ParseFormat()
à NLog.MessageTemplates.TemplateEnumerator.ParseHole(NLog.MessageTemplates.CaptureType)
à NLog.MessageTemplates.TemplateEnumerator.MoveNext()
à NLog.MessageTemplates.TemplateRenderer.Render(System.String, System.IFormatProvider, System.Object[], Boolean, System.Text.StringBuilder, System.Collections.Generic.IList`1<NLog.MessageTemplates.MessageTemplateParameter> ByRef)
à NLog.Internal.LogMessageTemplateFormatter.AppendFormattedMessage(NLog.LogEventInfo, System.Text.StringBuilder)
à NLog.LogEventInfo.AppendFormattedMessage(NLog.Internal.ILogMessageFormatter, System.Text.StringBuilder)
à NLog.LayoutRenderers.MessageLayoutRenderer.Append(System.Text.StringBuilder, NLog.LogEventInfo)
à NLog.LayoutRenderers.LayoutRenderer.RenderAppendBuilder(NLog.LogEventInfo, System.Text.StringBuilder)
à NLog.Layouts.SimpleLayout.RenderAllRenderers(NLog.LogEventInfo, System.Text.StringBuilder)
à NLog.Layouts.Layout.RenderAppendBuilder(NLog.LogEventInfo, System.Text.StringBuilder, Boolean)
à NLog.Layouts.SimpleLayout.PrecalculateBuilder(NLog.LogEventInfo, System.Text.StringBuilder)
à NLog.Targets.Target.PrecalculateVolatileLayoutsWithLock(NLog.LogEventInfo)
à NLog.Targets.Wrappers.AsyncTargetWrapper.Write(NLog.Common.AsyncLogEventInfo)
à NLog.Targets.Wrappers.AsyncTargetWrapper.WriteAsyncThreadSafe(NLog.Common.AsyncLogEventInfo)
à NLog.Targets.Target.WriteAsyncLogEvent(NLog.Common.AsyncLogEventInfo)
à NLog.LoggerImpl.WriteToTargetWithFilterChain(NLog.Targets.Target, NLog.Filters.FilterResult, NLog.LogEventInfo, NLog.Common.AsyncContinuation)
à NLog.LoggerImpl.Write(System.Type, NLog.Internal.TargetWithFilterChain, NLog.LogEventInfo, NLog.LogFactory)
à Microsoft.BIServer.BIService.ManagedProcess+<ThrottledStart>d__20.MoveNext()
à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
à System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
à System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
à System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
à System.Threading.ThreadPoolWorkQueue.Dispatch()
I've been digging Google but didn't find any relevant information about those 2 errors.
We are running PBIRS January 2020 (15.0.1102.777)
The only difference with our 2 other servers is we have an HTTPS certificate configured on this one.
Everytime the server crash, we have to manually restart the PBIRS Service via the configuration manager console.
Thank you all for your input.
Solved! Go to Solution.
Hello,
Quick update:
The error message was not relevant because it was a memory error. Some DAX queries were loading the memory and made the server crash.
@Anonymous , it is showing out of the memory exception. Open this with most of the other processed closed and see does it open up. Check how much RAM and CPU power bi take up at that time.
Hi @amitchandak
Thank you for the reply.
I've checked the metrics for the last 7 days (we have this monitored):
Each of the 4 CPUs is always below 15% and the RAM is always around 16Gb used with 32Gb available.
Can you pelase clarify the following sentence, I didn't get your point:
"Open this with most of the other processed closed and see does it open up"
Thanks
@Anonymous , seems like no load.
Log an issue https://community.powerbi.com/t5/Issues/idb-p/Issues
Hello,
Quick update:
The error message was not relevant because it was a memory error. Some DAX queries were loading the memory and made the server crash.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Power BI update to learn about new features.
User | Count |
---|---|
10 | |
4 | |
4 | |
2 | |
1 |
User | Count |
---|---|
16 | |
10 | |
6 | |
5 | |
4 |