So I am going back to a project I created in College, so I can transfer it to PHP. I orginally coded it in ASP Classic.
I am on Windows 8 and running Access 2013.
I am currently getting the following error
ADODB.Connection error '800a0e7a' Provider cannot be found. It may not be properly installed. /PROJECT!Better/verifyuser.asp, line 11
and this is my connection string code.
Dim vPath, pPath, Conn
vPath = ".\db\Comic.accdb"
pPath = Server.MapPath( vPath )
objConn = "PROVIDER=Microsoft.ACE.OLEDB.12.0;DATA SOURCE=" & pPath & ";"
Set Conn = Server.CreateObject("ADODB.Connection")
Conn.Open objConn
any help that you can provide would be awesome!
edit: I already have the enable 32-bit applications in IIS Activated
This question is related to
asp-classic
Under Window Administrative Tools, run ODBC Data Sources (32-bit).
Under the Drivers tab, check you have the Microsoft Excel Driver (*.xls, *.xlsx etc...) - the file name is ACEODBC.DLL
If this is missing, you will need to install the Microsoft Access Database Engine 2016 Redistributable.
You'll find the installer here https://www.microsoft.com/en-us/download/details.aspx?id=54920
Set objConn1 = Server.CreateObject("ADODB.Connection")
objConn1.Provider = "Microsoft.ACE.OLEDB.12.0"
objConn1.ConnectionString = "Data Source=" & pPath & ";Extended Properties=""Excel 12.0 Xml;HDR=YES;IMEX=1"""
Got this exception when maintaining very old application on Server 2003 using Asp classic on IIS6 with Oracle 9.2.0.1. The fix is by updating oracle to 9.2.0.6.
You should use the provider available in your machine.
See the attached screen shot. Here my provider will be SQLNCLI11.0
I got the same issue and It got solved by installing Oracle 11g client in my machine..
I have not installed any excclusive drivers for it. I am using windows7 with 64 bit. Interestignly, when I navigate into the path Start > Settings > Control Panel > Administrative Tools > DataSources(ODBC) > Drivers. I found only SQL server in it
A couple of suggestions
The ACE driver isn't installed by default. It's also a 64 bit driver, so it might be worth disabling 32bit in your app pool. I've known 64 bit drivers not work when 32 bit is enabled.(eg the ISAPI filter which connects IIS to Tomcat).
The older JET driver is 32bit. It is included by default. If you could save a copy of your database as a .mdb file then using the JET driver might be a workaround
Have you got the driver installed? If you go into Start > Settings > Control Panel > Administrative Tools and click the Data Sources, then select the Drivers tab your driver info should be registered there.
Failing that it may be easier to simply set up a DSN connection to test with.
You can define multiple connection strings of course and set-up a 'mode' for working on different machines.
Also there's ConnectionStrings.com.
-- EDIT --
Just to further this, I found this thread on another site.
Following steps has fixed my issue.
(1) Moved the website to a Dedicated application pool.
(2) Changed the Managed Pipeline Mode from integrated to Classic.
(3) Set Enable 32-Bit Applications from false to true.
ASP pages are working fine now!
Check the site's Application Pool in IIS / Application Pools / YourPool / Advanced Settings :
There's some anecdotal evidence to suggest you do this too:
install this https://www.microsoft.com/en-us/download/details.aspx?id=13255
install the 32 bit version no matter whether you are 64 bit and enable the 32 bit apps in the application pool
Source: Stackoverflow.com