• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 719
  • Last Modified:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005) ERROR

I am trying to use ASP to Access an Access 2003 database
I am using windows XP profesional with IIS installed the error is

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Driver Manager] Driver's
found and no default driver specified

I have tried different ODBC drivers but which one should i use to get it working?

Could someone explain to me step by step what to do thanks.
0
mtips
Asked:
mtips
5 Solutions
 
sachin_raoraneCommented:
You can use the connection string to open the connection with access2003

<%
Dim oCN
Dim strCon

strCon = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\Projects\VirtualDirs\DS_App\Db\DS.mdb;Persist Security Info=False"

Set oCN = Server.CreateObject("ADODB.Connection")

oCN.Open strCon
%>

Note :
"Data Source=D:\Projects\VirtualDirs\DS_App\Db\DS.mdb" This should be the physical path where the MDB file is stored. You need to check your file path
0
 
GawaiCommented:
what is your connection string to connect Access DB ?
post it here so we can find the problem
0
 
GawaiCommented:
try this one :

      strDB = "DRIVER={Microsoft Access Driver (*.mdb)};uid=;pwd=;"
      strDB = strDB & "DBQ=C:/path/db/Access.mdb"

save this file as con.asp

and now u call the file:
<!--#include file="con.asp" -->
Dim strDB, objRs, objCon, strSQL
Set objCon = Server.CreateObject ("ADODB.Connection")
objCon.Open strDB
strSQL= "SELECT * FROM AccessTbl"
Set objRs = Server.CreateObject ("ADODB.Recordset")
objRs.Open strSQL, objCon,1,3

and so on......


0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
beenish_anwarCommented:
Try this

Set conn = Server.CreateObject ("ADODB.Connection")
conn.Open "Driver={Microsoft Access Driver (*.mdb)};DBQ=" & Server.MapPath("../database/filename.mdb")
0
 
Leo EikelmanCommented:
The following microsoft doc lists the most common solutions to this problem:

http://support.microsoft.com/kb/306345/EN-US/


It could stem from not having permissions to use the dirvers.

Using an ODBC DSN

Insufficient Permissions to Read the DSN Registry Key
Grant the Windows NT 4.0 or Windows 2000 user account Read access to the specified ODBC System DSN registry key as follows:

1. Determine which account is used to process the request for the ASP page.
2. From the Start menu, click Run, type regedt32.exe, and then click OK to start Registry Editor.
3. In the HKEY_LOCAL_MACHINE window, browse to the HKLM\SOFTWARE\ODBC\ODBC.INI key. The ODBC.INI key contains a subkey for each ODBC SYSTEM DSN that is registered on the server.
4. Click the DSN registry key for the DSN that is specified in the ADO connection string.
5. From the Security menu, click Permissions.
6. Add the user account that you identified in step 1 to the list of users who can access this key, and select the Read check box for this user.
7. Click Apply, and then close Registry Editor.

Cheers,

Leo



0
 
timkerCommented:
I can recommend this site:
http://www.connectionstrings.com/

It has both OLEDB and ODBC connection strings for Access.
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now