Unable to open registry key 'Temporary (volatile) Jet DSN

[Laphan]

Hi Guys

I was wondering if you could help.

Basically I have an ASP page that inserts details from a standard form into
an Access DB and even though this is 'run of the mill' stuff, I've got a
problem I just can't fathom.

I can query this DB fine, but everytime I try and insert or update it, I get
the following error message:

Microsoft OLE DB Provider for ODBC Drivers error '800401f3'

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

/news-submit.asp, line 307

My ISP said that it has to be something I'm doing in my code, but I've had a
good look and can't
see anything to generate it from my end.

To cement this fact, I actually uploaded the DB and ASP pages to a different
ISP (FastHosts) and everything works fine.

I know this now makes it obvious that the problem is at my current ISP's
end, but could you give me some idea as to why this is the case so that I
can prove to and assist them in getting this sorted ASAP.

Thanks

Laphan

[Aaron Bertrand [MVP]]

[url]http://www.aspfaq.com/search.asp?q=volatile+80004005[/url]

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]




"Laphan" <news@DoNotEmailMe.co.uk> wrote in message
news:uERmCGo7DHA.3804@tk2msftngp13.phx.gbl...

> Hi Guys
>
> I was wondering if you could help.
>
> Basically I have an ASP page that inserts details from a standard form

into

> an Access DB and even though this is 'run of the mill' stuff, I've got a
> problem I just can't fathom.
>
> I can query this DB fine, but everytime I try and insert or update it, I

get

> the following error message:
>
> Microsoft OLE DB Provider for ODBC Drivers error '800401f3'
>
> [Microsoft][ODBC Microsoft Access Driver]General error Unable to open
> registry key 'Temporary (volatile) Jet DSN for process 0xd64 Thread 0x18c
> DBC 0xa488024 Jet'.
>
> /news-submit.asp, line 307
>
> My ISP said that it has to be something I'm doing in my code, but I've had

a

> good look and can't
> see anything to generate it from my end.
>
> To cement this fact, I actually uploaded the DB and ASP pages to a

different

> ISP (FastHosts) and everything works fine.
>
> I know this now makes it obvious that the problem is at my current ISP's
> end, but could you give me some idea as to why this is the case so that I
> can prove to and assist them in getting this sorted ASAP.
>
> Thanks
>
> Laphan
>
>

[Laphan]

Dear Aaron

As the ISP is now going mad setting permissions for everything and other
pages and DBs in the same area are working fine, is it a possibility that
something like ASPupload not being configured right on the server might
affect the page going through?

If you have the time, could you please go to the following web site, type
some dummy chars in all but the News Picture upload box and click the Send
button:

[url]http://www.haemophiliacs.org.uk/news-submit.asp?part=1&type=1[/url]

The page and DB worked fine on a different ISP (FastHosts), so the only
reason I can think of is that the ASPUpload section of code is the problem
because it is the only thing different between a page that works and the
page that generates this error.

A long shot I know, but both the ISP and myself are running out of ideas.

Rgds

Laphan


Aaron Bertrand [MVP] <aaron@TRASHaspfaq.com> wrote in message
news:eYkhGNo7DHA.3024@tk2msftngp13.phx.gbl...
[url]http://www.aspfaq.com/search.asp?q=volatile+80004005[/url]

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]




"Laphan" <news@DoNotEmailMe.co.uk> wrote in message
news:uERmCGo7DHA.3804@tk2msftngp13.phx.gbl...

> Hi Guys
>
> I was wondering if you could help.
>
> Basically I have an ASP page that inserts details from a standard form

into

> an Access DB and even though this is 'run of the mill' stuff, I've got a
> problem I just can't fathom.
>
> I can query this DB fine, but everytime I try and insert or update it, I

get

> the following error message:
>
> Microsoft OLE DB Provider for ODBC Drivers error '800401f3'
>
> [Microsoft][ODBC Microsoft Access Driver]General error Unable to open
> registry key 'Temporary (volatile) Jet DSN for process 0xd64 Thread 0x18c
> DBC 0xa488024 Jet'.
>
> /news-submit.asp, line 307
>
> My ISP said that it has to be something I'm doing in my code, but I've had

