I am getting following error:
Error in file .The request could not be submitted for background processing.
This is happening in Crystal Reports XIR2 after changing the Data Sources to Use custom database logon information specified here and Use same database logon as when report is run
We just changed from DEV ( Use original database logon information from the report) to QA ( Use custom database logon information specified here). These settings we have done through CMC.
We are using Oracle Database Procedures.
Any one has an idea why we are getting this error?.
Note: if we set the Prompt the user for database logon checked and while running it is asking the userid/password and the report runs fine
Does the dev database have the same schema owner (prefix) as the production db? If not, you need to be sure to set the Table Prefix. We usually use a custom prefix and set it to blank. However, all of our data is in a single schema so we don’t have any conflicts if we do that.
Did you find the solution? We are experiencing the same thing here and would dearly like to swat this bug.
We did not have this problem when we were a 1 server shop. The hardware was showing signs of imminent failure and I obtained a much larger and more powerful server - so much so that I was able to setup 3 virtual servers that are clustered (“a” runs Tomcat and other ‘support’ servers, while “b” and “c” run the report and related servers). That arrangement has worked well and I am very pleased with the performance. Segregating Tomcat from the reporting services has resulted in its remaining highly responsive even when the other 2 VMs are fully committed to running reports. That is a marked improvement over the old server where Tomcat became far less responsive when the maximum number of simultaneous reports were running.
We have been transitioning our clients from the old server to the new cluster a few at a time, coincident with a vendor database upgrade (killing two birds with one downtime). The old server is NOT clustered with the new, although both are on the same network segment and are fully visible to each other. The CMC of one recognizes the presence of the services (servers) of the others.
We are experiencing the “background processing” error on the cluster at approximately 2/3 of the way through the transition process. (I do not know if that is merely coincidence, or have we reached a tipping point?) We cannot add the old server to the new cluster because it has not been patched to the same level and the database drivers on it are different than those on the cluster (a consequence of the database upgrade). Since all the databases will be upgraded by the end of this month, it makes little sense to retrofit the hundreds of recurring instances to use designated server groups to ensure the right server (and hence, the right drivers) are used by each report. Once the upgrades are done, we will then be able to fully patch the old server, upgrade its database drivers, and add it to the cluster.
(BOB member since 2007-04-16)
(BOB member since 2009-07-30)