ADO Error%3A 0x80004005

[Eric_G]

I am in process of converting code writen in Labview 8.2 to Labview2013, and also changing from Windows XP to Windows 7.  I've been able to successfully compile & rebuild the code, but now am getting error message when running the executable.  Any ideas of how to resolve these?  

Here are the error messages I get:
NI_Database_API.lvlib:DB Tools Open Connec
(String).vi->NI_Database_API.lvlib:DB Tools Open Connec
(Path).vi->Titan_DBConnect.vi->TMS_frontend_Titan.vi<ERR>ADO Error:
0x80004005

Exception occured in Microsoft OLE DB Provider for ODBC
Drivers: General error: Invalid file dsn '' in NI_Database_API.lvlib:DB Tools
Open Connec (String).vi->NI_Database_API.lvlib:DB Tools Open Connec
(Path).vi->Titan_DBConnect.vi->TMS_frontend_Titan.vi-2147467259 -

There is a "Titan DBConnect.vi" VI that points to a "Database.dsn" file. 

Here is what is in the Database.dsn file:  (This file is created by Windows, and is the same for XP & 7.)

[ODBC]
DRIVER=Driver do Microsoft Access
(*.mdb)
UID=admin
UserCommitSync=Yes
Threads=3
SafeTransactions=0
PageTimeout=5
MaxScanRows=8
MaxBufferSize=2048
FIL=MS
Access
DriverId=25
DefaultDir=C:\Test Config
DBQ=C:\Test
Config\Database.mdb

Thanks!

[MStewart]

If you are using a 64-bit version of Windows 7, you may want to check out this KB article.

http://digital.ni.com/public.nsf/allkb/E7984C0DA0F0E65086257694005B4CB7

[Eric_G]

Could the info in the following link be relevent to my issue?

http://digital.ni.com/public.nsf/allkb/1D5EB4DCBD13106486256B9D005E11B0

I tried these instructions, but no window appeared or Provider tab.

"

NOTE: If you are using a 64 bit Windows operating system, the provider tab will not show the Microsoft Jet 4.0 OLE DB Provider or Microsoft Office 12.0 Access Database Engine OLE DB Provider.  This is because they are 32 bit database providers.  To make 32 bit providers display in the Provider tab, follow these steps:

1. Navigate to Start>>All Programs>>Accessories>>Command Prompt
2. Type the following command: C:\Windows\syswow64\rundll32.exe "C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll", OpenDSLFile C:\test.udl, where C:\test.udl is the file path to the UDL file you have created. This will open the UDL file.
3. Click the Provider tab, the 32 bit database providers should now show.

"

I copied the database.mdb file from the system running Labview 8.2 code & Windows xp into my new computer running Windows7 & Labview2013 code.  Could copying this file instead of creating a new one be part of the problem I'm having?  If so, how can I create a new database.mdb file?  I don't have MS Access.

[Ryan_K.]

The document you linked above definitely could be useful in resolving your issue. Your original error mentioned a .dsn file, and your second post mentioned a .udl file. LabVIEW communicates with the database through either the ODBC standard (uses a DSN) or the OLE DB standard (uses a UDL file). Which standard are you actually trying to use? Either way, make sure all the the settings you're using are consistent whichever standard you're trying to use.

http://digital.ni.com/public.nsf/allkb/1D5EB4DCBD13106486256B9D005E11B0 (the one you linked above) gives a good description of how to use the OLE DB standard to communicate with a database.

I'm also a little unclear whether you were able to test the steps outlined in the first document linked above (http://digital.ni.com/public.nsf/allkb/E7984C0DA0F0E65086257694005B4CB7). Let me know if that process was successful or if you ran into any problems trying to follow those steps.

You also asked a question about .mdb files. It may be possible that copying the file from XP to Windows 7 could have caused your problem. You can create a new .mdb file through LabVIEW by following the instructions detailed in this document:http://digital.ni.com/public.nsf/allkb/95EE6A951D01CE0A8625733F00098371?OpenDocument

Finally, when executing the above instructions that you quoted, make sure that the file path is correct and that you are pointing to a .udl file. I was unable to duplicate the problem you were experiencing with those steps on my machine.

Let us know if you make in progress with these suggestions.