Re: 80004005 Unspecified Error
- From: "Dimitris Pantazopoulos" <DimitrisPantazopoulos@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 19 May 2005 05:41:06 -0700
It is very very true indeed.
First, I did not expect MVPs to argue over cute variable names ("cn" vs.
whatever) instead of trying to solve the problem. I can't believe you guys
made the man change his variable name just in case!
Second, I want to verify the occurance of the dreadfull 80004005 error when
connecting to Access databases from asp code.
* The error message usually is "unspecified error" (but not always).
* The error has nothing to do either with db authentication or badly written
code (mispelled connection strings etc).
* Prior to some windows and/or mdac update, OUR code worked just fine. Now
it just produces this error.
* It so happens that the same asp code may work today but not tomorrow or
the day after!!!
Third, I've tried the TEMP/TMP solution also suggested by QUE in this
thread. It worked just fine (I had to restart my win2000 server) TILL I
restarted the IIS. Then the problem appeared again!
* My configuration is: IIS 5 on Windows 2000. My database is Access 2000.
* Exactly the same asp code runs perfectly locally on my XP machine (with
IIS 5 again).
Last but NOT LEAST, obviously Microsoft does not really know how this
problem occured nor how to solve it. None of the msdn articles really
presents a final and deterministic solution.
My opinion is, it must be side-effect of some windows update.
There is really nothing we can do to solve this problem once and for all,
right ?
dp
"Bob Barrows [MVP]" wrote:
> que wrote:
> > I feel like I am in good company this week.
> > I was moving an application from one server to another when it broke.
> > Exactly same error message: Microsoft JET Database Engine error
> > '80004005'
> > Unspecified error
> > from the database connection line
> >
> > It had to be either a permissions problem or a driver issue since it
> > was
> > fine on the old server.
> > I double checked the permissions between servers - ok
> > I tried using a different connection string hoping it was the driver:
> > Conn.open "Driver={Microsoft Access Driver (*.mdb)};DBQ=" & dbpath
> > Got a different error: "[Microsoft][ODBC Microsoft Access
> > Driver]General
> > error Unable to open
> > registry key 'Temporary (volatile) Jet DSN for process"
> >
> > Found this website:
> > http://www.attention-to-details.com/newslog/38n-temporary-volatile-jet-dsn-for-process.asp
> >
> > The solution was the user who has modify rights on the .mdb must also
> > have
> > modify right to the system TEMP directory
> > Tried it - fixed
> > Switched back to original connection string - fixed
> >
>
> That's not true if you use the OLE DB provider for Jet, instead of the ODBC
> driver.
>
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"
>
>
>
.
- Follow-Ups:
- Re: 80004005 Unspecified Error
- From: Eiste Geloioi
- Re: 80004005 Unspecified Error
- From: Dimitris Pantazopoulos
- Re: 80004005 Unspecified Error
- From: Jeff Cochran
- Re: 80004005 Unspecified Error
- From: Mark J. McGinty
- Re: 80004005 Unspecified Error
- From: Bob Barrows [MVP]
- Re: 80004005 Unspecified Error
- Prev by Date: RE: Upgrading W2K3 Server to MSXML SP2
- Next by Date: Re: 80004005 Unspecified Error
- Previous by thread: Upgrading W2K3 Server to MSXML SP2
- Next by thread: Re: 80004005 Unspecified Error
- Index(es):
Relevant Pages
|