I have successfully created several pass-through queries to an external database using ODBC and each of these queries successfully open individually. However, when I attempt to open more than one pass-through query, I get this message: ODBC--connection to '[XXXX]' failed.
I was using MS Access 2016 and have only just migrated to Access 365 which is when the error arose.
Related
I have a report that is connecting to a new server.
When I run the report in Visual Studio, it runs fine but when I deploy the report, the new data source is getting an error:
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or
was not accessible. Verify that the instance name is correct and that
SQL Server is configured to allow remote connections. (provider: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)
The Type is MS SQL Server and the Connection String is basic (Data Source=;Initial Catalog=). When I hit Test, it takes about a minute to come up with the error. I also get the error whether using stored credentials or Windows Integrated.
I have recreated the data source by hand without any difference.
I have went through the Microsoft troubleshooting without success. I have numerous other similar data sources but have never had this issue.
MS Docs: Troubleshoot connecting to the SQL Server Database Engine
Don't know what else to try. Any suggestions to fix this?
SSRS 2015 - SQL Server 13.0.5820.21
We have a user that is trying to run an Access query on a new laptop and it's failing with an ODBC error. They obviously don't have the required odbc definition(s) on the new laptop.
How can I get the odbc name the query is using from Access? We can't figure out what name it's looking for so we can recreate it.
We're using Access for Office 365 MSO.
I am trying to move data from SQL Server to MySQL using SSIS. I have used OLE DB Source for fetching data from SQL Server and ODBC Destination to push data into MySQL tables.
I have kept row by row insert method which is working fine without any error but it is very very slow.
When I tried Batch Insert method, the SSIS Package is failing with following error.
[ODBC Destination[191] Error: Open Database Connectivity (ODBC) error occured. State: 'HYC00' - Native Error Code:0 [MySQL] [ODBC 8.0(w) Driver] [mysqld-5.7.12] Parameter arrays with data at execution are not supported
There are 7 tables having 500 000 records each. It took around 9 hrs to complete using row by row method (no errors but very slow).
But when I choose batch, it is throwing the above error.
How to achieve batch insert for improving the data movement speed? I have installed ODBC 8.0 Driver.
Should I modify the connection string OR should I enable any pre-defined variable in MySQL OR what method can I try to achieve this.
I am going around in crop circles, trying to set up a linked server (from SQL Server 2016 to MySQL).
Here is the basic procedure that I used: Create a Linked Server to MySQL from SQL Server. Upon clicking OK to create the new linked server, I received the following SSMS 2016 spasm, Error #7303:
The linked server has been created but failed a connection test. Do you want to keep the linked server?
Additional information:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "MYSQL".
OLE DB provider "MSDASQL" for linked server "MYSQL" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". (Microsoft SQL Server, Error: 7303)
I tried variations that included a Provider String and Catalog (same error):
I have tried the latest MySQL ODBC ANSI/Unicode drivers (5.03.07.00), set up via System DSNs in both the 32- and 64-bit versions of the ODBC Data Source Administrator.
Now, I suspect that something screwy is going on with MS SQL Server and/or its OLE-DB Provider (MSDASQL), because:
All tests of the System DSNs within the ODBC Data Source
Administrator are successful.
Crippled Access 2016 is able to link (via the aforementioned Unicode System
DSN) to MySQL just fine, with minimal effort, listing all databases
and tables.
What is the magic that SQL Server 2016 needs to make the linked-server dialog not result in the above error?
Two things --
Product Name should be MSDASQL.
Leave Provider String and Catalog blank (these are typically taken care of by your DSN definition).
That should do it...
Hi I am using Windows 7 and Access 2013. I am unable to link tables using Visual Fox Pro DB via Access after a windows update. I get the error message : ODBC connection failed. In order to fix this where should I start exploring? I went to windows regedit-> ODBC->ODBCINST.INI and I am not sure how to proceed from here.
To my opinion, you should start from "data sources(ODBC)",
then create a User DSN, by selecting the correct driver
Microsoft Visual FoxPro Driver.
Then you can setup all needed information to create a ODBC connection to your Foxpro database. (I don't have FoxPro as it's not used in my company), but we do the same between MS Access and Oracle.
Once set, you can open your MS Access database and create linked tables towards your FoxPro database via the ODBC DSN just created.
good luck !