Job server - Query Engine error Custom db logon 1

[gooseriver]

Hopefully someone can help us out. We are using Crystal Enterprise 10 and the reports point to a SQL Server 2000 backend. Our report contains SP parameters.
example:
When the report is created the Data Source embedded in the rpt is 1234, we schedule using Use original database logon information from the report located under Process tab\database...
The report will run successfully and the data will appear on the report.

If we schedule using Custom database logon information, the report will fail with a Query Engine error. If I change the report from using an ODBC to OLE Driver for SQL server, the report will run but with no data on the report.

We need to generate batch reports and we thought using the job server is the way to go... Can anyone help us out here or make any strong recommendations!!!

 

[MJRBIM]

Are you using a sub-report via linked-parameters in the RPT...?

There is a known bug with using CUSTOM DATABASE logon with linked-parameters in BOE-XI (R2) which probably also effects CE-10.

I think in BOE-XI (R2) it gives a "background processing error".

The only work-around is to update the ORIGINAL DATABASE logon in the source RPT file. This issue has been reported to BOBJ support, but they couldn't give a timeline on a fix.

 

[gooseriver]

Thats correct, subreport with linked parameters. So if I need to change the DSN I will have to create a sperate report with each embedded dsn? What are you doing as a workaround?

 

[MJRBIM]

We had a developer write a custom .NET application that updates the the ORIGINAL DATABASE logon in the source RPT files on our BOE-XI (R2) infrastructure using the .NET SDK.

 

[gooseriver]

Using the job server? The parameters are read-only are they not?

 

[gooseriver]

With .net can you modify the CE10 job server?

 

[MJRBIM]

No, with .Net SDK you can open and update the object properties of the Report Objects and their Sub-Reports.

The other non-code option is to use the "Set Datasource Connection" for the Report Objects and their Sub-Reports in the desktop Crystal Reports tool, then do a "Save As" of the updated RPTs into the CE-10 environment.

 

[gooseriver]

In other words have a seperate report for each dsn?

 

[MJRBIM]

Yes, there is a different version of the same RPT-file for each ORIGINAL DATABASE setting.

In our case, it is for our DEV, TEST, and PROD databases. Which match-up to our DEV, TEST, and PROD BOE-XI environments.

When we post to PROD BOE-XI environment, we update the ORIGINAL DATABASE settings for each report object to the PROD database.

 

[gooseriver]

We are doing the same but this can be painful if you have several reports. Reports are duplicated for this reason..