Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unknown Database Error with XML

Status
Not open for further replies.

VibrantIce

Programmer
Mar 3, 2006
6
US
[highlight]It works fine in the desinger![/highlight]

We have a report that is using a HTTP data source (NOT a SOAP web service) that returns xml results which the report consumes. We point to an XSD for the schema. The report previews beautifully in the designer every time, no matter where the XSD resides. However, the report hangs when viewed via the BO web interface. It eventually times out after a very long wait (5-8 minutes). The results from the same query in the url always come back in under a second, so it isn't a data volume or processing issue.

I'm getting an error:
[highlight #FF99FF]An error has occurred: Request timed out.[/highlight]

The weird thing is that the history doesn't show that the report has ever been run.
HELP!!!

 
History only gets created when a report has been scheduled. Your post indicates that you're using "View on Demand". This will never create a historical instance.

As to the data source, I don't have any experience using the one you describe, but there are a couple of considerations.
When you're running the report from the designer, it's your account that has access to where the data resides.
When you've published the report to CE, it's the Page Server that's actually running the report, if you're using "View on Demand" (if using scheduling, it's the Crystal Report Job Server ).
These services are typically started using the Local System Account.
Try starting up these two services with your Domain account. (use the CCM to do this)
If this works, create a Doamin account that you can use for this purpose and set these services to use this new account.


Bob Suruncle
 
We reinstalled BO several times with the same patches, etc. as the legacy box. We installed a KB patch from BO that was NOT on the legacy box, and things suddenly started working.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top