Forum Discussion
Pyodbc Connect to Warehouse Endpoint timing out
- 1 year ago
Hey Anonymous ,
Well, another classic example of tunnel vision due to missleading Error Messages on my end.
After some configuration changes to the KeyVaults I noticed that the Secrets were outdated.
Updated the Secrets... guess what... worked.
Would've been nice if i got an error saying "invalid credentials" or something instead of "login timeout" but whatever.
Issue is fixed and as always, was down to a basic configuration issue.
TLDR: never trust the error message and always check your credentials first.
Thanks anyway for the support!
Regards,
Tim
Hey Anonymous ,
There is environment configuration for all workspaces but that is only for spark environment variables like Datetime conversion and so on and not specifically to SQL or Warehouses.
Capacity is only in a single location. I have multiple tenants in the same geo Region (Germany West in this case) and in one it works in the other it doesnt. So i'd say it's not a geo issue.
The resources are also in the same workspace.
Im using a notebook to access a warehouse in the same workspace for inserting Values to a Table using pyspark. Lakehouse is no option due to the need to Pipeline Integration for STPs and Lookups - at least i have iterated that a few times and there was always an issue with using a lakehouse instead.
However good points. Yet i cannot really get my head around what might cause it. Will test if i can actually connect using pyodbc when i run a local python script.
If you have any other points feel free to add them. I will open a MS Ticket at some point if it's not fixed but can't right now due to my difficult availability so i won't be able to collaborate probably.
Edit: I have tried running it from a new workspace with a Trial Capacity (against the same Warehouse) and that also Fails. Running it locally (VS Code) via pyodbc works without any issues. Same code, just local python file.
Thanks,
Tim
HI Timal,
As your said, If they are work on the same data region but one work the other not.
Have you enabled allow list on the azure service principal usage or any different setting on the internal network policy setting or firewalls between these scenarios?
Regards,
Xiaoxin Sheng
- Timal1 year ago
Helper I
Hey Anonymous ,
Well, another classic example of tunnel vision due to missleading Error Messages on my end.
After some configuration changes to the KeyVaults I noticed that the Secrets were outdated.
Updated the Secrets... guess what... worked.
Would've been nice if i got an error saying "invalid credentials" or something instead of "login timeout" but whatever.
Issue is fixed and as always, was down to a basic configuration issue.
TLDR: never trust the error message and always check your credentials first.
Thanks anyway for the support!
Regards,
Tim