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!
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!