I have a Node app that I need to run in Azure Devops Pipelines - it needs to connect to SQL Server (on a VM, also in Azure). It uses 'msnodesqlv8' to talk to SQL Server.
The connection string looks like:
Server=dns.name.here,1433;Database=mydb;Driver={SQL Server Native Client 11.0};Trusted_Connection=Yes;APP=Extraction in DevOps;
Everything runs fine locally (obviously!) but the app fails when built and run in Pipelines with the following error:
Error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
The VM image is 'windows-latest' which I would have thought would include the necessary bits to talk to a SQL Server.
Would appreciate any pointers.
Thanks,
Jeff
You can check this with a simple powershell Get-OdbcDriver.
Just run this as a step in ADO pipeline or release.
ODBC Driver 17 for SQL Server (32-bit & 64-bit) is available on windows-latest agents (as of writing, windows-2019 is the latest)
Related
I'm attempting to follow the guide here which shows how to link an azure cosmos-db as a linked server via ODBC. I have created the ODBC links to the remote cosmos-db in both x64 and x86 flavours. These appear to connect without issue when checking from within the ODBC Admin console and I can even see the data when setting up a schema, however I am unable to create a working linked server as I get the following error when testing the connection ..
"[microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
I Believe this is maybe because I have SQL Express installed and the "Providers" folder is missing from the "Linked Server" folder. I am therefore assuming that I do not have the necessary providers installed on the SQL Server Instance running locally.
I have attempted to install both the OLE DB Driver and the ODBC Driver, however these have not helped.
I have an IIS web application which connects to a SQL Server like this:
set objConn = Server.CreateObject("ADODB.Connection")
objConn.Open("DRIVER={SQL Server};SERVER=servername;DATABASE=dbname;UID=username;PASSWORD=pwd)
Recently I started getting the following error:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error
When I asked my server admin what this meant, he said that they had recently removed TLS 1.0 from the IIS server my web application is mounted on. He made sure the new SQL ODBC 13 drivers were installed on the web server, but it did not help.
Although the web app has never had a DSN before, we created one for it using the ODBC 13 driver. When I tried connecting like this:
objConn.Open "DSNname"
I got the following error:
[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
I looked up ConnectionStrings.com to see if there were a way of specifying a different driver. I tried this:
objConn.Open("DRIVER={SQL Server Native Client 13.0};SERVER=servername;DATABASE=dbname;UID=username;PASSWORD=pwd)
And this is the error message that was produced:
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Don't know what else to do. Any ideas?
We had to update 3 servers that are running several Classic ASP websites. The main reason was we need to implement Twillio API SMS messaging wich required TLS 1.0 and TLS 1.1 to be disabled/removed.
It took several days and we had the websites go up and down through the process.
I wrote a blog post to document the process for other team members. I hope it helps.
https://dhali.com/programming/tls-1-2-with-classic-asp/
Here are the outlined steps:
https://www.ssllabs.com/ssltest to get the current TLS Configuration
Using IISCrypto Tool we updated the Registry Files on the server
Ran https://www.ssllabs.com/ssltest to prove TLS 1.0 and 1.1 removed
Update ODBC to the latest ver supports TLS 1.2 [Microsoft® ODBC Driver 13.1 for SQL Server]
Update the connection string to use the current ODBC SQL 13 driver
The specified DSN contains an architecture mismatch between the Driver and Application
You can create either a 32bit DSN or a 64bit DSN. You need to create one matching the bitness of your program. Probably 32-bit.
I am trying to obtain access to SQL Server Native Client OLE DB provider using :
hr = CoCreateInstance(CLSID_SQLNCLI11, NULL, CLSCTX_INPROC_SERVER, IID_IDBInitialize,
(void **) &PIDBInitialize);
and this fails with 80040154 error.
I am using sqlserver 2012 and everything worked perfectly fine as long as my application was running on the same machine as sql server was installed but now that the app is deployed in a different environment in which the app runs on a separate server than the server which has the database and sql server I am failing with this error even though the sql server version on the target server is same as mine.
Any ideas why would this behave in such way?
I appriciate your response.
Thats REGDB_E_CLASSNOTREG so CLSID_SQLNCLI11 is not available, download and install the redistributable package for the Native Client (Matching the bitness of your application).
Download.
I have installed Bitnami DreamFactory WAMP Stack on windows
server 2008 R2. I am unable to connect to a MS SQL DB through a service
in Dream Factory. The error message I get is “Failed to launch service
“servicename”: CDbConnection failed to open the DB connection”
I have tried everything that is mentioned over here: http://community.dreamfactory.com/t/connecting-to-ms-sql-server/163
Eagerly awaiting help.
Native ODBC Driver 11 for SQL Server must be installed for the PHP extensions to connect MS SQL DB.
I recommend referring to the DreamFactory documentation for all drivers and modules necessary in Windows for SQL Server connections. Depending on your environment, you may need to install more than just the ODBC Driver 11. Bitnami cannot package and distribute the Microsoft drivers.
I'm building a NodeJS app on my Mac and I need to connect to a MSSQL database.
Using the node module mssql, I'm able to connect to the server. But authentication fails because the database server requires the use of Windows Authorization or 'trustedConnection'. If I could use the Microsoft Driver for Node.js for SQL Server with mssql, I could provide a true value for 'options.trustedConnection', but that driver is Windows only.
Is there any way to do what I'm attempting? I don't see a way with the other drivers/node modules (tedious, tds, etc) to provide a connection string that would set trustedConnection to true or use Windows Authentication.
I just successfully connected to the SQL Server from Ubuntu 14.04.
I use FreeTDS as the driver, and unxiODBC as the driver manager, node odbc as the Node.js module to connect. I think this might be used on OSX as well.
More information can see this link. I blog it, and hope can save someone else's time.
But I need to do more research because I want to use this node module mssql to connect. mssql uses tds or tedious as drivers.