Stange behaviour with Database Results Wizard - FP2003.

[David Martin]

Since upgrading from FP2000 to FP2003 I have a problem that ALL
pages using the database results stop working after a server reboot.

The server is a Windows 2000 server (with all SP's and fixes to date) also
running SQL Server 7.0 (with latest SP). [It's a homeserver].FPserver
extensions2002 are installed.

The databases are defined as machine data sources on the server and use NT
authentication. No log entries are found for the failures in either SQL
Server or Windows 2000 logs. Security fails are set to be logged.

The database results are returned to the client as:
Database Results Wizard Error
The operation failed. If this continues, please contact your server
administrator.

One long query for sure has done the select as a lot of diskactivity occurs
on the server.

Now if I go to the page with FP and edit the database results properties
(changing nothing) and save the page -all pages work fine - yes even ones in
other pages / using other OBDC connectors and databases. (the edit can
either be done on the client or the server.)

I am not sure where the problem is - so please excuse the cross post to both
the client & extensions group.

David.

 

[Kevin Spencer]

I am not sure where the problem is - so please excuse the cross post to
both

the client & extensions group.

For future reference: Cross-posting is frowned upon and bad Netiquette.
History is littered with the failures of those who have found their own
custom "exceptions" to established courtesies.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Since upgrading from FP2000 to FP2003 I have a problem that ALL
pages using the database results stop working after a server reboot.

The server is a Windows 2000 server (with all SP's and fixes to date) also
running SQL Server 7.0 (with latest SP). [It's a homeserver].FPserver
extensions2002 are installed.

The databases are defined as machine data sources on the server and use NT
authentication. No log entries are found for the failures in either SQL
Server or Windows 2000 logs. Security fails are set to be logged.

The database results are returned to the client as:
Database Results Wizard Error
The operation failed. If this continues, please contact your server
administrator.

One long query for sure has done the select as a lot of diskactivity occurs
on the server.

Now if I go to the page with FP and edit the database results properties
(changing nothing) and save the page -all pages work fine - yes even ones in
other pages / using other OBDC connectors and databases. (the edit can
either be done on the client or the server.)

I am not sure where the problem is - so please excuse the cross post to both
the client & extensions group.

David.

 

[David Martin]

O.K.- but which group would you have posted 2 ?

David

I am not sure where the problem is - so please excuse the cross post to both
the client & extensions group.

For future reference: Cross-posting is frowned upon and bad Netiquette.
History is littered with the failures of those who have found their own
custom "exceptions" to established courtesies.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Since upgrading from FP2000 to FP2003 I have a problem that ALL
pages using the database results stop working after a server reboot.

The server is a Windows 2000 server (with all SP's and fixes to date) also
running SQL Server 7.0 (with latest SP). [It's a homeserver].FPserver
extensions2002 are installed.

The databases are defined as machine data sources on the server and use NT
authentication. No log entries are found for the failures in either SQL
Server or Windows 2000 logs. Security fails are set to be logged.

The database results are returned to the client as:
Database Results Wizard Error
The operation failed. If this continues, please contact your server
administrator.

One long query for sure has done the select as a lot of diskactivity occurs
on the server.

Now if I go to the page with FP and edit the database results properties
(changing nothing) and save the page -all pages work fine - yes even

ones

in
other pages / using other OBDC connectors and databases. (the edit can
either be done on the client or the server.)

I am not sure where the problem is - so please excuse the cross post to both
the client & extensions group.

David.

 

[David Martin]

Thank you for your reply,
after much testing & reboots I find that I get the following consistantly,
with debug mode on

Database Results Wizard Error
Description: Class not registered
Number: -2147221164 (0x80040154)
Source: Provider

If I edit the Results of the DB reuslts wizard with FP then (without
changing anything) - I get a the correct result - without saving the file.

Can anyone undersatnda this ?

David.

O.K.- but which group would you have posted 2 ?

David

I am not sure where the problem is - so please excuse the cross post

to
both

the client & extensions group.

For future reference: Cross-posting is frowned upon and bad Netiquette.
History is littered with the failures of those who have found their own
custom "exceptions" to established courtesies.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Since upgrading from FP2000 to FP2003 I have a problem that ALL
pages using the database results stop working after a server reboot.

The server is a Windows 2000 server (with all SP's and fixes to date) also
running SQL Server 7.0 (with latest SP). [It's a homeserver].FPserver
extensions2002 are installed.

The databases are defined as machine data sources on the server and

use

NT ones to
both