Classic ASP Discussion - Connection Problems

Print Page | Close Window

Connection Problems

Printed From: Web Wiz Forums
Category: General Discussion
Forum Name: Classic ASP Discussion
Forum Description: Discussion on Active Server Pages (Classic ASP).
URL: https://forums.webwiz.net/forum_posts.asp?TID=1467
Printed Date: 29 March 2026 at 5:17am
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com

Topic: Connection Problems

Posted By: choshour
Subject: Connection Problems
Date Posted: 29 March 2003 at 9:11pm

I am new to ASP and am trying to get this connection string to work. I would thankful to any one that might be able to help me. Thanks in advance

<%
Dim adoCon    'Database Connection Variable
Dim rsCommon   'Holds the configuartion recordset
Dim strCon   'Holds the Database driver and the path and name of the database
Dim strSQL   'Holds the SQL query for the database
Dim strDbPathAndName  'Holds the path and name of the database

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

strDbPathAndName = Server.MapPath("admin/database/player.mdb")

strCon = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" & strDbPathAndName

adoCon.connectionstring = strCon

adoCon.Open

Set rsCommon = Server.CreateObject("ADODB.Recordset")

rsCommon.Open strSQL, adoCon

rsCommon.Close

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x4f4 Thread 0x9a0 DBC 0xc633f64 Jet'.

/profile manager/connection2.asp, line 17

Replies:

Posted By: Gullanian
Date Posted: 30 March 2003 at 1:29am

Well its a database path problem, try

strDbPathAndName = Server.MapPath & "admin/database/player.mdb"

General error Unable to open registry key
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x6cc Thread 0x78c DBC 0x144cfc4 Jet'.

This error can happen for a number of reasons the main reason being if the path to the database is incorrect.

You need to check that the path to the database is correct (You must use the physical path on the server to the database and not a virtual path).

The error is also quite common if the permissions on the server are incorrect. Check that IIS has sufficient permissions to access the registry and that the correct permissions, read and write, are set on the directory containing the database and the database itself, for the IUSR account.