• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved Connect to MS Access database - Classic ASP Script

ixtusipp

New Pleskian
Hi,

I'm migrating a clasic ASP development, from Plesk Onyx v7.8.11 to Plesk Obsidian v18.0.35 (Windows Server 2019).

I can't connect to the MS Access database.

Error
|9|80004005|[Microsoft][ODBC_Driver_Manager]_Data_source_name_not_found_and_no_default_driver_specified HTTP/2


Conection to DB:
Code:
cn.open "DRIVER={Microsoft Access Driver (*.mdb)};DBQ=" & Server.MapPath("cp/cpdb/cp.mdb")
rs.open "select * from usuarios where id='" & user & "' and pass='" & pass & "'", cn

I have installed the driver and the problem continues. What can be the solusion?

Thanks!
Leandro
 
Usually, the 1st step is enough:
  1. Download and install 64-bit version of Microsoft Access Database Engine package on the Windows server available at: Download Microsoft Access Database Engine 2010 Redistributable from Official Microsoft Download Center
  2. Reconfigure ODBC connections
    Plesk > Domains > example.com > ODBC data sources > <connection name> > Next > Test connection.
  3. In case of Microsoft Access Driver: modify driver name in connection string in .asp file from:
    Code:
    {Microsoft Access Driver (*.mdb)}
    to:
    Code:
    {Microsoft Access Driver (*.mdb, *.accdb)}
  4. Ensure that psacln group has access permissions to the folder where the engine was installed.
    Note: You can check the currently available drivers at ODCB Data Sources (32-bit) and ODCB Data Sources (64-bit) Windows consoles.
    Note: Set of drivers is not always the same for x32 and x64. Consider the website application pool architecture at IIS > Application Pools > example.com(domain)(4.0)(pool) > Advanced Settings > Enable 32-Bit Applications: true/false
 
Usually, the 1st step is enough:
  1. Download and install 64-bit version of Microsoft Access Database Engine package on the Windows server available at: Download Microsoft Access Database Engine 2010 Redistributable from Official Microsoft Download Center
  2. Reconfigure ODBC connections
    Plesk > Domains > example.com > ODBC data sources > <connection name> > Next > Test connection.
  3. In case of Microsoft Access Driver: modify driver name in connection string in .asp file from:
    Code:
    {Microsoft Access Driver (*.mdb)}
    to:
    Code:
    {Microsoft Access Driver (*.mdb, *.accdb)}
  4. Ensure that psacln group has access permissions to the folder where the engine was installed.
    Note: You can check the currently available drivers at ODCB Data Sources (32-bit) and ODCB Data Sources (64-bit) Windows consoles.
    Note: Set of drivers is not always the same for x32 and x64. Consider the website application pool architecture at IIS > Application Pools > example.com(domain)(4.0)(pool) > Advanced Settings > Enable 32-Bit Applications: true/false
Hello IgorG,

Thank you for your answer! That's right, the first step was not enough. He resolved the error by modifying the Application Pools configuration from 64-bit to 32-bit.

Thanks!
 
Back
Top