a

> good look and can't
> see anything to generate it from my end.
>
> To cement this fact, I actually uploaded the DB and ASP pages to a

different

> ISP (FastHosts) and everything works fine.
>
> I know this now makes it obvious that the problem is at my current ISP's
> end, but could you give me some idea as to why this is the case so that I
> can prove to and assist them in getting this sorted ASAP.
>
> Thanks
>
> Laphan
>
>

[Aaron Bertrand - MVP]

The volatile error is Access MDB-file related and has absolutely nothing to
do with ASPUpload not being configured.

If you create an identical ASP page in the same folder that accesses the
same database file and DOESN'T include a mention of ASPUpload, you'll get
the same error.

The articles on the site should cover all scenarios that I know of, so
either they're overlooking something, or they've discovered some new flaw in
Access/ASP that we've never seen before. I will repeat, this error has
absolutely nothing to do with ASPUpload.

Anyway, GET RID OF THE ODBC CONNECTION STRING ALREADY!!!! Use OLEDB!
[url]http://www.aspfaq.com/2126[/url]

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]




"Laphan" <news@DoNotEmailMe.co.uk> wrote in message
news:#DcpyuN8DHA.1548@tk2msftngp13.phx.gbl...

> Dear Aaron
>
> As the ISP is now going mad setting permissions for everything and other
> pages and DBs in the same area are working fine, is it a possibility that
> something like ASPupload not being configured right on the server might
> affect the page going through?
>
> If you have the time, could you please go to the following web site, type
> some dummy chars in all but the News Picture upload box and click the Send
> button:
>
> [url]http://www.haemophiliacs.org.uk/news-submit.asp?part=1&type=1[/url]
>
> The page and DB worked fine on a different ISP (FastHosts), so the only
> reason I can think of is that the ASPUpload section of code is the problem
> because it is the only thing different between a page that works and the
> page that generates this error.
>
> A long shot I know, but both the ISP and myself are running out of ideas.

[Laphan]

Promise I'll get rid of it now that you and Jeff have shown me the error of
my ways!!

Rgds

Laphan


Aaron Bertrand - MVP <aaron@TRASHaspfaq.com> wrote in message
news:#K#w23N8DHA.1592@TK2MSFTNGP10.phx.gbl...
The volatile error is Access MDB-file related and has absolutely nothing to
do with ASPUpload not being configured.

If you create an identical ASP page in the same folder that accesses the
same database file and DOESN'T include a mention of ASPUpload, you'll get
the same error.

The articles on the site should cover all scenarios that I know of, so
either they're overlooking something, or they've discovered some new flaw in
Access/ASP that we've never seen before. I will repeat, this error has
absolutely nothing to do with ASPUpload.

Anyway, GET RID OF THE ODBC CONNECTION STRING ALREADY!!!! Use OLEDB!
[url]http://www.aspfaq.com/2126[/url]

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]




"Laphan" <news@DoNotEmailMe.co.uk> wrote in message
news:#DcpyuN8DHA.1548@tk2msftngp13.phx.gbl...

> Dear Aaron
>
> As the ISP is now going mad setting permissions for everything and other
> pages and DBs in the same area are working fine, is it a possibility that
> something like ASPupload not being configured right on the server might
> affect the page going through?
>
> If you have the time, could you please go to the following web site, type
> some dummy chars in all but the News Picture upload box and click the Send
> button:
>
> [url]http://www.haemophiliacs.org.uk/news-submit.asp?part=1&type=1[/url]
>
> The page and DB worked fine on a different ISP (FastHosts), so the only
> reason I can think of is that the ASPUpload section of code is the problem
> because it is the only thing different between a page that works and the
> page that generates this error.
>
> A long shot I know, but both the ISP and myself are running out of ideas.