The user session limit for the workspace has been reached

[coverturfLSH]

We're receiving the below error on multiple workspaces. The error message started on Sunday morning and it's very unlikely we had any active users at that time let alone 724 users. My guess is that there are active sessions that aren't being terminated. Is there any way to look up active sessions in the Admin Portal and terminate them?

The common thread behind the multiple workspaces is that they all are pointing to Fabric Data Warehouse/Lakehouses in one workspace. We've never had this issue before though. 

[SemanticModelName]_WriteToDataDestination: Mashup Exception Data Source Error Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: Microsoft SQL: The user session limit for the workspace is 724 and has been reached. Changed database context to 'DataflowsStagingLakehouse'. Changed language setting to us_english. Details: Reason = DataSource.Error;DataSourceKind = Lakehouse;DataSourcePath = Lakehouse;DataSourceKind.2 = SQL;DataSourcePath.2 = [Server Address].fabric.microsoft.com;DataflowsStagingLakehouse;Message = The user session limit for the workspace is 724 and has been reached. Changed database context to 'DataflowsStagingLakehouse'. Changed language setting to us_english.;ErrorCode = -2146232060;Number = 10988;Class = 14;State = 1;Microsoft.Data.Mashup.Error.Context = User...

Ticket has been opened with Microsoft: 2410070010004117

[mohamedabohassn]

@coverturfLSH  "Could you help me if you have a solution? I'm currently facing the same issue. What should I do?"

[coverturfLSH]

Hi Mohamed,

You'll need to submit a support ticket to Microsoft and ask them "restart the capacity". You can reference my ticket (2410070010004117) to hopefully speed things along if they can reference the notes on how they resolved my situation. If you're on a "Fabric" F1-64 SKU, you can have your own powerBI administrator restart the capacity. We couldn't do it ourselves because were on a P# SKU.

[mohamedabohassn]

thanks @coverturfLSH  i already restarted the capacity and still the same issue , the support team still investigate about the problem 

[coverturfLSH]

Very odd! Please report back with your ticket number when they're able to resolve and it may help someone in the future.

[mohamedabohassn]

yeah sure , i hope they resolve it soon 

[coverturfLSH · Accepted solution]

The product team was able to apply a mitigation on the backend. Unsure of what this means exactly but it wasn't something that the first level of support could do. The "Mashup Engine (PowerBIPremium-Import)" took up 621 sessions and "Mashup Engine" took up 84 sessions. There's a theory that some dataset/semantic models never properly closed their sessions, but we're unable to pinpoint where. 

[GilbertQ]

Hi @coverturfLSH 

To be tightly honest, this sucks like a bug within the power of BI service. I would wait and see if this is still happening tomorrow, and then probably log a support ticket. The other. alternative you can do is to potentially restart the capacity or swap the capacity to a different one and see if that works.

[coverturfLSH]

Issue started on Saturday morning and has persisted all day today. So we're heading into day 4 tomorrow. I've asked to restart the capacity but there's a lot of hoops to jump through to get the product team to do it. I don't have any other options to swap the capacity. 

Unfortuantely, this is the 2nd time this has happened to me this year. Seems like there's something on the server that's preventing sessions from timing out and they're being left open.