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

BOE-XI (R2) - Custom database logon and “Linked Parameters”

Status
Not open for further replies.

MJRBIM

MIS
May 30, 2003
1,579
CA
BOE-XI (R2) - patched with SP-1, MHF-1 and CHF-15.

Main Crystal report and embedded Sub-report have “Linked Parameters”.

Report in BOE-XI (R2) uses Custom database logon to a different Oracle source rather than the Original database logon.

Report FAILS when accesed via View-On-Demand or Scheduled in BOE-XI (R2).

ERROR = "The request could not be submitted for background processing."

Report runs fine when the ORIGINAL database logon is updated to the new database, rather than using the Custom database logon function in BOE-XI (R2).

However, this does not meet our needs for report "Source Control" as we have to maintain multiple copies of the same report files each pointing to a different Oracle database.

If you see the old CE-10 KBase Article ID: c2017286


...it says that this EXACT issue was tracked and fixed in CE-10 under ADAPT00387704.

Has this old CE-10 issue returned in BOE-XI (R2), and is there a fix...?

Anyone seen this in BOE-XI (R2)..?

Thanks in Advance for the Help!
 
Can you get the report to run by setting up 'custom info' to point to the ORIGINAL data source?

 
ERROR "The request could not be submitted for background processing" still happens if the 'custom info' is set-up to point to the ORIGINAL data source?

The issue appears to be with the way BOE-XI (R2) handles the CUSTOM DATABASE LOGON if you use linked parameters.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top