ASP連接數(shù)據(jù)庫的連接字符串是Provider=Microsoft.Jet.OLEDB.4.0; Data Source=路徑，采用的是OleDB方式連接，問題可能就出在OleDB方式連接這一環(huán)節(jié)上。

后來搜索網(wǎng)絡得到了解決的辦法 。原來是自己裝的64位Windows 7系統(tǒng)的原因，默認64位環(huán)境下，IIS應用程序池未啟用32位應用程序，我們只需要啟用一下就可以了。打開IIS 7，定位到“應用程序池”，然后選擇使用OleDB方式連接數(shù)據(jù)庫的程序池，然后將啟用32位應用程序設置為True就可以了。



Using MyODBC with ASP.NET in IIS7 on Vista x64

That's a heck of a title, but it's a problem I hit recently. I have a bunch of ASP.NET sites that use MySQL as their datastore, but I hadn't tried the on IIS7 yet. It took a while to get them to work at all (I had to set permissions on web.config and the other website files so that they could be read by both the Users group and the IIS_IUSRS group), but then I was left with an error about my MySQL connection. “ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified” – another very general error that basically means “Something is wrong with your ODBC driver, somewhere.”

After some searching, I learned two things. The first is that if you're running 64-bit you can't use the standard ODBC Data Source Administrator in Administrative Tools with MySQL. You've got to go to C:\Windows\SysWOW64\odbcad32.exe and set up your DSN, if that's your thing. The other thing is that the MyODBC driver is 32-bit only. So to use it at all, you need to make sure you're calling it from 32-bit apps only. That means you've got to tweak the Application Pool you're using to run all its ASP.NET applications as 32-bit. To do this, go to Administrative Tools > Internet Information Services (IIS) Manager (or just hit the Windows key and type “IIS”). Then go to “Application Pools” and select whichever application pool your ASP.NET app uses (or create a new one just for your MySQL apps. Click “Advanced Settings…” and set “Enable 32-Bit Applications”. Now the AppPool will use the 32-bit .NET CLR to run your app, and it'll be able to see your MyODBC driver (whether you use a DSN or not).