• 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 Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue error connecting to access db after migration

J

jonium

Basic Pleskian
Hello,
a client of mine has problem after a migration to obsidian last version of a script in Classic ASP connecting to a MS Access db.
Here is the connection string:

Set DbConn = Server.CreateObject ("ADODB.Connection")
DbConn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & server.mapPath("/mdb-database") & "\xxx.mdb"
DbConn.CursorLocation = 3
DbConn.Open
Click to expand...

and here is the error log
2021-06-02 19:06:01 127.0.0.1 GET / |5|800a0e7a|Provider_cannot_be_found._It_may_not_be_properly_installed. 80 - 127.0.0.1 HTTP/1.1 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64;+rv:88.0)+Gecko/20100101+Firefox/88.0 - www.xxx.xx 500 0 0 543 590 458
Click to expand...

How to fix it?
Do you think it is better to use DSN ?

Plesk Obsidian 18.0.35
Windows Server 2016
 
Last edited:
hello @jonium ,
I'm not an expert but probably there's no OLEDB 4.0 driver installed on your destination server?
 
how may I verify that?
After having set a ODBC DSN connection he gets:
_The_specified_DSN_contains_an_architecture_mismatch_between_the_Driver_and_Application
 
Last edited:
the problem seems to be related to 32bit and 64bit, I fix it following the post of IgorG here

Resolved - Connect to MS Access database - Classic ASP Script

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...
talk.plesk.com talk.plesk.com
It was enough to Enable 32-Bit Applications in the app pool
now it's running with both connecction string types
Thanks
 
only a question:
is it a problem related only to the hostings migrated from an old server or do I have to do something to other app pools too?
 
You must log in or register to reply here.
Back
Top