Skip to main content
A
Aman2024
Ground Control | Tier 1
September 24, 2024
Solved

snowflake - Could not Connect to Database. Error number: 80004005 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

  • September 24, 2024
  • 2 replies
  • 237 views

Hi All,

am trying to connect snowflake DB using connect 
its throwing error:

Could not Connect to Database. Error number: 80004005 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
am using the below connection string:
Driver={SnowflakeDSIIDriver};Server=wpzmac-ll0952.snowflakecomputing.com;Database=******;uid=******;pwd=*****;
and i configured DSN in ODBC DATA Sources (64-bit)
 

can anyone help me to resolve the issue 

thanks

    This topic has been closed for replies.
    Best answer by Tamil Arasu10

    Hi ​@Aman2024 ,

     

    In Automation Anywhere A360, when using the Connect action:

    • Ensure you are using the 64-bit version of the ODBC driver.
    • If you're using a DSN, make sure the bot runner has access to it.
    • If you're using a DSN-less connection, double-check the driver name and parameters
    • Try connecting using a simple script (e.g., in Python or a UDL file) to isolate whether the issue is with the connection string or Automation Anywhere

    2 replies

    CaptainPathfinder
    CaptainPathfinder
    Community AI Agent
    July 15, 2025

    That’s an interesting question, Aman2024 !

    I think the following community members may be able to help 

    @Zaid Chougle 

    @Tamil Arasu10 

    @Sridhar Yadlapalli 

    @Ashwin A.K 

    @Padmakumar 

    I'm your friendly neighbourhood AI Agent! (it/they). I try my best to match you with the right questions - but in case I miss, please feel free to let me know!
    Tamil Arasu10
    Most Valuable Pathfinder
    Tamil Arasu10Most Valuable PathfinderAnswer
    Most Valuable Pathfinder
    July 15, 2025

    Hi ​@Aman2024 ,

     

    In Automation Anywhere A360, when using the Connect action:

    • Ensure you are using the 64-bit version of the ODBC driver.
    • If you're using a DSN, make sure the bot runner has access to it.
    • If you're using a DSN-less connection, double-check the driver name and parameters
    • Try connecting using a simple script (e.g., in Python or a UDL file) to isolate whether the issue is with the connection string or Automation Anywhere
    _Tamil_
    Terms & ConditionsAccessibility statement