Dbase Driver 64-bit
Vira Bhakta
You just need to provide the name of the target table, and the path and filename (without the extension) of the source file. Assuming the source file is 'c:\data\testfile.dbf', then the statement would read:
This thread is in the T-SQL (SS2K8) forum. If you are using the 64-bit version of SQL Server 2008, then you are out of luck; the 64-bit version of the MSDASQL provider cannot access the 32-bit dBase driver. Currently, there is no 64-bit version of the dBase driver.
OLE DB provider "msdasql" for linked server "(null)" returned message "[Microsoft][ODBC dBase-stuurprogramma]Algemene waarschuwing Kan de registersleutel Temporary (volatile) Jet DSN for process 0x704 Thread 0x598 DBC 0x3598aec Xbase niet openen.".
The error is caused by that you create User DSN in ODBC administrator. Please create a System DSN to points to your data source in in ODBC administrator, then add the ODBC data source under gateway. When adding a ODBC data source under gateway, make sure you enter the same connection string as that you get in Power BI Desktop. For more details, please review this similar thread: -with-Files-and/Personal-Gateway-X-On-Premises-Gateway/m... .
I'd like to add that I discovered the reason it wouldn't let me select On-premises gateway before, it was because I had a few CSV files included as part of the published report, these CSVs also need to be added to the Gateway as a File, pointing to the CSV.
I had to create a 64-bit DSN and use the 64-bit driver 'Microsoft Access dBASE Driver' where I was trying to use a 32-bit driver 'Microsoft dBase Driver' with a 32-bit DSN which gave mismatch between Driver and Application error, this can be seen in:
EDIT: I've also tried removing the existing gateway from the dashboard and re-installing on-premesis gateway, creating an entirely new gateway with a different name, then added the data source back, yet the dataset still asks for a personal gateway. Perhaps I should try remove the dataset and republishing it?
Hi @davidSIT,
Do you use Windows authentication method when creating the ODBC data source? If so, is there any possibility that you use basic authentication method? Based on my test, I have to use same authentication method when creating ODBC data source and adding ODBC data source under gateway.
Thanks,
Lydia Zhang
This error message occurs because the appropriate 64-bit driver isn't installed on your machine. Kindly note that Power Automate for desktop is based on 64-bit architecture and thus is only compatible to 64-bit database drivers.
Verify that you have 64-bit Access Database driver installed on your machine by going to ODBC Data Source Administrator (64-bit) application on windows and then the Drivers tab. If you don't see "Microsoft Access Driver" in the list, you need to download and install the 64-bit version from Microsoft Access Database Engine 2016 Redistributable.
Check if the "mso.dll" registry key is present in both the above paths. If the key is present, this means that you haven't uninstalled all the drivers. Verify the drivers on your system and uninstall all the Access drivers and verify the registry editors' paths mentioned in step 2 again.
Download a new version of Microsoft Access Database Engine from the Microsoft official website, and then install the 64-bit driver using command prompt (CMD) with the command AccessDatabaseEngine_x64.exe /quiet for 2016 Redistributable.
Lastly, install the 32-bit driver using command prompt (CMD) with the command AccessDatabaseEngine.exe /quiet for 2016 Redistributable. This will allow both the 32-bit and 64-bit drivers to co-exist on your machine.
So I suspect that the Microsoft Excel calls the 64-bit version while Citadel 5's ODBC driver uses the 32-bit version. But I am not sure what would be a good way to fix this situation (probably not naively replace the 64-bit version with 32-bit version, or make a pointer for Excel to the 32-bit version?)
This bit me pretty hard recently, too. One of the key things to notice in nyc's link is that the 32 bit and the 64 bit Data Source Administrator exe's look the same and have the same name but are launched from different directories.
But the last step never completes (Executing is displayed forever).When Management Studio is forcibly closed and restarted the new linked server is there but only contains Catalogues subitem. If we try to expand it, Management Studio goes into loop yet again.
The first thing to do is to make sure that you are using 32 bit drivers if you have a 32 bit SQL Server and 64 bit drivers if you are using a 64 bit SQL Server. 64 bit SQL Servers can't use 32 bit ODBC (or OLEDB or anything else) drivers.
On recent versions of SQL Server, 2005+, I've had the best success with the "ACE" drivers. These drivers replace the old "JET" drivers and were introduced with Office 2007. They are OLEDB based, but you wouldn't necessarily notice. The release for Office 2010 that comes in 32 bit and 64 bit versions. The redistributable ACE drivers are available for download on Microsoft's site.
With the new drivers, you don't need to create a system DSN like with the old ODBC drivers. You can just create the linked server and go. There should be plenty of examples of how to create linked servers using ACE drivers (both with TSQL and the SSMS GUI) on the internet.
You may also find that accessing files on the network is harder than accessing the same file on a local disk. This is usually a problem with delegation and security. Getting that going can be a hassle, depending on your infrastructure.
(If you are interested, I did a few of blog entries "Legacy Connectivity in a 64 bit world" about three or four years ago, covering dbase/foxpro issues, 32/64 bit issues, plus db/2 and other stuff. There is probably more than there than you would want to read. This was back before the 64 bit ACE drivers were released, and things are better now.)
Bridging Data, is the second blog in this series. It guides you through the experience of creating OLE DB connections to a personal geodatabase (.mdb), a Microsoft Access database (.accdb), and a MySQL database in ArcGIS Pro. Once an OLE DB connection has been created, many options are available to use and work with this tabular data in ArcGIS Pro.
Migrating Data is the third blog in this series. It provides a look at the differences between file-based geodatabase types, characteristics, and capabilities. Additionally, two new sample tools are introduced and available to help with migrating a personal geodatabase to a file geodatabase and, if needed, migrating a file geodatabase to a mobile geodatabase.
In ArcGIS Pro, you can establish an Object Linking and Embedding Database (OLE DB) connection (read-only) to access tabular data sources from any database that supports OLE DB, and for which you have the driver. This type of connection is most commonly used to connect ArcGIS Pro to data sources that support OLE DB but cannot be accessed from the list of supported database platforms on the Database Connection dialog box.
Object Linking and Embedding Database (OLE DB) is a Microsoft Windows connectivity method that uses the same core application programming interface (API) to help bridge communication between client applications and a variety of data sources. This bridge consists of an OLE DB provider (a set of .dll files) that uses the services of an ODBC driver to connect and interact with both relational and nonrelational databases in a uniform manner.
An OLE DB provider is similar to a language translator that helps bridge communications between two people speaking different languages. For a client application and a data source to successfully communicate with each other, the specific OLE DB provider for the data source you want to connect to must be installed on the same client machine where ArcGIS Pro is installed and will be used to create the OLE DB connection. Installing the appropriate OLE DB provider equips the client application with the correct language needed to communicate with its associated data source.
There are specific providers for each type of data source supported by OLE DB. To make an OLE DB connection from a 64-bit ArcGIS client such as ArcGIS Pro, install the appropriate 64-bit drivers on your ArcGIS Pro machine to connect to these data sources using OLE DB.
Open Database Connectivity (ODBC) is a connectivity method supported on Windows, Linux, Mac, and UNIX. The Microsoft ODBC Data Source Administrator application manages database drivers and data sources and is located in the Windows Control Panel under Administrative Tools.
A data source name (DSN) is a unique name that you can create to associate a particular ODBC driver with the data source you want to access. You can use the Microsoft ODBC Data Source Administrator to add, update, and delete DSNs. A DSN also stores the connection details to the data source, like its database name, directory, database driver, UserID, password, and so on.
Once a DSN has been created, you can use ArcGIS Pro to create an OLE DB connection using the Data Link Properties dialog box, where you can specify your newly created unique DSN to request a connection to an ODBC data source.
The Microsoft Access Database Engine technology helps bridge communication and data transfers between files that are proprietary to the Microsoft Office system and other non-Microsoft Office applications such as ArcGIS Pro.
c80f0f1006