Getting error when trying to access Cosmos DB analytical storage

Question

Getting error when trying to access Cosmos DB analytical storage

Julius Dietmar 60

When running query against Cosmos DB analytical storage, I am getting the following error:

Msg 15893, Level 16, State 51, Line 30

Resolving CosmosDB path has failed with error 'Cosmos DB analytical storage contains no data.'.

Completion time: 2026-05-31T21:17:15.0337245-07:00

This has been working fine previously - no changes - analytical store is still enabled on this collection.

This is the query I am running:

    SELECT COUNT(*)
    FROM OPENROWSET(PROVIDER = 'CosmosDB',

                    CONNECTION = 'Account=xxx-prod;Database=xxxhtapdb',

                    OBJECT = 'items',

                    SERVER_CREDENTIAL = 'xxx-prod'


                    

    ) as items
;

Manoj Kumar Boyini 19,590 Reputation points Microsoft External Staff Moderator

2026-06-01T15:34:03.1866667+00:00

Hi @Julius Dietmar

I kindly request you to please share the details requested in the private message for further investigation.
Manoj Kumar Boyini 19,590 Reputation points Microsoft External Staff Moderator

2026-06-03T13:01:14.95+00:00

Hi @Julius Dietmar

As you requested an RCA, I have shared the link to create an SR. Could you please create it and confirm.

Answer accepted by question author

Manoj Kumar Boyini 19,590 Microsoft External Staff Moderator

Hi @Julius Dietmar

Based on our review, the issue aligns with a transient Azure Synapse service incident that affected connectivity to Synapse workspaces and related operations through private network paths. During this period, some customers experienced connection failures, timeouts, and inability to access or query data. The issue was caused by a platform configuration change involving load balancer migration, which resulted in connectivity disruptions for affected requests. The service team mitigated the issue by rolling back the change and restoring normal traffic routing. Following mitigation, service functionality was restored and the query is now executing successfully. No customer-side configuration changes were required.

Please let us know if you have any questions or concerns.

Julius Dietmar 60 Reputation points

2026-07-03T19:05:55.56+00:00

I really appreciate your ongoing effort on tracking this down. I am glad that we found out what was going on.

1 additional answer

Your answer

Manoj Kumar Boyini 19,590 Reputation points Microsoft External Staff Moderator

2026-06-01T15:34:03.1866667+00:00

Hi @Julius Dietmar

I kindly request you to please share the details requested in the private message for further investigation.
Manoj Kumar Boyini 19,590 Reputation points Microsoft External Staff Moderator

2026-06-03T13:01:14.95+00:00

Hi @Julius Dietmar

As you requested an RCA, I have shared the link to create an SR. Could you please create it and confirm.
Julius Dietmar 60 Reputation points

2026-07-03T19:05:55.56+00:00

I really appreciate your ongoing effort on tracking this down. I am glad that we found out what was going on.

Answer 1

Hi @Julius Dietmar

We have reviewed the issue and observed that it was transient in nature. Since the issue has now been resolved and access to the Cosmos DB analytical storage is working again, no further action is required at this time.

As part of our ongoing service improvements, the engineering team is continuously enhancing automated detection and recovery mechanisms to identify similar situations earlier and minimize potential impact on incoming requests.

We sincerely apologize for any inconvenience this may have caused.

If you encounter a similar issue in the future, please feel free to reach out to us.