User Limit reached for Workspace

[JosueMolina]

We have a subset of Semantic Models using Direct Lake to Query data stored in our Lakehouses. The SQL Endpoints in one of our Workspaces stopped working today and we are getting the error for User Limit reached in the Workspace. 

"The requested Lakehouse operation failed. A retry of the operation may help. Additional error details: The user session limit for the workspace is 400 and has been reached. Changed database context to 'DataflowsStagingLakehouse'. Changed language setting to us_english.."

We have a Premium Capacity (not PPU). Any idea why this is? Other workspaces are working fine.

[coverturfLSH]

Hi Josue,

Were you ever able to get a solution for this? I'm running into a similar issue where it says I have 724 user sessions when I only really have 20 unique people that have access to the workspace. 

[Lars_G]

Hi,

I had the same issue with a client. At first I was affraid I had to recrate the whole workspace (as indicated in this post).

The solution was to pause and resume the Fabric Capacity! 🙂

Wait for app. one hour to let it work through.

[souldish]

Unfortunately for our Premium P1 capacity, we have to delete and recreate the capacity. This has happened twice now. Trying to go through support with this now.

[souldish]

Issue is still ongoing. When I last talked with support they mentioned it would be fixed eventually, but still annoying having to re-create my capacity whenever my 50+ datasets start failing.

[coverturfLSH]

I'm curious and I wrote this in my other thread. Are you running Python Notebooks in the workspace that you're having this error? My workspace eventually fixed itself and we never did have an actual answer to what caused the issue. However, I have a hunch it's because I was running multiple Notebooks in the workspace and each time I ran one it started a new "session" that counted against my "user/session count". Eventually the sessions would be terminated over time (like 72 hours?) and the workspace eventually started working again. I haven't ran any notebooks since and haven't had any issues either.  

[souldish]

I do have notebooks running every hour in the workspace so I imagine this is what's causing the issue. 

[coverturfLSH]

Try adding this to the last step in your notebook and see if it makes a difference. I gave up on the notebooks but I came across this in my research. 

spark.stop()

[JosueMolina]

Hi @coverturfLSH 

Sadly, no. We had to recreate the whole workspace and reassess our inner process to safeguard against this happening again. Microsoft Support could not provide a solution at all. The Endpoints "fixed" themselves a week after and we have not seen the error again, but we moved on to another architecture for Data Loading and Processing instead. 

Where are you seeing the 724 User Sessions?

[coverturfLSH]

I started another thread because I'm having issues with my data warehouse (https://community.fabric.microsoft.com/t5/Data-Warehouse/Data-Warehouse-is-inaccessible-overnight/m-...)

Half of my dataflows failed and the error message was "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." 

I was wondering if they were related because theoretically, if the workspace is at "max users" then it wouldn't authenticate any more. But there's no shot that there's actually 724 users with active sessions in my workspace. I was hoping that you would say Microsoft was able to terminate all of the sessions. 

Receating the workspace seems to be a common suggested solution by Microsofft... I'd probably spend an entire week rebuilding it, but that may be the path I have to head down. 😞

[JosueMolina]

What we found worked as a temporary measure is creating a Lakehouse in a new area and creating Shortcuts to all tables in the unusable Warehouse / Lakehouse. Data is still there, it's just authentication that fails, so using shortcuts will make so the authentication happens at the other workspace / Lakehouse.  This can help temporarily. 

[coverturfLSH]

That's a great solution, will try!

[JosueMolina]

If you have Datasets connected to the previous Warehouse, you can do a rebind of the dataset to the new lakehouse. There's an API for that as Update DataSource.

[lbendlin]

That is highly unusual, and I am not aware of such a limit. Since you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi

[JosueMolina]

I've been meaning to avoid that. Have had terrible experience with Fabric items and Microsoft Support. Resolution Time has been over 1 month, sometimes 2 and this is a very critical item.

Appreciate your help, in any case.

[lbendlin]

As painful as it may be, it is the only way to get results. Eventually.