Last post May 25, 2010 02:35 PM by maccaj
Jun 19, 2009 01:24 AM|VaticNZ|LINK
This is more an informational post for anyone that might be experiencing this issue (and for myself incase I have the same problem in the future and can't remember the solution :-))
It's kind of obscure but caused me a few hours of stress, so maybe it'll help someone else... Sorry if this is repeated (couldn't find it) or deprecated (some don't have the luxury of latest and greatest).
If you are using trying to use Jet 4.0 to access MS Excel documents (or other data files) on a x64-based server, you will have discovered that there is no support for this combination.
The only solution is to allow IIS to run 32-bit applications on Windows 64 and to install a supported db provider:
You'll need to install the driver, 64-Bit OLEDB Provider for ODBC (MSDASQL) that acts as a bridge:
"The Microsoft OLE DB Provider for ODBC (MSDASQL) is a technology that allows applications that are built on OLEDB and ADO (which uses OLEDB internally) to access data sources through an ODBC driver. MSDASQL is an OLEDB provider that connects to ODBC,
instead of a database. MSDASQL ships with the Windows operating system, and Windows Server 2008 & Windows Vista SP1 are the first Windows releases to include a 64-bit version of the technology."
Download here :
This all works fine, but I came across two things that had me scratching my head (and stressing):
1) You need to allow 32-bit ASP.Net in IIS Web Service Extensions - Read
http://www.textcontrol.com/blog/permalink/2006082101/ for instructions on both enabling 32-bit apps AND the IIS web service extension setup.
2) If you are using any registry keys under IIS x64, a new node will be added in the registry - Wow6432Node - into which you'll need to move/copy any relevant keys that were used under x64.
i.e. We had a data key stored in HCLM\Software\CustomKey that was no longer available when 32-bit was enabled. We re-created the key under the Wow6432Node and all was good.
Sorry if I've waffled - hopefully the info is fairly succinct. Feel free to reply if you need more info.
Windows 2003 x64 oledb jet 4 excel
Aug 21, 2009 01:47 PM|deepaknaidu|LINK
Thnank you very much, this lead helped me a lot. Those links are real saver. I was having a OleDB connection to featch my data on the server side from excel, wich in running x64 based processor. I was scavenging the internet like cray for any help. with
your find I was able to debug my webapp. I am with difference error now. I will reply back if it really worked.
Aug 30, 2009 12:29 AM|deepaknaidu|LINK
Unfortunately I couldn't make the App Pool to run in 32 bit because the application had to run inside the sharepoint custom pages which my admin wanted to run in 64 bit only. So searched more found this excellent
resource which can runin 64 bit environment too and load the excel sheet to my dataset
May 25, 2010 02:35 PM|MaccaJ|LINK
Thanks for your info - much appreciated.
I am running Windows 2008 Server x64 with IIS 7.0 and came across this problem when connecting to an Access Database.
Luckily, I had the luxury of installing Access and Excel 2007 which in turn installed the latest OLEDB library onto the system (Microsoft.ACE.OLEDB.12.0). For those who don't have that luxury, you can get the Office 2007 connectivity drivers from this link:
Then after reading your post above, I created a separate application pool for the site and under the advanced settings, I set the property "Enable 32-Bit Applications" to true.
Everything then worked fine.