This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 15%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi
In a net framewok WinForm app below connection string works in x86 and Any CPU active platforms.
connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Password=;User ID=Admin;Data Source=' S:\MyPath\MyDB.mdb';Mode=Share Deny None;"
However in asp.net classic same connection string in Visual Studio debug (IIS Express) comes out with errors as below;
x86: Could not load file or assembly 'xxxxxxx' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Any CPU: The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.
Same machines was used for both WinForm and asp.net classic.
How can I make the connection string work in asp.net classic?
Thanks
Regards
**S:**MyPath\MyDB.mdb
What for a drive is S:? A local drive, SAN or NAS? Do the IIS service account have access to?
S: is a network drive on a server on same LAN.
Environemt for both WinForm and aps.net was same. Same machine accessing same db on network via S: drive.
IIS is local and should have access.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 46%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Have you forced the web site to run as x86? You can't use any cpu here, since then how the application is launched (from win32 or win64 command line will determine the bit size). So, for the web site, you need to force the web site to run as x32 bits (or x64 bits if you using ACE x64 bits). ACE (the Access data engine) is not .net code, so this means you need to ALWAYS force your .net project to match that of the x32 or x64 bit version of ACE. Don't use ANY CPU in such cases.
Hi Albert
In application pool I have set Enable 32-Bit Applications to True but that has not helped.
Thanks
Regards
Setting and enabling the x32 bit applications is a step I recommend, but as noted, you can't "guess" - so in addition to enabling the x32 bit app pool, you STILL have to force the project build to match the version of Access you have - don't leave this issue up to the wind here. In other words, don't risk using ANY cpu, but force the project to x32 or x64 (to match the version of Access you using - they need to match).
S: is a network drive on a server on same LAN.
So it's on a NAS and the share is mapped as drive S: in your profile/for your user; it's not avaliable for IIS.