Data Source Not Found on Windows using MyODBC (MySQL) connector
-
We have a customer running a new Windows 7/64 system. Our 32 bit VB.NET 2008 application uses the MyODBC connector - DSNLESS. However, for 1 particular Windows 7/64 customer only that we can see no matter which MyODBC connector we try we always get -2147467259 Hex(80004005) [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified We have tried 6 different versions. Both the 32 bit and 64 bits versions of 3.51, 5.1.11 and 5.1.8 (I believe). It always fails on her machine and never fails anywhere else. We have tried it on 3 different systems here and it always works. Any ideas? Thanks
-
We have a customer running a new Windows 7/64 system. Our 32 bit VB.NET 2008 application uses the MyODBC connector - DSNLESS. However, for 1 particular Windows 7/64 customer only that we can see no matter which MyODBC connector we try we always get -2147467259 Hex(80004005) [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified We have tried 6 different versions. Both the 32 bit and 64 bits versions of 3.51, 5.1.11 and 5.1.8 (I believe). It always fails on her machine and never fails anywhere else. We have tried it on 3 different systems here and it always works. Any ideas? Thanks
QBTeKcom wrote:
Any ideas?
Several, but very nothing useful.
- Is the connecter backed by a company? Do they have a helpdesk? Open source? Do they have a specialized forum?
- What does her eventlog say?
- Does it only reject local connections (suspect the local servers' settings) or also non-local connections? (suspect any client driver)
- Can you contact the server with any other tool?
- Are the versions of the dependencies of the plugin the same?
- Can she work temporary in a virtual machine?
- Verify the versions of both ODBC and MDAC?
- Considered testing with another data-provider?
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
QBTeKcom wrote:
Any ideas?
Several, but very nothing useful.
- Is the connecter backed by a company? Do they have a helpdesk? Open source? Do they have a specialized forum?
- What does her eventlog say?
- Does it only reject local connections (suspect the local servers' settings) or also non-local connections? (suspect any client driver)
- Can you contact the server with any other tool?
- Are the versions of the dependencies of the plugin the same?
- Can she work temporary in a virtual machine?
- Verify the versions of both ODBC and MDAC?
- Considered testing with another data-provider?
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
See answers in bold •Is the connecter backed by a company? Do they have a helpdesk? Open source? Do they have a specialized forum? It is from MySQL so I assume so but it is not the MyODBC module in question but the Windows system. It is a brand new laptop just 2 weeks old •What does her eventlog say? I didn't see it yet •Does it only reject local connections (suspect the local servers' settings) or also non-local connections? (suspect any client driver) Did not try. This is a remote db to Windows •Can you contact the server with any other tool? I can connect to the same database from different windows - mine using same program. Next would be to try a little test program then maybe the MySQL Query Browser but the Query browser does not use the MyODBC driver •Are the versions of the dependencies of the plugin the same? ??? Do not understand the question? What plugin? We have been doing this for 8 years. First the program was VB6 and now VB.Net 2008 and never had this before or on any other Windows. •Can she work temporary in a virtual machine?No •Verify the versions of both ODBC and MDAC? HOW? •Considered testing with another data-provider? How? This is a live eCommerce shopping cart database.
-
See answers in bold •Is the connecter backed by a company? Do they have a helpdesk? Open source? Do they have a specialized forum? It is from MySQL so I assume so but it is not the MyODBC module in question but the Windows system. It is a brand new laptop just 2 weeks old •What does her eventlog say? I didn't see it yet •Does it only reject local connections (suspect the local servers' settings) or also non-local connections? (suspect any client driver) Did not try. This is a remote db to Windows •Can you contact the server with any other tool? I can connect to the same database from different windows - mine using same program. Next would be to try a little test program then maybe the MySQL Query Browser but the Query browser does not use the MyODBC driver •Are the versions of the dependencies of the plugin the same? ??? Do not understand the question? What plugin? We have been doing this for 8 years. First the program was VB6 and now VB.Net 2008 and never had this before or on any other Windows. •Can she work temporary in a virtual machine?No •Verify the versions of both ODBC and MDAC? HOW? •Considered testing with another data-provider? How? This is a live eCommerce shopping cart database.
QuickBooksDev wrote:
It is from MySQL so I assume so but it is not the MyODBC module in question but the Windows system.
Don't assume, verify. Windows itself has little to do with databases. It might be a different version of the driver, yes.
QuickBooksDev wrote:
•Verify the versions of both ODBC and MDAC? HOW?
QuickBooksDev wrote:
I can connect to the same database from different windows - mine using same program. Next would be to try a little test program then maybe the MySQL Query Browser but the Query browser does not use the MyODBC driver
Sounds like :thumbsup:
QuickBooksDev wrote:
Are the versions of the dependencies of the plugin the same? ??? Do not understand the question?
The MySql client library, or connector, or provider or whateveritscalled, has dependencies on other software. Just like you reference libraries, so did they. Might be that some other application overwrote them with an incompatible version.
QuickBooksDev wrote:
Did not try. This is a remote db to Windows
Aight, no need to check, since you already said that you can connect with another client.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
We have a customer running a new Windows 7/64 system. Our 32 bit VB.NET 2008 application uses the MyODBC connector - DSNLESS. However, for 1 particular Windows 7/64 customer only that we can see no matter which MyODBC connector we try we always get -2147467259 Hex(80004005) [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified We have tried 6 different versions. Both the 32 bit and 64 bits versions of 3.51, 5.1.11 and 5.1.8 (I believe). It always fails on her machine and never fails anywhere else. We have tried it on 3 different systems here and it always works. Any ideas? Thanks
Have you tried the program on other Windows 7/64 bit machines besides the customer's?
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
-
Have you tried the program on other Windows 7/64 bit machines besides the customer's?
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
Yes, only fails on her's.
-
Yes, only fails on her's.
Sounds like something is goofy with the drivers on that specific machine. Good luck and if anything comes to mind, I'll let you know.
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus