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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database prompt & report failure from enterprise but not otherwise

Status
Not open for further replies.

wimkotze

Programmer
May 23, 2003
2
ZA
Hello all,

In my setup, I used to view my reports on the intranet via enterprise. The reports still work when I view them directly from the Crystal report editor, also after I use "verify database".
However, if I add or re-add anyone of them to Crystal Enterprise (including setting the db details in the database tab for each to the same as on the report itself), and call them from csp, they come up with the database prompt, which does not accept the details I enter.

It appears as if the database is not recognised from CE. By they way, I use Crystal 8.5.0.217 with Oracle 8i, using an ODBC connection. The same problem also occurs with the simplest of test reports that I've now created. They work fine when previewing from crystal, but won't work when called using the CRViewer object in CSP.

Experienced this before. I'll be very thankful if anyone can help..

thks, Wim
 
This is usually a permission problem on the server.

I use a standard ODBC connection for dev and on the CE box rather than Windows Authentication.

A simple way to test this is to open the report using CR on the CE server and see if it runs.

-k
 
Thanks, k, for the suggestion.
I have standard ODBC connections. I tried using different drivers (for Oracle). I now use an "Oracle ODBC driver" instead of a "Microsoft Oracle driver".

The problem now is that each time I try to open a report it complains that the page server has gone down. I then restart the page server (I've also tried restarting all the CR services) but the problem persists. I also re-installed these services.

One of my colleagues suggested that the only way to get around this might be to re-install CE, and re-add all the reports (quite a mission on this site). Any suggestions before I resort to that?

thanks

Wim
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top