[Microsoft][ODBC Driver Manager] Data Source name not found and no default driver specified #344
-
Hi, I'm trying to benchmakr MSSQL running in Windows instance in the GCP platofmr from Hammer DB. When I try to build the schema I'm getting the below error: Error in Virtual User 1: Connection to DRIVER=ODBC Driver 17 for SQL server; SERVER=x.x.x.x; UID=sqladmin; PWD=XXX could not be established : [Microsoft][ODBC Driver Manager] Data Source name not found and no default driver specified. When I checked the "librarycheck" command from the hammerdbcli it is showing success for the MS SQL but still I'm unable to build the schema. I even confirmed the port 1433 is opened between SQL server and the Hammer DB. Kindly do share your thoughts if you come across this issue. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
The error is shown here:
Here is an example, We run librarycheck and the library is found
We will also run the ODBC data sources tool and check what drivers we have: Now lets try and use a driver that we don't have installed eg ODBC Driver 22 for SQL Server ... We now get the same error that you get:
Verify you have the correct drivers installed that you want to use. |
Beta Was this translation helpful? Give feedback.
-
In the MSSQL server I have already added the ODBC Driver for SQL 17 in both "System Data Source and User data source". Still same error. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your support in isolating this issue. After installing the correct version of ODBC drivers in both MS SQL and Hammer DB server, I'm able to build schema. |
Beta Was this translation helpful? Give feedback.
The error is shown here:
[Microsoft][ODBC Driver Manager] Data Source name not found and no default driver specified.
Here is an example, We run librarycheck and the library is found
We will also run the ODBC data sources tool and check what drivers we have:
Now lets try and use a driver that we don't have installed eg ODBC Driver 22 for SQL Server ...
We now get the same error that you get: