vb.net - Intermittent Crystal Reports error "The request could not be submitted for background processing." -


We are running Crystal Reports on a Windows server with the .NET Framework 3.5 SP1 2008.

I have seen several reasons for general error "The request could not be submitted for background processing." On other forums, but they become repeatable due to the issue of a particular formatting with a particular report, and constantly impacting only one report.
We see this error with a stack trace below, intermittently.

  • This affects many of our separate reports.
  • This affects a particular report more often than other reports.
  • Once a report is affected, the same error will often appear in many reports at almost the same time eg. Next 10 minutes.
  • When (soon after) can do the same work standards as well as run reports to run again or application can be successfully report before restarting play May be again.

All of these work before without any problems. There is no change in the server or code, which seems to be the error. In the code behind for VB.NET

We had a hard time of it again breeding in the test environment and upgrade to the latest version of Crystal is absolutely not helped. Any help or suggestions that you may be able to solve this issue will be appreciated.


  "Request for background resource could not be submitted." CrystalDecisions.ReportAppServer.Controllers.DatabaseControllerClass.ReplaceConnection at CrystalDecisions.CrystalReports.Engine.Table.SetDataSource on CrystalDecisions.CrystalReports.Engine.ReportDocument.SetDataSourceInternal at CrystalDecisions.CrystalReports.Engine.Table.SetDataSource (object old connection, object newConnection object parameter field , Object Parameter field, Object CRDBOptionUseDefault) --- CrystalDecisionskReportAppServerkConvertDotNetToEromkThrowDotNetException (Exception e) at CrystalDecisionskCrystalReportskEnginekReportDocumentkSetDataSourceInternal (Object val, type) CrystalDecisions on --- inner exception end of the stack trace (val, type object) .CrystalReports.Engine.ReportDocument.SetDataSource (dataSet dataset) "user code"  

on Separate the report generation code.

Our final solution was to take that code that was preparing the report and to move it to its separate service. Our original service then calls our new crystal service with relevant parameters and crystal RPT file. This is clearly an expensive solution because it involves modifying all the report generation codes to call crystal service. Crystal Service error does not display the code not changed other than that, so we had only a few contacts can infer Crystal Report engine that caused the error and the environment within our application.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -