![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
I cannot make my DB-Queries using ADO, I get the same error message as when trying to connect to the SQL-Server with Enterprise manager. (???) |
#12
| |||
| |||
|
#13
| |||
| |||
|
#14
| |||
| |||
|
|
PS: For other reasons I have to go back to another snapshot. So I could test the installation of SQL-Server again, and odbc crashed again. So, I cannot install SQL-Server without problems. The error message is (translated from german): runtime error '-2147467259 (80004005)': [Microsoft][ODBC Driver Manager] The name of the datasource could not be found, there was no standard driver mentioned. So, I will have to try SQL Server express 2005 to see if I can set linked servers with GUI. |
#15
| |||
| |||
|
|
runtime error '-2147467259 (80004005)': [Microsoft][ODBC Driver Manager] The name of the datasource could not be found, there was no standard driver mentioned. The error message indicates an incorrect connection string. |
#16
| |||
| |||
|
|
I run queries using ADO from Excel vs. a SQL-Server from my PC (XP SP1, and updated to SP2, MDAC 2.8 installed). Everything works fine. I install SQL-Server 2000 (only client stuff) on the PC, during setup I get an error that the installation of MDAC failed and from that moment ADO-queries fail with the above mentioned error and I get the same message when trying to connect to the SQL Server with Enterprise manager from the PC. So, the installation of SQL-Server destroys something on the PC. Reinstalling MDAC 2.8 does not help. |
#17
| |||
| |||
|
#18
| |||
| |||
|
#19
| |||
| |||
|
|
I went through MS-KB 232060 which told to check dll usage with ListDLLs.exe, no thread should use some dlls during mdac installation, however, winlogon and explorer always use as far as I remember odbc32.dll. (somebody should tell them...) BTW mdac 2.6 is aware of newer versions and does not replace newer files. I used MS cc_x86.msi (MS mdac component checker) and did not get a "simple" info from it as it found many, many different versions of MDAC-files on the PC. And replacing dlls is not possible because of windows xp security features. I found another tool calles mdac-repair.exe, links for both downloads: http://www.macropool.com/en/download/repair_mdac.html This tool found missing entries in the registry of quite a number of files and added everthing to the registry. Then the setup of SQL Server 2000 Client tools, esp. MDAC procedure worked. I'd guess that the installation of mdac 2.6 failed because there where many errors in the registry and it could not determine which mdac version was installed (2.8 was installed, one normal version, one from Windows 2003 server an some older versions). |
![]() |
| Thread Tools | |
| Display Modes | |
| |