Your classic ASP website is likely returning Jet driver or database driver not found errors because the application pool is running as 64-bit. To resolve this, log into the ASPnix control panel, select your website, navigate to the Home Folder tab, enable the 32-Bit Application Support checkbox, and update the settings. This forces the application to run in 32-bit mode, which is required for legacy drivers to function.

Classic ASP depends on older 32-bit COM-based components like the Microsoft Jet database engine for Access .mdb files or other OLE DB/ODBC drivers. These are incompatible with 64-bit processes. The default behavior in IIS is 64-bit for application pools, which is why this issue surfaces frequently on new setups or after server changes.

#Why Classic ASP Driver Errors Occur

The root cause is an architecture mismatch. Microsoft never updated classic ASP to support 64-bit execution, and components like Microsoft.Jet.OLEDB.4.0 exist only in 32-bit form. When a 64-bit w3wp.exe process tries to load a 32-bit DLL, it fails with driver not found or provider not registered errors. This affects not only Jet but also other legacy drivers for Excel, dBase, or older SQL connectors. Understanding this helps avoid chasing incorrect solutions like reinstalling drivers on the server, which is not possible or necessary in a hosted environment.

#Steps to Enable 32-Bit Application Support

  • Log into the ASPnix Windows control panel at https://panel.aspnix.com
  • Click the Websites icon under the System resource box
  • Select your website by clicking on it
  • Switch to the Home Folder tab
  • Check the Enable 32-Bit Application Support box
  • Click the Update button to apply changes

#Testing Your Database Connectivity After the Change

With the update complete, reload your ASP pages that perform database operations. Common test involves a simple page that opens a connection and queries a table. If using an Access database, ensure the file permissions allow the application to read it. Watch the event logs or custom error logging in your ASP code for any remaining issues. This configuration change applies specifically to that website and does not affect others on the account.

#Example ADO Connection String in VBScript

vbscript 
Set conn = Server.CreateObject("ADODB.Connection")
conn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & Server.MapPath("/db/mydb.mdb")
conn.Open
' Execute your SQL here
conn.Close
Set conn = Nothing

Use similar patterns for other providers, making sure they match 32-bit availability. A common pitfall is specifying a driver that only exists in 64-bit form or using an incorrect connection string syntax after the architecture change.

Enabling 32-bit mode is the standard resolution for these classic ASP database errors. Apply it to any site using legacy database access. Review your connection strings and ensure no other 64-bit specific components are in use. For more complex setups our support team can provide additional guidance.