LBI, Crystal & subreport - LawsonGuru.com

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

RoxanneS

Basic Member

Posts: 12

11/11/2010 9:40 PM

Using Crystal 2008 and have a report with a subreport. When I open it up in Crystal, looks fine. I publish the report to LBI (9.0.4.0.192) and enter the parameters, then I get an error message back "Failed to retrieve data from the database". I tried deleting the subreport and publishing that to LBI and it works fine. Does LBI have some kind of issues with Crystal subreports?

The strange thing is, the users approved the report/subreport in LBI in October; so it worked then when it was pointed to the test server. No changes to the report except repointing the report from our test server to our production server. One idea someone has was that the datasources weren't right. When I open Set Datasource Location in Crystal, everything is pointing to prod including the SQL, however, it does give me a message "More than one datasource or a stored procdure has been used in this report". If it is really pointing to more than one datasource and that's the culprit, why does it work in Crystal but not in LBI??

Any ideas?

Thanks!!

Matthew Nye

Veteran Member

Posts: 514

11/12/2010 10:58 AM

Remember, running a report from the Crystal Report Editor isn't a valid test for running it in LBI since they use a completely different set of drivers.

What method are you using to connect to your RDBMS and what platform is it?

I assume you know you have to update the data source in your subreport as well as you main report.

Did you look in your websphere logs? Often they will give more verbose errors.

Hth,
Matt

-----Original Message-----
From: forums-epm-lbi@lawsonguru.com
Date: 11 Nov 2010 16:46:17
To:
Subject: LBI, Crystal & subreport [00008159:00000000]

Lawson Business Intelligence/Reporting/Crystal Forum Notification ---------------------------------------------------------------- Posted by:RoxanneS Date: 11/11/2010 04:40 PM Subject: LBI, Crystal & subreport Message: ---------------------------------------------------------------- Using Crystal 2008 and have a report with a subreport. When I open it up in Crystal, looks fine. I publish the report to LBI (9.0.4.0.192) and enter the parameters, then I get an error message back "Failed to retrieve data from the database". I tried deleting the subreport and publishing that to LBI and it works fine. Does LBI have some kind of issues with Crystal subreports?

The strange thing is, the users approved the report/subreport in LBI in October; so it worked then when it was pointed to the test server. No changes to the report except repointing the report from our test server to our production server. One idea someone has was that the datasources weren't right. When I open Set Datasource Location in Crystal, everything is pointing to prod including the SQL, however, it does give me a message "More than one datasource or a stored procdure has been used in this report". If it is really pointing to more than one datasource and that's the culprit, why does it work in Crystal but not in LBI??

Any ideas?

Thanks!! ---------------------------------------------------------------- To view the complete thread and reply via your browser, please visit: https://www.lawsonguru.co...i-crystal-subreport/ Thank you, LawsonGuru.com You were sent this email because you opted to receive email notifications when someone posted and/or responded to a message on this forum. To unsubscribe to this thread please visit your user profile page and change your subscription options.

Char

Veteran Member

Posts: 62

11/12/2010 11:49 AM

If Crystal thinks there are two connections and there aren't - go to datasource set location and set both of them at the same time - both the main and sub reports. This most often happens with OLEDB with SQL server

RoxanneS

Basic Member

Posts: 12

11/17/2010 8:49 PM

Thanks, Char! Going back to my test version and doing the datasource set locations all at the same time did the trick. Could have sworn that I did them all at the same time before, but guess I didn't since I got the error.