database results error

our server was upgraded to win 2003 sever and now all database results are
not working, receive the following errors.

ADODB.Command error '800a0e7d'
The connection cannot be used to perform this operation. It is either closed
or invalid in this context.

C:\INETPUB\WWWROOT\DATABASE4_INTERFACE\RESULTS\../../_fpclass/fpdbrgn1.inc,
line 115

running fp 2002 sp3
publishing to local server in house
extensions have been updated

For starters, make sure you're running the FP 2002 server extensions and then
run Server Health (with all the Repair boxes checked) against at least all
the Web sites that contain problem DRWs.

Also, verify that all those Web sites are flagged as applications in IIS.

Then, if these are Access databases, check NTFS permissions to make sure the
folder that contains the database files grangs Change permission to the
account the Web server is using.

If that doesn't do it, try deleting and recreating the database connections.

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*-----------------------------Â*-----------------------
|\----------------------------Â*-----------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||----------------------------Â*-----------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/----------------------------Â*-----------------------
*-----------------------------Â*-----------------------


"phil" wrote:

> our server was upgraded to win 2003 sever and now all database results are
> not working, receive the following errors.
>
> ADODB.Command error '800a0e7d'
> The connection cannot be used to perform this operation. It is either closed
> or invalid in this context.
>
> C:\INETPUB\WWWROOT\DATABASE4_INTERFACE\RESULTS\../../_fpclass/fpdbrgn1.inc,
> line 115
>
> running fp 2002 sp3
> publishing to local server in house
> extensions have been updated

It could be the version of OLEDB32.DLL - check this post:
http://www.eggheadcafe.com/ng/micro.../post372728.asp

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/




"Jim Buyens" <news@interlacken.com> wrote in message
news:A9F3FF2D-2D33-4D4D-84F7-835DFE9F9751@microsoft.com...
> For starters, make sure you're running the FP 2002 server extensions and
> then
> run Server Health (with all the Repair boxes checked) against at least all
> the Web sites that contain problem DRWs.
>
> Also, verify that all those Web sites are flagged as applications in IIS.
>
> Then, if these are Access databases, check NTFS permissions to make sure
> the
> folder that contains the database files grangs Change permission to the
> account the Web server is using.
>
> If that doesn't do it, try deleting and recreating the database
> connections.
>
> Jim Buyens
> Microsoft MVP
> http://www.interlacken.com
> Author of:
> *-----------------------------*-----------------------
> |\----------------------------*-----------------------
> || Microsoft Windows SharePoint Services Inside Out
> || Microsoft Office FrontPage 2003 Inside Out
> ||----------------------------*-----------------------
> || Web Database Development Step by Step .NET Edition
> || Microsoft FrontPage Version 2002 Inside Out
> || Faster Smarter Beginning Programming
> || (All from Microsoft Press)
> |/----------------------------*-----------------------
> *-----------------------------*-----------------------
>
>
> "phil" wrote:
>
>> our server was upgraded to win 2003 sever and now all database results
>> are
>> not working, receive the following errors.
>>
>> ADODB.Command error '800a0e7d'
>> The connection cannot be used to perform this operation. It is either
>> closed
>> or invalid in this context.
>>
>> C:\INETPUB\WWWROOT\DATABASE4_INTERFACE\RESULTS\../../_fpclass/fpdbrgn1.inc,
>> line 115
>>
>> running fp 2002 sp3
>> publishing to local server in house
>> extensions have been updated

that was it, along with enable Parent Paths.
thanks to everyone for the help!

"Kathleen Anderson [MVP - FrontPage]" wrote:

> It could be the version of OLEDB32.DLL - check this post:
> http://www.eggheadcafe.com/ng/micro.../post372728.asp
>
> --
>
> ~ Kathleen Anderson
> Microsoft MVP - FrontPage
> Spider Web Woman Designs
> web: http://www.spiderwebwoman.com/resources/
>
>
>
>
> "Jim Buyens" <news@interlacken.com> wrote in message
> news:A9F3FF2D-2D33-4D4D-84F7-835DFE9F9751@microsoft.com...
> > For starters, make sure you're running the FP 2002 server extensions and
> > then
> > run Server Health (with all the Repair boxes checked) against at least all
> > the Web sites that contain problem DRWs.
> >
> > Also, verify that all those Web sites are flagged as applications in IIS.
> >
> > Then, if these are Access databases, check NTFS permissions to make sure
> > the
> > folder that contains the database files grangs Change permission to the
> > account the Web server is using.
> >
> > If that doesn't do it, try deleting and recreating the database
> > connections.
> >
> > Jim Buyens
> > Microsoft MVP
> > http://www.interlacken.com
> > Author of:
> > *-----------------------------Â*-----------------------
> > |\----------------------------Â*-----------------------
> > || Microsoft Windows SharePoint Services Inside Out
> > || Microsoft Office FrontPage 2003 Inside Out
> > ||----------------------------Â*-----------------------
> > || Web Database Development Step by Step .NET Edition
> > || Microsoft FrontPage Version 2002 Inside Out
> > || Faster Smarter Beginning Programming
> > || (All from Microsoft Press)
> > |/----------------------------Â*-----------------------
> > *-----------------------------Â*-----------------------
> >
> >
> > "phil" wrote:
> >
> >> our server was upgraded to win 2003 sever and now all database results
> >> are
> >> not working, receive the following errors.
> >>
> >> ADODB.Command error '800a0e7d'
> >> The connection cannot be used to perform this operation. It is either
> >> closed
> >> or invalid in this context.
> >>
> >> C:\INETPUB\WWWROOT\DATABASE4_INTERFACE\RESULTS\../../_fpclass/fpdbrgn1.inc,
> >> line 115
> >>
> >> running fp 2002 sp3
> >> publishing to local server in house
> >> extensions have been updated
>
>
>