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

Failed to publish report to C. Server 2008 using publishing wizard

Status
Not open for further replies.

scb1776

Programmer
Dec 29, 2006
31
US
Hi,

We are using Crystal Report 2008 and Crystal Server 2008 (SP3)with an oracle 10 database.

Our system has 27 reports and 25 of them are properly loaded into Crystal Server when using the publishing wizard.
Development is done on a different machine and developers don't actually have access to the server area, so the reports cannot be saved to the server through the Save As command. I need to find a way to fix the report so that the Admins can publish it.

The two reports that fail produce the Reason: Unable to launch C:\ProgramFiles\BusinessObjects Enterprise 12.0\win32_x86\ReportAdd program to add to the system. However this is in the same batch of other reports which were successfully loaded.

These reports do have cascading dynamic prompts, complex formulas, and numerous sub-reports. Some of the reports which loaded successfully also have these items, however they do have fewer sub-reports. These are also out two largest reports (they file sizes are larger by about 10x most of our other reports)

Does anyone have any ideas about what could cause this? Is there a limit to the number of sub-reports that are allowed? I know that there is a limit to the depths to which they can be nested, but how about how many can be in a report? Is there an issue with large reports not importing into Crystal Server?

Thanks for any help.
 
I don't think the subreports are the issue - I think it's may be the cascading dynamic prompts, which are handled much differently when a report is just run through Crystal than when they're run through CRS or BusinessObjects.

In CRS and BO, cascading dynamic prompts are set up in the repository and then can be scheduled using the Business View Manager (that's what the List of Values job server handles!) so that the data is available without going to the database to get the prompt values every time a report using them is loaded.

Are you using the Administrator ID to log in using the publishing wizard or are you using another ID. If you're using a different ID, then you need to run the Business View Manager (BVM) and set up security so that the user id you're using for the Publishing Wizard has full control - this security is NOT set up in the CMC, it's specifically done in the BVM.

Something else to think about, the Publishing Wizard is primarily meant for publishing new reports. The last time I looked at it (XI r2) it would not overwrite existing reports. So, if you have to update an existing report, you will probably end up with multiple reports with the same name and '(2)' or another number at the end. A way to resolve both of these issues would be to have a copy of Crystal installed on a computer where it CAN connect to the CMS and publish your reports by opening them in Crystal and saving them to the CMS from there instead of using the Publishing Wizard.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.
 
Thanks for the help. We did take another look at the prompts. Unfortunately I don't have access to Crystal Server at all, under any user name, so I can't change the way that items are published.

For anyone else who has a similar issue we did find that there were some unused parameters in the report. They were not used by the filter, by the parameter prompt screen, or to display information. These were causing a problem.

Another problem we found was the way that parameters were defined in the sub-report. The sub-reports were designed as stand alone reports but were then incorporated into a larger report as sub-reports. Those parameters were changed from promting from the database to being associated with a value passed from the main report. Unfortunately they were still classified as dynamic parameters and that was also causing a problem. Changing these types of parameters allowed us to successfully import the reports.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top