Database Results Wizard: ALL Custom queries are now failing

[Paul Hahn]

Regular queries against existing database structures work
fine. However, when I attempt to use a custom query,
choose Edit, type in the SQL statement, verify: OK, it
doesn't display on the page. I get the following error
for EVERY custom query defined throughout the entire web
site:

Database Results Wizard Error
The operation failed. If this continues, please contact
your server administrator.

This happened recently, and there weren't any global
changes made that I am aware of. If you have seen this
happen before and have a way to fix it, please let me
know. I've attempted to re-do one of the DRW sections by
removing it and re-entering it, but still the problem
remains.

Thanks!

 

[Exiled Canuck]

I'm experiencing the same problem. Only known change in my
configuration was the upgrade to FP 2003. My server side config has
not changed, but all custom queries have now stopped working. Eroor
message reads:

"Database Results Wizard Error
The operation failed. If this continues, please contact your server
administrator."

Any Ideas Anyone?

 

[John]

I am also having the same problem.

I edited the page with FP 2000 and republished it and got the following
message:

Database Results Wizard Error
Your page contains a query with user input parameters that could not be
resolved.
This could happen if your DatabaseRegionStart webbot has an empty or missing
s-columnnames or s-columntypes attributes.
You may need to read Microsoft Knowledge Base Article 817029.

MS Article 817029 does not exist.

Any suggestions from anyone???

 

[Cliff Missen]

All,

Several programmers with my group have run into similar problems:
immediately after updating to FP2003, queries that have worked
perfectly fine for months have gone awry. It seems (although I'm not
entirely sure) that the problems start when we open pages for editing
and then save them under FP2003. Whether or not we edit the DRW, the
queries return the following error message.

"Database Results Wizard Error. Your page contains a query with user
input parameters that could not be resolved..."

Here's an additional observation:

When the WHERE clause of my errant query reads:

WHERE (Event.Program=':rogramID::')

and I pass in the parameter ProgramID=5, the query fails.

Now, if I replace the parameter in the query with the integer

WHERE (Event.Program=5)

.... the query works.

So I know this is the line that is giving me the grief.

If I change the query to use a text field in the same table, it works.
As in...

WHERE (Event.EventName='::EventName::')

Now I go into my database and I create five records with EventNames of
progressively larger size. ("B", "Bo", "Bog", "Bogu", and "Bogus".

The first four values fail when used as the "EventName" parameter.
Only the one with five charecters works. This supports another
poster's observation that longer values appear to work. It also
points to the back-end files as the culprits.

Has anyone heard of a fix for this?

-- Cliff