Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

Status
Not open for further replies.

smeyer56

IS-IT--Management
Oct 16, 2002
206
US
I inherited a website that is working fine. We are in the process of swicthing to a different host. Last week I had a working connection to the database using DSNless connection on the new host. The old host used DSN the new doesn't.

The connection string used is:
Set C = Server.CreateObject("ADODB.Connection")
C.Open "Driver={Microsoft Access Driver (*.mdb)}; DBQ=" & server.mappath("..\db\database.mdb") & ";"

Today I try to run through the site before changing the DNS servers to point to the new host and I get the error:
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 0x1d64 Thread 0x191c DBC 0x3068f024 Jet'.

Nothing changed on our end. Any ideas why we would get this error?
 
Here is a snippet taken from
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 0x9ac Thread 0xa0c DBC 0x15d1024 Jet'.

or

Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Microsoft Access Driver] General error Unable to open registry key 'DriverId'.

or

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] Cannot update. Database or object is read-only.

or

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] Disk or network error.

or

Microsoft JET Database Engine error '80004005'
Disk or Network error

or

Provider error '80004005'
Unspecified error

or

Microsoft JET Database Engine error '80004005'
Unspecified error

Again, IUSR_<machineName> must have read and write permissions not only on the MDB file, but also on the folder in which it resides, and in some cases the system %TEMP% folder. See Article #2154 and KB #315456 for more information. If you are trying to access a network drive, see Article #2168 for information on setting up IUSR_<machineName> to connect to an Access database via a UNC share. You should also check out Article #2142 for information on opening Access in the correct mode (e.g. adModeReadWrite).

There are certain situations where you will need to set up permissions for the IWAM_<machineName> user as well. Specifically, the C:\document and settings\%domainname%\IWAM_localmachine\local settings\temp folder. Thanks to Sylvain Paquin for pointing this out to us!

If you are not using anonymous access, but rather Windows Authentication, you want to be sure that all potential users are in a Windows group that has sufficient privileges on the folder on the web site where the MDB files resides. You might have to update individual permissions systematically if you are unable to do so via group membership.

If you are getting "unspecified error" then try running the IIS site in its own memory space or, if it is already doing so, returning it to the normal memory pool. Another possibility is the symptom described in KB #225042.

Finally, Access can produce the "unspecified error" message if you use reserved words anywhere in your SQL statement (see Article #2080 for a list of reserved words).

It looks like you have a permissions issue.

[monkey][snake] <.
 
I was wondering if this might have to do with switching from a DSN connection to a DSNless connection. Is there anything in the global.asa file that needs to be removed?

I did some more checking and the DB is recreated occassionally locally and then ftp'd to the web server at the host. The DB is being created on an old server using Access 97. Could this be part of the problem?
 
Okay, to add to the fun. Today everything works fine. Yesterday when I left, I was still getting the errors.
 
[cheers]

See if you have some jobs that run nightly that could change settings that could possibly cause/fix that problem.

[monkey][snake] <.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top