If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

RESOLVED: Report Failing in an Event within an Event

Started by adam_mc, 13 Nov 2019 12:30:21 PM

Previous topic - Next topic

adam_mc

CA 11.0.13 (recently upgraded from Cognos BI 10.2.2):

In Event Studio, we have Event A that kicks off Event B that runs an Active Report that is emailed to the business via a DL.
This is failing with the following message:

RSV-DST-0019 This output format is not supported for an IBM Cognos Active Report.

Note: The report output is set to HTML.

However, if we run the report on its own it runs successfully.
Also, if we run Event B only, the report again runs successfully.

Why would it fail when it runs in an Event within an Event scenario?

Any thoughts would be greatly appreciated.
Thanks in advance,
Adam.

adam_mc

#1
Update - The plot thickens...

We now pulled Event B out of Event A and scheduled Event B to execute on its own.
However, now that it is scheduled, Event B fails at the same report with the same error message "RSV-DST-0019 This output format is not supported for an IBM Cognos Active Report".

Again, we are able to run the Event interactively successfully.

In fact what we are seeing is that potentially all our Events that are scheduled fail, but all run successfully interactively.
Is there anything different between scheduling events in 10.2.2 vs. 11.0.13.
I know Event Studio is a legacy tool now, but our expectation was that it would work in CA 11.0.13.

Any thoughts?
Thanks in advance,
Adam.

adam_mc

We were able to resolve this issue by scheduling the agent within the Event rather than scheduling the Event itself.

Intuitively, this makes more sense to me, but we are unsure if this is the way it should always have been done (and that it was a quirk in Cognos BI 10.2.2 that scheduling the Event worked) or if this is a change necessary in going to CA 11.0.13.

Thanks,
Adam.