Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SNOW-1499157: Error: Snowflake Internal Error: Unable to connect. One or more errors occurred. SqlState: 08006, VendorCode: 270001, QueryId: #980

Closed
gaj-ad opened this issue Jun 22, 2024 · 1 comment
Assignees
Labels
invalid status-triage_done Initial triage done, will be further handled by the driver team

Comments

@gaj-ad
Copy link

gaj-ad commented Jun 22, 2024

Please answer these questions before submitting your issue.
In order to accurately debug the issue this information is required. Thanks!

  1. What version of .NET driver are you using?
    2.2.0

  2. What operating system and processor architecture are you using?
    Windows server 2019

  3. What version of .NET framework are you using?
    .net framework 4.8

  4. What did you do?
    Started seeing this error on the server since few days, was working before -
    Error: Snowflake Internal Error: Unable to connect. One or more errors occurred. SqlState: 08006, VendorCode: 270001, QueryId:
    at Snowflake.Data.Core.Session.SessionPool.NewSession(String connectionString, SecureString password)
    at Snowflake.Data.Core.Session.SessionPool.GetSession(String connStr, SecureString password)
    at Snowflake.Data.Client.SnowflakeDbConnection.Open()

  5. What did you expect to see?
    No error on Snowflake connection.
    What should have happened and what happened instead?

  6. Can you set logging to DEBUG and collect the logs?
    snowflake_dotnet4-Arw - Copy.log

    https://community.snowflake.com/s/article/How-to-generate-log-file-on-Snowflake-connectors

    There is an example in READMD.md file showing you how to enable logging.

  7. What is your Snowflake account identifier, if any? (Optional)

@gaj-ad gaj-ad added the bug label Jun 22, 2024
@github-actions github-actions bot changed the title Error: Snowflake Internal Error: Unable to connect. One or more errors occurred. SqlState: 08006, VendorCode: 270001, QueryId: SNOW-1499157: Error: Snowflake Internal Error: Unable to connect. One or more errors occurred. SqlState: 08006, VendorCode: 270001, QueryId: Jun 22, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka self-assigned this Jun 24, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka added the status-triage Issue is under initial triage label Jun 24, 2024
@sfc-gh-dszmolka
Copy link
Contributor

hi - thanks for sharing the logs. they suggest the client driver is not able to connect to the Snowflake account due to the login request not getting a response and eventually timing out.

this behaviour is very rarely associated with the driver itself, especially if the same workflow was working with the same driver earlier, and suddenly it stopped working.
this suggests a change in the underlying network configuration which now apparently prevents the client from reaching the server.

you can use https://community.snowflake.com/s/article/Snowflake-Client-Connectivity-Troubleshooting for generic connectivity troubleshooting guide, or if you prefer to work with someone from Snowflake on that, please open a Support ticket with us - this repository focuses on the .NET driver and issues/requests associated with the .NET driver. This problem you're seeing is not related to that.

for now I'm closing this Issue as it is not related to the .NET driver but if you think it is afterwards, please do comment and attach the relevant evidence and I can continue looking.

@sfc-gh-dszmolka sfc-gh-dszmolka added invalid status-triage_done Initial triage done, will be further handled by the driver team and removed bug status-triage Issue is under initial triage labels Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Development

No branches or pull requests

2 participants