Last post May 15, 2019 03:52 AM by oned_gk
May 14, 2019 04:49 PM|Justin337|LINK
What could be possible reason(s) for this error? and what's the solutions? I've Googled this issue, and nothing seems to help.
The website is a 32-bit ASP.NET website with Access 2003 database, and it is already running WELL using the classic 32-bit mode AppPool at IIS 8.5 for several MONTHS at windows server 2012 R2 64-bit. So far so good. However, that exception still occurs
occasionally for some unknown reason at this website, and when that error is encountered, website crashes although website can already running well without problem for months.
The website has its own AppPool. AppPool setting: 'Enable 32 Bit Applications' is 'True'. NET CLR version is 4.0, and managed pipeline mode is Classic, at at IIS AppPool setting. However, website still are not stable enough to prevent error continue
to happens and crash.
Thank you in advance for your help.
May 15, 2019 02:05 AM|Wei Zhang|LINK
According to your description, the exception basically basically due to the incompatibility of the Microsoft.Jet.OLEDB.4.0 driver in 64 bit OS which means jet.Oledb.4.0 doesn't work well for 64Bit machine.So,it shows that we have to force our application
to build in in 32 bit mode and that will cause other part of code to break.
Since you have enabled Enable 32 Bit Applications , you could try to use a 64 bit compatible 2010 Office System Driver which can be used as replacement for the traditional Microsoft.Jet.OLEDB.4.0 driver. It works both in 32 bit as well as 64 bit servers.
Here is the link, I hope it could help you.
May 15, 2019 03:52 AM|oned_gk|LINK
Your configuration seem good, but using access 2003 may have some limitation. I suggest you to migrate to sqlexpress or sql localdb if you don't want sql server database.
To fix the error, you can go to event log. See when error happend and what causing the problem there. See some warning messages if exists before the error hapend.