Hello all - The following connection strings:

Conn.open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" & Server.MapPath("/DB/em.mdb")

Conn.open "DRIVER={Microsoft Access Driver (*.mdb)};DBQ=C:\Inetpub\wwwroot\em\DB\em.mdb"

are the two I have always used successfully with Access (2003). A couple of questions if I may.

> Am I using outdated strings or ones considered no ideal?
> Can someone please assist with what I may have missed relating to the following very annoying brick wall:

I have new XP pro machine. While getting everything up an running all of my sites using Access which were previously runing fine using the above strings are now giving me the following error:

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 0xb9c Thread 0xe48 DBC 0x1164024 Jet'.

I have checked permission on the folder holding the .mdb files, the .mdb files them selves, turned of any antivirus, win firewall. All steps I am aware of fail to rectify the issue. Now I turn to Google - After spending an hour researching the issue I have found no advice outside what I have done. last step the ever so helpful Wrox members

BTW - I have now given the EVERYONE user full rights the the folder/file and still no joy :(

TYIA or your time...

Wind is your friend
Matt
www.elitemarquees.com.au

__________________
Wind is your friend
Matt

Try to avoid using the Access driver.

It's ancient, buggy, and prone to this kind of stuff.

Look here:
http://www.carlprothman.net/Default....orMicrosoftJet

MUCH more reliable, in my experience.

SO:

Conn.Open ""Provider=Microsoft.Jet.OLEDB.4.0;" & _
           "Data Source=" & & Server.MapPath("/DB/em.mdb") & ";"

See if that doesn't work better.

And by the way...

If Google didn't serve up these pages, you might look at them, if the JET driver doesn't work:

http://search.msdn.microsoft.com/Default.aspx?query=Unable+to+open+registry+key+'Te mporary+(volatile)+Jet+&brand=msdn&locale=en-us&refinement=

The first two links there give the same answer: Make a change in the registry.

Thankyou for the prompt reply...

Sorry I should have posted this one to:

Conn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & Server.MapPath("/DB/em.mdb") & ";"

I always try to help myself before taking peoples time here. I got that on from connectionstrings.com which is a fairly good resource however this string gives me a very ambiguopus error:

Microsoft JET Database Engine (0x80004005)
Unspecified error

Very odd....I will look at your second link now

TYVM



Wind is your friend
Matt
www.elitemarquees.com.au

Man, that is WEIRD!

I assume you know that error number 0x80004005 is actually just a memory violation error? That is, something tried to access memory that doesn't exist (usually location 0x0000000) or maybe tried to write to read-only memory. Sometimes you see readable error messages associated with that number, which just means that somebody chose to catch the error and then re-throw it with a different message (but same number).

So that means you really are getting a *HARD* failure under the covers of the Open. Ugh. FWIW, by the by, I *am* running XP Pro and Access 2003. And I use the OLEDB connection string consistently, and I've yet to get that particular error.

My morning is getting even wierder...

I just allowed full permissions in the:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC

area of the registry, closed the reg and them refreshed the page to be told:


Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.

Now I am very confused. This is a brand new machine aggghhhhh

Wind is your friend
Matt
www.elitemarquees.com.au

for the benefit of others who may look at this post in the future the reason I done that in the registry was the following MS article:

http://support.microsoft.com/kb/295297

We shouldnt have to do this. I have never experienced so muxh troble getting an app running that was, and still is running fine on my old machine

Wind is your friend
Matt
www.elitemarquees.com.au

Did you see this one:

http://support.microsoft.com/default.aspx/kb/315456

I checked my %temp% variable and indeed it points to
C:\Documents and Settings\[username]\Local Settings\Temp

But that folder does *NOT* give IIS or EVERYONE any permissions at all. So I dunno how much to rely on that KB article.

WHOOPS! NOT TRUE!

For my *OWN* user, that is the path to my %temp% folder.

But for System Variables, which is what would be used by IUSR_xxxx the path is simply
    c:\TEMP
and there indeed EVERYONE has write permissions.

Dunno if that helps, but worth looking at?

I have given Everyone full access to my personal and ensured this is present in the c:temp dir also.

After the registry permission change which resulted in:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.

I restarted my machine, no change. in your opinion is the above error made my issue worse? Wow really stuck now...



Wind is your friend
Matt
www.elitemarquees.com.au