Error HYT00

[Pupic]

Hello

I have a python notebook in a Fabric workspace that contains also a warehouse and runs on a F8 Fabric Capacity.

The notebook has different cells that use T-SQL to drop and recreate tables in the warehouse, one cell for each table.

This notebook has been working correctly for about 6 month now. Yesterday, when executing I received this error:

I saw this post https://community.fabric.microsoft.com/t5/Data-Engineering/Pyodbc-Connect-to-Warehouse-Endpoint-timi... and checked my secrets but they are still valid and expire in 2027.

I tried stopping and restarting my F8 capacity but the error is still there.

I also tried switching to the Trial Capacity and with that the notebook works without any error.

Note that I have the same setup for the production environment (notebook and warehouse in the same workspace, but different from the development one) and this notebook still works perfectly also with the F8 Capacity.

Do you have any suggestions?

Thank You

[v-karpurapud]

Hi @Pupic 

Has your issue been resolved after using the stored procedure?

[v-karpurapud]

Hi @Pupic 

We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank You.

[Pupic · Accepted solution]

Hi, the solution for us was using a Stored Procedure activity instead of the notebook one.

[v-karpurapud]

Hi @Pupic 

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @tayloramy  for sharing valuable insights.

Could you please confirm if your query has been resolved by the provided solution?If you have any more questions, please let us know and we’ll be happy to help.

Regards,

Microsoft Fabric Community Support Team

[tayloramy]

Okay, that is some funky behaviour. I recommend opening a ticket and seeing what the support engineers say. 

[tayloramy]

Hi @Pupic, 

If running it manually doesn't work then I'm at a loss. I'd suggest opening a ticket to microsoft. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[Pupic]

Hi @tayloramy,

do you have any idea on why we don't receive the error if we run the notebook after switching to the Trial Capacity?

[tayloramy]

THat's factinating.. 

Is your capacity overloaded at all? 

[Pupic]

Hi @tayloramy,

not really.

Also we turn the capacity off every day at 6 PM and back on at 8.30 AM the next day so anything that's pending should terminate.

[tayloramy]

Hi @Pupic, 

Interesting, that should be working to my knowledge. 

I just tested this in my environment and it works as expected. How are you running this notebook? Manually or through a pipeline? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[Pupic]

Hi @tayloramy,

that's exactly why we don't understant why it's stopped working. 

It is usually executed by a pipeline but we've been testing it manually since it gave the error yesterday.

[tayloramy]

Hi @Pupic, 

Okay the actual error here is a login timeout. 

Are you able to access the warehouse diretly not from the notebook and run queries against it? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[Pupic]

Hi @tayloramy,

yes I can access the warehouse from fabric and also from SQL Server Management Studio and run queries.

[tayloramy]

Hi @Pupic, 

Can you post your notebook? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[Pupic]

Hi @tayloramy,

it's a simple Python notebook with a series of T-SQL cells like this one, one for each table that needs to be dropped and recreated. 

Mind you that this is the development environment, in my production environment I have a copy of this notebook that writes on the prod warehouse and that one is still working properly.

[tayloramy]

Hi @Pupic, 

Can you post a screenshot of the error in a higher resolution so it is not blury and we can read it? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[Pupic]

Hi @tayloramy,

I have updated the picture, thank you.