| T O P I C R E V I E W |
| sikandar |
Posted - 17 January 2012 : 02:17:47
hi all,
I have a challenge that on windows 2003 there was no challenge but now I am trying same setup on 2008 but getting error as now even mysql version is changed from 3.2 to 5 so kindly let me know what will be new connection method or string as getting following error,
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
/forums/inc_header.asp, line 121
Thanks in advance. |
| 15 L A T E S T R E P L I E S (Newest First) |
| ruirib |
Posted - 13 July 2012 : 17:35:06
Are you using a classic app pool? |
| robbieh |
Posted - 13 July 2012 : 16:53:41
I'm having similar issues. If I try DSN, I get the following:
[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
If I try the 'strConnString = "driver={MySQL ODBC 3.51 Driver I get this
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
If I try 'strConnString = “driver={MySQL ODBC 5.1 Driver} I get an IIS 500 error.
I've tried changing the application pool to 32 bit, no luck. I've tried both ODBC drivers as well.
I'm giving up trying to get the Access database working on Windows Server 2008 R2 and want to get MySQL working. |
| ruirib |
Posted - 03 June 2012 : 20:41:30
I had it as a general setting, actually. That's why I find this weird.
Anyway, you're all set now, so no need to keep worrying about this :): |
| Davio |
Posted - 03 June 2012 : 20:00:11
Well, you can set the 32bit setting per site. So for your site using Access, you can turn it on and for your site using MySQL, you can turn it off. Would make sense if you have it that way. |
| ruirib |
Posted - 03 June 2012 : 19:53:42
No, had you started with MySQL and I wouldn't have advised the 32 bit thing. The puzzling bit is that things work for me one way or the other. |
| Davio |
Posted - 03 June 2012 : 19:44:30
lol that works rui. I had set the 32bit setting when I was testing with Access. Thought that meant I needed this setting set to true to run classic asp.
The defaultapppool is now running in 64bit mode and using the 64bit myodbc drivers with the dsn-less connection string. |
| ruirib |
Posted - 03 June 2012 : 19:19:37
I just set Enable 32 bit apps in my IIS to false and ran one of my local Snitz forums. No issues whatsoever. You only need the 32 bit setting if you use Access, which there is hardly any need, at least on my case.
You can try this too. |
| ruirib |
Posted - 03 June 2012 : 19:16:06
Then I should get the same and I don't. My Process Explorer does not show me that info for w3wp, funnily enough.
Did you install the 64 bit version of MySQL? |
| Davio |
Posted - 03 June 2012 : 19:02:52
Sorry Rui, I can't help it. I couldn't put this one down, as the debugging part of me wouldn't rest. 
The error using a system dsn with the 64bit drivers had given me this error:
quote:
[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
This error means, either the driver is 64bit and the app is 32bit, or vice versa.
Since I know I installed the 64bit driver, I checked my Task Manager to see if IIS was a 32bit or 64bit process. And I notice, the DefaultAppPool is running as a 32bit process.
See screenshot: http://img41.imageshack.us/img41/6352/iisv.jpg
So the 32bit app is accessing the 64bit DSN connection which can't work. (still doesn't explain how you got it working. ah well.)
Anyways, leaving this alone again. lol |
| Davio |
Posted - 03 June 2012 : 18:20:55
quote:
Originally posted by ruirib
David, if 32 bit works for you, don't waste any more time, I'd say. It doesn't affect anything you do. As long as you have a working solution...
I was more doing it for debugging purposes, for anyone else who might have a similar problem in the near future. 
But yeah, I guess I can leave it there for now. |
| ruirib |
Posted - 03 June 2012 : 18:14:03
David, if 32 bit works for you, don't waste any more time, I'd say. It doesn't affect anything you do. As long as you have a working solution... |
| Davio |
Posted - 03 June 2012 : 18:12:57
Well I'm stumped on it as well. Will keep searching and see if anything comes up that could help.
EDIT: Just a small tip, realized there are 2 versions of the ODBC Data Source Administrator. The 64bit and the 32bit.
The 64bit is located here: C:\WINDOWS\System32\odbcad32.exe
The 32bit is located here: C:\WINDOWS\SysWOW64\odbcad32.exe
The 32bit drivers showed up in the 32bit version of the ODBC Data Source Admin. That's why I didn't see them listed in the 64bit version. |
| ruirib |
Posted - 03 June 2012 : 18:05:51
I have had the 64 bit version installed right from the beginning of my usage of Windows 7 (almost 3 years now). I recently upgraded the 5.1 driver (9 May) and it seems the 32 bit version was installed too. I still have a few local test forums running under 3.51, of which I have only the 64 bit version. |
| Davio |
Posted - 03 June 2012 : 17:59:19
So you're sure you have the 64bit version of the driver using?
To check, the 32bit versions are installed in:
C:\Program Files (x86)\MySQL\Connector ODBC 5.1
C:\Program Files (x86)\MySQL\Connector ODBC 3.51
And the 64bit version in:
C:\Program Files\MySQL\Connector ODBC 5.1
C:\Program Files\MySQL\Connector ODBC 3.51
by default.
You have to make sure the 32bit version is not installed, to ensure it is the 64bit version you are using. If the drivers are listed in the folders for the 32bit, then you have the 32bit installed as well, and most likely using the 32bit.
Let me know. |
| ruirib |
Posted - 03 June 2012 : 17:52:14
You enabled the pool to work with 32 bit apps (which works for Access), but that was it. It's still a 64 bit IIS. I have a pretty similar config and I had no issues whatsoever. |
