Hi, I'm encountering a lot of errors when using that synapse workspace to query the data lake storage account (Only 5-10% of my adhoc queries have been succeeding today). These all look suspisciously like network errors e.g.: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) Database 'dataverse_xxxxxxx' on server 'xxxxx' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '{xxxxxxxxx}'. Cannot open database "dataverse_xxxxxx" requested by the login. The login failed. Finding this very strange as the connection should just be from the synapse workspace to the storage account.

Connection errors on Synapse

KEN 5

Hi,

I'm encountering a lot of errors when using that synapse workspace to query the data lake storage account (Only 5-10% of my adhoc queries have been succeeding today). These all look suspisciously like network errors e.g.:

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
Database 'dataverse_xxxxxxx' on server 'xxxxx' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '{xxxxxxxxx}'.
Cannot open database "dataverse_xxxxxx" requested by the login. The login failed.

Finding this very strange as the connection should just be from the synapse workspace to the storage account.

John Minihan 1 Reputation point

2023-03-02T15:29:53.6866667+00:00

Seemed to be fine following initial setup; then stops working apart from sporadic successes.

Strangely, in the workspace, the 'metadata' retrieval (list of Tables/Views) works fine; and the context menu works (e.g. New SQL script > Select TOP 100 rows produces the correct script).

Also, scripts in master database work...! E.g. SELECT TOP 100 * FROM information_schema.tables works in master - not in Lake database...
John Minihan 1 Reputation point

2023-03-02T15:30:20.59+00:00

Deleted as duplicated
John Minihan 1 Reputation point

2023-03-02T16:51:32.56+00:00

I've noticed that, in SSMS, the database mostly shows (In Recovery) in the database name
BhargavaGunnam-MSFT 28,106 Reputation points Microsoft Employee

2023-03-07T21:01:33.8266667+00:00

Hi John Minihan and KEN ,

It seems like the errors you encountered are related to the network between the synapse and the data lake storage.

It could be an intermittent issue too. If you are still seeing the errors, please let me know.
Steve Platz 1 Reputation point

2023-03-08T16:24:05.0466667+00:00

I also saw this issue last evening with a pipeline that executes a dataverse lake database.
Gauthier DUMONT 0 Reputation points

2023-03-14T15:06:25.4466667+00:00
Hi @BhargavaGunnam-MSFT

for information,

when I start to work on Synapse with a dataverse lake, I often have this error

Cannot open database "dataverse_xxxxxx" requested by the login. The login failed.

after a few minutes ( 5~10min), it's OK
BhargavaGunnam-MSFT 28,106 Reputation points Microsoft Employee

2023-03-14T19:09:52.9466667+00:00

Hello @Gauthier DUMONT,

Thank you.

I have reached out to my internal team about these issues. I will update this thread as soon as I hear from them.

Share via

Connection errors on Synapse