Azure Windows 2016 server IIS 10 ASP connection to MS Access 2016 w3wp.exe crashes
Summary:
My ASP pages are having w3wp.exe errors when using ADODB.Connection to my MS Access 2016 database. I tried two different approaches and observe different behaviors.
Approach #1 – Use OLEDB connection string
When I use OLEDB connection string (e.g. “Provider=Microsoft.ACE.OLEDB.16.0; Data Source=C:inetpubwwwroot6peasdb6Peas.accdb”), I am able open ADODB.Connection to the database without any error. And I have no problem trying to open ADODB.Recordset with small and simple queries. However, I run into w3wp.exe errors when trying to open ADODB.Recordset of some more complex and larger queries. The w3wp.exe errors will cause the page to crash most of the time and result in a “ERR_CONNECTION_RESET” error.
Approach #2 – Use DSN connection string
When I use DSN connection string (e.g. “DSN=6peas;UID=;PWD=”), I will run into w3wp.exe error every time *BUT* the error will not be severe enough to cause the page to crash. I am only seeing the w3wp.exe error in the Event Viewer. And with the DSN connection string, I am able to open ADODB.Recordset of the same more complex and larger queries without any additional w3wp.exe error.
At this moment, Approach #2 seem to be a better choice as there are no page crashes. However, its drawback is that regards of the size/complexity of the queries, I am getting a w3wp.exe error. And due to the Rapid-Fail Protection setting in IIS Application Pools, the web site application pool will stop if too many w3wp.exe errors occur within the set time period.
So I am hoping to get some help in resolving/stopping the w3wp.exe errors when accessing my MS Access database. Hope some one may have run into similar issues and can provide a solution.
Thank you very much!!
Tech Stack Summary of my web site:
Azure Windows 2016 server
IIS 10.0.14393.0
MS Access 2016
ASP classic
Summary:My ASP pages are having w3wp.exe errors when using ADODB.Connection to my MS Access 2016 database. I tried two different approaches and observe different behaviors. Approach #1 – Use OLEDB connection stringWhen I use OLEDB connection string (e.g. “Provider=Microsoft.ACE.OLEDB.16.0; Data Source=C:inetpubwwwroot6peasdb6Peas.accdb”), I am able open ADODB.Connection to the database without any error. And I have no problem trying to open ADODB.Recordset with small and simple queries. However, I run into w3wp.exe errors when trying to open ADODB.Recordset of some more complex and larger queries. The w3wp.exe errors will cause the page to crash most of the time and result in a “ERR_CONNECTION_RESET” error. Approach #2 – Use DSN connection string When I use DSN connection string (e.g. “DSN=6peas;UID=;PWD=”), I will run into w3wp.exe error every time *BUT* the error will not be severe enough to cause the page to crash. I am only seeing the w3wp.exe error in the Event Viewer. And with the DSN connection string, I am able to open ADODB.Recordset of the same more complex and larger queries without any additional w3wp.exe error. At this moment, Approach #2 seem to be a better choice as there are no page crashes. However, its drawback is that regards of the size/complexity of the queries, I am getting a w3wp.exe error. And due to the Rapid-Fail Protection setting in IIS Application Pools, the web site application pool will stop if too many w3wp.exe errors occur within the set time period. So I am hoping to get some help in resolving/stopping the w3wp.exe errors when accessing my MS Access database. Hope some one may have run into similar issues and can provide a solution. Thank you very much!! Tech Stack Summary of my web site:Azure Windows 2016 serverIIS 10.0.14393.0MS Access 2016ASP classic Read More