Currently I was moved the worked fine ASP code from PWS to Windows 2000

server for testing purposes, but it failed to retrieve the database. It

showed  'General error Unable to open registry key 'Tempoarary (volatile)

Jet DSN for process'.

I've tried very hard to investigate the configuration on the IIS itself but

still unable to rectify the problem.

Appreciate if someone who can guide me to identify this problem.



thanks

Dillon

Don't use ODBC, use OLEDB instead and your error will go away:



http://www.adopenstatic.com/faq/whyOLEDB.asp

&

http://www.adopenstatic.com/faq/OLEDBConnection.asp



Cheers

Ken



----- Original Message -----

From: "Dillon" <bacsr@p...>

To: "ASP Databases" <asp_databases@p...>

Sent: Monday, November 20, 2000 11:24 PM

Subject: [asp_databases] Jet DSN Error





> Currently I was moved the worked fine ASP code from PWS to Windows 2000

> server for testing purposes, but it failed to retrieve the database. It

> showed  'General error Unable to open registry key 'Tempoarary (volatile)

> Jet DSN for process'.

> I've tried very hard to investigate the configuration on the IIS itself

but

> still unable to rectify the problem.

> Appreciate if someone who can guide me to identify this problem.

>

> thanks

> Dillon

My e-mail server went down and the Lyris List Manager put me on hold - any

replies you may have given to my message originally (repeated again below)

may not have got through.



If so could I ask you to re-send your reply to this query (no pun intended):



 >

 >Since an APPEND query is being used, I'm using the parameters collection

 >under ADODB.Command, so the lock parameters are not being called.

 >

 >No, I'm not using InterDev.

 >

 >What is actually happening:

 >

 >I'm attempting to append 16 records - SOME OF THE RECORDS ARE BEING

 >SUCCESSFULLY APPENDED before it comes up with the error message, but the

 >actual number of successful records varies each time (between 5 and 12!).

 >

 >This may be a clue - there are 2 tables being written to: and when the

 >JOIN relationship between the 2 tables is deleted the operation is ALWAYS

 >carried out successfully - which tends to eliminate the "database is still

 >being edited by something else" theory.

 >

 >Any further ideas ?

 >

 >regds

 >

 >Simon G

 >

 >

 >

 >At 11:21 17/11/00 +1100, you wrote:

 >>Are you opening recordsets with adLockPessimistic?

 >>

 >>Are you using InterDev?

 >>

 >>Cheers

 >>Ken

 >>

 >>----- Original Message -----

 >>From: <sgarstin@t...>

 >>To: "ASP Databases" <asp_databases@p...>

 >>Sent: Friday, November 17, 2000 6:04 AM

 >>Subject: [asp_databases] Oh no not again Error 80004005

 >>

 >>

 >> > When trying to add records to a database via an APPEND query using ASP I

 >> > keep getting the following message:

 >> >

 >> > Microsoft OLE DB Provider for ODBC Drivers error '80004005'

 >> >

 >> > [Microsoft][ODBC Microsoft Access Driver] Could not update; currently

 >> > locked by user 'admin' on machine 'DEFAULT'.

 >> >

 >> > /nss/asp/clienttojob_proc_new_recs.asp, line 293

 >> >

 >> >

 >> > The message occurs even when Access 2000 itself is closed. I am running

 >> > stuff locally under PWS (Win 98) so no one else is accessing the 

database.

 >> > The only clues are:

 >> >

 >> > a. This only happens when there is a one-to-many relationship join 

between

 >> > tables,

 >> > and

 >> > b. The only way to solve this appears to be to copy each table, query,

 >> > form etc.. into a new database WITH A DIFFERENT NAME.

 >> >

 >> > This is deeply worrying and it would be much better to solve the problem

 >> > than avoid it (how can I be sure this will not occur when the 

database is

 >> > copied on-line ?).

 >> >

 >> > Can anyone help ?

 >> >

 >> > regds

 >> >

 >> >

 >> > Simon G

 >> >

 >>

 >>

the error was remove when apply for the OLEDB as a data source, but it can

only

manipulate the database for a

certain period (after I had closed the browser and launch it again, the

error comes back) unless if I restart the IIS, again and again.

further on that, I open the windows explorer and look for the database where

I have reside in the web root directory by right click the properties and

giving the security permission,

and somehow the error was permanent removed.

thanks Ken, for make me the first moved by understanding why the OLEDB is

needed on IIS environment.



----- Original Message -----

From: Ken Schaefer <ken@a...>

To: ASP Databases <asp_databases@p...>

Sent: 21 November, 2000 12:40

Subject: [asp_databases] Re: Jet DSN Error





> Don't use ODBC, use OLEDB instead and your error will go away:

>

> http://www.adopenstatic.com/faq/whyOLEDB.asp

> &

> http://www.adopenstatic.com/faq/OLEDBConnection.asp

>

> Cheers

> Ken

>

> ----- Original Message -----

> From: "Dillon" <bacsr@p...>

> To: "ASP Databases" <asp_databases@p...>

> Sent: Monday, November 20, 2000 11:24 PM

> Subject: [asp_databases] Jet DSN Error

>

>

> > Currently I was moved the worked fine ASP code from PWS to Windows 2000

> > server for testing purposes, but it failed to retrieve the database. It

> > showed  'General error Unable to open registry key 'Tempoarary

(volatile)

> > Jet DSN for process'.

> > I've tried very hard to investigate the configuration on the IIS itself

> but

> > still unable to rectify the problem.

> > Appreciate if someone who can guide me to identify this problem.

> >

> > thanks

> > Dillon

>

>