• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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