Hi There, I am using Crystal Reports XI v2 on Windows XP in combination with Business Objects Enterprise on a Windows NT server and I had the same problem: Error in File C:\Filename.rpt: The request could not be submitted for background processing.
I had never seen this problem before and I have a fleet of Crystal Reports running on the Business Objects schedule perfectly ranging in complexity from simple to straight out confusing. This one report was working fine if exported to PDF however as soon as I tried to export it using CSV format then either my Crystal Reports would die or the BO scheduler would return the above error.
After searching a few forums I figured I should do some investigation of my own as this error potentially has multiple causes. I employed simple trial and error methodology. I generated the report in Crystal and saved the report file u2018with datau2019 so that when Crystal died I could open the report again and not have to rerun it (to save time). I started by u2018suppressingu2019 all the sections of the report except for the main section where all the data was contained and then tried exporting the limited report in CSV format and it worked. Thus the main section of the report was not the issue. One by one I unsuppressed each section and exported in CSV until I found the section which was causing the error.
The cause of the error was the section with all my sub-reports (one of the eight sub-reports)! So I employed the same method as above (suppressed all sub-reports, then unsuppressed each one in turn and exported CSV file to determine which sub-report was causing the error). Once I found the single sub-report that was causing the error I noticed that some of the values my sub-report was producing were NULL values and I suspected this was the cause. I removed the NULL values from the sub-report, re-imported it into the main report (linking it using the same field) and proceeded to export the file in CSV format. I then saved the Crystal Report to the BO server and triggered the schedule in CSV format and everything worked out fine. Success!
As it was all working I did not investigate further so do not know the true cause of the problem but I would advise trial and error investigation isolating different sections of the report to determine which is causing the problem, then either remove, replace or recreate this section.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.