0

I am using SnowSql 1.2.5 and I receive no response, no error, absolutely nothing from it. It does not matter which command I type, even if type just "SnowSql.exe" and hit confirm, I get no response.

This is happening in an specific machine, in others with the same SnowSql version it is working properly.

OS used: Microsoft Windows 10 Enterprise (64-bit) Version (Build) 1903 (10.0.18362)

Destro
  • 41
  • 1
  • 3
  • 1
    This can happen for a few reasons, my first suspicion would be something network related - what happens if you try to run SnowCD? https://docs.snowflake.com/en/user-guide/snowcd.html – Hotchips Jun 09 '20 at 10:23

1 Answers1

0

Can you please check and confirm if you have already whitelisted the required snowflake endpoints(hosts/ports) for your Snowflake account in the network firewall etc?

You can run the below system function call in your Snowflake account to get the endpoint details specific to your Snowflake account which needs to be whitelisted.

select system$whitelist()

https://docs.snowflake.com/en/sql-reference/functions/system_whitelist.html

I hope this helps. Let us know if you still see the issue.

Md Aurangzeb
  • 51
  • 1
  • But I have other machines running SnowSql correctly in the same domain. Even for a simple SnowSql --version I get no response. I turned off my local windows firewall and still get the same behaviour. – Destro Jun 10 '20 at 12:46
  • Just to give more info, SnowSql does not hang for while, it is like hitting an emtpy command in prompt. – Destro Jun 10 '20 at 13:02
  • @Destro This behaviour is similar to what I've seen when there's a network connection issue, but it could also be a shell configuration issue. Can you please run the SnowCD tool I linked above and edit the output into your question? – Hotchips Jun 11 '20 at 03:53
  • Hello, @Hotchips. Plese check the results from SnowCD-> Performing 30 checks for 12 hosts All checks passed – Destro Jun 12 '20 at 12:38
  • @Destro When you say it is like hitting an empty command in prompt, do you mean that Snowsql immediately closes and you go back to the next line in the command prompt? It might be good if you edit the (anonymised) output (or lack thereof) that you're getting into the question. – Hotchips Jun 15 '20 at 14:48
  • @Hotchips I am sorry but I did not understand what you meant – Destro Jun 16 '20 at 10:08