CE10: Database Logon Issues

[tayloraw]

Has anyone experienced the problem below, since moving to CE10 from a previous version?

When running a report (using the Advanced DHTML viewer) the following error message is received:

"There was an error retrieving data from the server: Failed to retrieve initial report values. For example, the database information for this report could be incomplete or incorrect. This is a configuration problem. Please contact your system administrator"

Running the same report (but this time using the ActiveX viewer) a similar error message is received:

"The database logon information for this report is either incomplete or incorrect [On Cache/PageServer xxxxxx]"

This is driving me nuts, as some reports work and some don't! I know I have the correct database logon information as the report in question works perfectly well in my old V9 installation (which I am now thinking of reverting to!).

Many thanks!

 

[ShortyA]

Are you able to view the report through the normal DHTML viewer ? In the Crystal Management Console is there definitely database logon information for that report ? Also, whilst in the CMC click on the Properties tab for one of the problem reports and then click on the Preview button. Do you get any error messages ?

Hope this helps a little to narrow down the options.
ShortyA

 

[gluik]

It works with me when y let the databasefield empty at:
Use original database logon information from the report tab.

 

[sh4kil]

Make sure the ODBC DSN has been created

Give a username and password in CE to connect with using the named DSN

Also, does the report contain any parameters as the import facility is not that great and default values seem not to migrate. Check under Parameters.

 

[dmvspt]

On the Process tab, do you have the "Prompt the user for database logon when viewing" checked? You may want to try using a generic user account that you put under "Use original database logon information from the report" which has access to the database. Uncheck the "Prompt the user..." box and Update. Then go to the Properties tab and uncheck "Default Database Logon Information." If this box is checked, then when the report is modified, it will remove the password under the Process tab for the database logon information.

Also, you mentioned that it worked with the Database field empty. Ensure that your Data Source is correct.

 

[khartman]

tayloraw,

I am experiencing a very similar issue. We are running CE10 and I have a number of on-demand reports with/wo parameters which runs against Lotus Domino, Oracle, SAP, and MSSQL. The reports execute fine when the user is using the ActiveX, DHTML or Java viewers. As soon as the viewer is switched to ADHTML the "There was an error retrieving data from the server: Failed to retrieve initial report values. For example, the database information for this report could be incomplete or incorrect. This is a configuration problem. Please contact your system administrator" error appears.

I'm sure it has something to do with the RAS since that is what the ADHTML viewer uses instead of the Page/Cache servers.

Anyone else have this problem?

--Ken

Kenneth Hartman
Manager, EIS
Hughes Network Systems

http://www.hns.com

 

[sh4kil]

We made sure the Database Logons had passwords and also Parameters tab had default values. Then it worked.

 

[joemc3]

I'm also having the same exact problem Khartman is experiencing. The usernames and passwords are correct and all reports work fine when viewed with the ActiveX, DHMTL or Java viewers. The ADHTML viewier gives the "error retrieving data from the server" message. Why do I care about the ADHTML viewer? Because the Crystal AdHoc Reporting tool uses the ADHTML viewer exclusively.

Additionally, I reboot the RAS server, I might get good ADHTML viewing of one or two reports, while the remainder of my reports give the error message. Once the error message comes up, it seems that the one or two reports that did work sometimes stop working, sometimes not. Finally, another reboot of the RAS server may fix those reports that were previously broken, but break those reports that previously worked. It's very random (and very frustrating)