Azure Cosmos DB for MongoDB: Error 261 (TooManyLogicalSessions) During Initial List Collections Call

Felix 0 Reputation points
2026-09-11T03:40:08.3433333+00:00

Problem description

I am encountering error 261, labeled as 'TooManyLogicalSessions', when attempting to connect to my Azure Cosmos DB for MongoDB (vCore) resource. This issue occurs during the first call to 'list collections' from a .NET Core application using SDK version 10.x.x. I expected to access the database for development purposes, but the error appears immediately on the initial list collections attempt. The problem started around 2026-09-11T03:04:26Z. I have not observed any open connections at that time and did not find specific guidance for error 261 in the available self-help materials.

Environment

Service: Azure Cosmos DB for MongoDB (vCore); Client: .NET Core application; SDK version: 10.x.x; Operation: listing collections; No specific region, tier/SKU, or resource names provided.

What I've already tried

I have not tried any troubleshooting steps yet.

Current status

I am seeking guidance on resolving the error 261 during the initial list collections call, understanding whether this is related to session limits or configuration issues, and how to mitigate or prevent this error in my development environment. However, I suspect it is a bug in the database.

Azure Cosmos DB
Azure Cosmos DB

An Azure NoSQL database service for app development.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.