Can't refresh my reports - handleCrystalEvent failed

[ashleybyrdnc]

I am able to preview all of my reports in the CMC when you hit preview, But when I try to refesh any of my reports I am getting this error:

CrystalReportViewer

handleCrystalEvent failed

Unable to retrieve Object.
The database logon information for this report is either incomplete or incorrect.



I know that having parameters is not the issue, because I have some reports that do not have any.

I am using Microsoft SQL master database as my data source.

I also not able to schedule any of them.

Thanks

 

[hilfy]

Do you have the security rights in BO to refresh the data in the reports?

Are you not able to schedule or do they fail when you schedule? If they fail, click on the word "Failed" and see what the error message is.

Does the user ID that the BO services run under have access to the network location where your database resides? The default ID when BO is installed is a local services ID on the server - this is not a network ID so it doesn't have access to network resources. We use a dedicated network ID for all of the BO services in order to avoid this issue.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[ashleybyrdnc]

I am trying to run these reports as the Administrator. And the BO is installed on the same computer that the Microsoft SQL server is sitting on.

How do I change the BO ID to become a network ID?

 

[hilfy]

First off, I hope this is a dev/test environment and not your production environment - it's not recommended to have both on the same server because they compete for CPU time so they'll both run slower.

Even if you're running as Administrator, you need to check the access rights because it is possible to change the access rights for administrators (though it rarely happens.) If you assign rights at the folder level (best practice) you need to check them there otherwise check them for the report.

As far as getting an ID, you'll need to talk with the folks in your organization who provide regular user ID's. This ID need access to run the services on the server (I usually set the ID up as a member of the Administrators group in Windows on the server) and access the network locations where the data is located. It also needs to be set up so that the password doesn't expire - unless you want to manually change the password on a regular basis and chance having BO not work at all if the password expires.

If you're accessing the database through a UNC path, this is probably what you're problem is. If not, then you'll need to do some more troubleshooting. You didn't answer my question about not being able to schedule reports. If they're failing, what is the error message you see when you click on "Failed" for the instance?

_Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[ashleybyrdnc]

Here is the message when I try to schedule the report.

Status: Failed

Printer: The instance is not printed.

External Destination: Mail the instance to " test1@test2.com; test1@test2.com " with a subject of " test ".

Data Refresh Settings: Use the server defaults.

Start Time: 11/18/08 1:21:08 PM

End Time: 11/18/08 1:21:16 PM

Server Used: clr-combr.reportjobserver

Error Message: Error in File C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Data\procSched\clr-combr.reportjobserver\~tmp1304574d197a990.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 18456 ]


We had someone else install and set all this up for us, now they are of no help (contract Issues), so I am sort of doing this blind.


The user ID Should have access because I am using the adminstators login.

 

[hilfy]

What type of connection does your report use? The two types of connections available for MS SQL Server are ODBC and OLEDB. If it's ODBC, is the ODBC DSN set up on the server?

In the CMC, go to the report object and check the database login information to be sure that it's correct. If you need to update the information, select the custom connection option and set the correct information. Be aware that if you update reports by connecting to the CMS through Crystal, you will also probably have to update this information in the CMC after the update.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[ashleybyrdnc]

The ODBC information is set up correctly. If it wasn't it wouldn't let me view the report to begin with, correct?

Would BO be able to solve this problem if we purchased a one time Single Incident? We have never done that?

 

[hilfy]

If the report has "Save Data with Report" turned on, then you would be able to see the report with data without hitting the database. I would verify that the ODBC DSN is set up correctly. I would also go to the report in the CMC and verify that the login for the report itself is set up correctly.

BO support may or may not help with the issue in a timely fashion. I've had lots of trouble getting things resolved since SAP took over support - their first-line support staff doesn't always know much about BO.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.