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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
alexchoc
Regular Visitor

An error occurred while loading the model. Failed to open the MSOLAP connection

Hi,
We have an ScaleOUT deployment balanced by Citrix.
After start PowerBI windows service works fine for about 2-4 hours.
For different reports different users receive error:
"An unexpected error occurred. Please try again later.
Please try again later or contact support. If you contact support, please provide these details.
We couldn't connect to the Analysis Services server. Make sure you've entered the connection string correctly.:
Request ID: 78b76716-b0f4-2ef2-92b6-59865bf41959
Time: Tue Feb 22
Service version: /powerbi/libs"

In PowerBI log for that error:
"
Failure in conceptualschema catalogObjectId=46d80967-430e-4f41-a5fd-d965ce64f404| RequestID = 78b76716-b0f4-2ef2-92b6-59865bf41959 ClientSessionID = 7b475ef1-f3fa-3977-fa30-6ad9f34f4064 Microsoft.PowerBI.ReportingServicesHost.CannotRetrieveModelException: An error occurred while loading the model. Verify that the connection information is correct and that you have permissions to access the data source. ---> Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException: Failed to open the MSOLAP connection. ---> MsolapWrapper.MsolapWrapperException: Could not initialize connection
at MsolapWrapper.Utils.ThrowErrorIfHrFailed(Int32 hr, String message)
at MsolapWrapper.Connection.Open()
at Microsoft.PowerBI.DataExtension.Msolap.Connection.OpenImpl()
--- End of inner exception stack trace ---
at Microsoft.PowerBI.DataExtension.Msolap.Connection.OpenImpl()
at Microsoft.PowerBI.DataExtension.Contracts.Utilities.RunSynchronously(Action action)
--- 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 System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.PowerBI.ReportServer.ExploreHost.WindowsUserIdentityConnectionImpersonator.<ExecuteInContextAsync>d__4.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.ReportingServicesHost.PoolableConnectionWrapper.<OpenAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.ReportingServicesHost.Utils.TaskExtensions.WaitAndUnwrapException(Task task)
at Microsoft.PowerBI.ReportingServicesHost.ModelMetadataProvider.ExecuteSchemaCommand[T](ExploreHostDataSourceInfo dataSourceInfo, IDbConnectionPool connectionPool, IConnectionFactory connectionFactory, IConnectionUserImpersonator connectionUserImpersonator, QueryExecutionOptionsBase queryExecutionOptions, ITelemetryService telemetryService, Func`2 action, String failTelemetryMessage, ServiceErrorStatusCode statusCode, ExploreBaseEvent exploreEvent)
--- End of inner exception stack trace ---
at Microsoft.PowerBI.ReportingServicesHost.ModelMetadataProvider.ExecuteSchemaCommand[T](ExploreHostDataSourceInfo dataSourceInfo, IDbConnectionPool connectionPool, IConnectionFactory connectionFactory, IConnectionUserImpersonator connectionUserImpersonator, QueryExecutionOptionsBase queryExecutionOptions, ITelemetryService telemetryService, Func`2 action, String failTelemetryMessage, ServiceErrorStatusCode statusCode, ExploreBaseEvent exploreEvent)
at Microsoft.PowerBI.ReportingServicesHost.ModelMetadataProvider.<>c__DisplayClass10_1.<GetModelMetadata>b__1(ExploreBaseEvent timedEvent)
at Microsoft.PowerBI.ReportingServicesHost.ExploreTelemetryService.<>c__DisplayClass4_0`1.<RunInActivity>b__0(ExploreBaseEvent activity)
at Microsoft.PowerBI.ReportingServicesHost.ExploreTelemetryService.RunInActivity(String activityName, Action`1 action)
at Microsoft.PowerBI.ReportingServicesHost.ExploreTelemetryService.RunInActivity[T](String activityName, Func`2 action)
at Microsoft.PowerBI.ReportingServicesHost.ModelMetadataProvider.GetModelMetadata(ModelMetadataRequest request)
at Microsoft.PowerBI.ReportServer.ExploreHost.RSPowerViewHandler.GetModelCSDL(String id, String maxModelMetadataVersion, IASConnectionInfo& asConnectionInfo)
at Microsoft.PowerBI.ReportServer.ExploreHost.RSPowerViewHandler.<>c__DisplayClass41_0.<GetOrAddModel>b__0()
at System.Lazy`1.CreateValue()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Lazy`1.get_Value()
at Microsoft.PowerBI.ReportServer.ExploreHost.RSModelCache.GetOrAddModel(ModelKey key, Func`1 modelInfoFunc)
at Microsoft.PowerBI.ReportServer.ExploreHost.RSPowerViewHandler.EnsureSession(String modelId)
at Microsoft.PowerBI.ExploreHost.ExploreClientHandlerBaseFlow.<RunAsync>b__9_0()
at System.Threading.Tasks.Task.Execute()
--- 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.ExploreHost.ExploreClientHandlerBaseFlow.<RunAsync>d__9.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.ExploreHost.ExploreClient.<GetClientConceptualSchemaAsync>d__13.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.ExploreHost.RSExploreHost.<GetConceptualSchemaAsync>d__4.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.<GetConceptualSchemaAsync>d__25.MoveNext()
"
In executionlog3 for that requestID i see:
status InstanceName ItemPath UserName ExecutionId RequestType Format Parameters ItemAction TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount AdditionalInfo
rsInternalError PBI1\PBIRS /rep/rep/report domain\username 78b76716-b0f4-2ef2-92b6-59865bf41959 Interactive PBIX NULL ConceptualSchema 2024-02-22 14:32:32.460 2024-02-22 14:32:32.600 0 0 0 Cache rsInternalError 0 0 NULL

That model is inside internal PBI SSAS.
I receive that error few times a day.
Could any one say what have i to check?
We have last update for PBI server. I tried to change ModelExpirationMinutes from 60 to 120 and tried change to 5. At the moment we have 60
Yesterday we changed session persistence on citrix and after that faces that we have that error message rather rare. But issue is not fully solved by that change.
Previous week i tried to restart PBI service every hour by task scheduler and zero such errors faced.

3 REPLIES 3
josef78
Memorable Member
Memorable Member

If I understand, you have scale-out deployment with Citrix NLB?

Not sure, but issue may be in weak NLB persistence (PBI RS (with import mode reports) is not good object for loadbalancing. Check ExecutioLog3 sequence of row for same report request, if actions ASModelStream, ConceptualSchema and QueryData are on same Instance.

Another issue may be in Refresh processing... Are models refreshed during day? Running refresh on dedicated instance of PBIRS? 

Also try turn off NLB, to check if problem is in NLB. For example, in my enviroment, we have also scale-out deployment on three servers, one is dedicated to refresh data, and two as frontend servers, but without loadbalancing, only for failover, or routing based on fixed URL (for specific reports).

lbendlin
Super User
Super User

surely you have raised a ticket for that?  Although I would suspect that your scaleout setup is outside the design envelope for Report Server.

Could you clear: why is scaleout outside? We have usual two servers installation with same settings on both. 

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

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

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.