Comments on: Resolve BOE/CR Error “The Request Could Not Be Submitted for Background Process… http://www.dbuggr.com/milly/resolving-boe-cr-error-request-submitted-background-proce/ Share Knowledge & Be Rewarded Fri, 03 Feb 2012 23:13:48 -0600 http://wordpress.org/?v=2.8.6 hourly 1 By: milly http://www.dbuggr.com/milly/resolving-boe-cr-error-request-submitted-background-proce/comment-page-1/#comment-3611 milly Wed, 16 Jun 2010 04:12:37 +0000 http://www.dbuggr.com/milly/resolving-boe-cr-error-request-submitted-background-proce/#comment-3611 In my situation, we had to update the data source using Crystal Reports XI Release 1, then add the report to Business Objects Enterprise R2 SP3. We encountered the error "The request could not be submitted for background processing" when trying to preview the report. We are using Oracle database. There are two things you can try: 1. Get the latest service pack for your Crystal Reports. Check it out here: http://resources.businessobjects.com/support/additional_downloads/service_packs/crystal_reports_en.asp 2. If patching doesn't work, I found out that while you update the report, make sure you uncheck "File->Save Data with Report" option first before you save the report. This option actually eliminate the error for us. 3. You can try using ODBC instead Oracle to see if it works. In my situation, we had to update the data source using Crystal Reports XI Release 1, then add the report to Business Objects Enterprise R2 SP3. We encountered the error “The request could not be submitted for background processing” when trying to preview the report. We are using Oracle database. There are two things you can try:

1. Get the latest service pack for your Crystal Reports. Check it out here:
http://resources.businessobjects.com/support/additional_downloads/service_packs/crystal_reports_en.asp

2. If patching doesn’t work, I found out that while you update the report, make sure you uncheck “File->Save Data with Report” option first before you save the report. This option actually eliminate the error for us.

3. You can try using ODBC instead Oracle to see if it works.

]]>