Hello all. Have you submitted Support tickets to SAP Concur? We need to know that errors and issues are occurring in Cognos 11 so we can address them ASAP.
Error submitted but no update received till then. It is very painful to receive multiple complaints in the organization when something is beyond our control. What i am doing is keep trying to generate on others' behalf.
Our scheduled/Burst reports are being received blank by our users? Would appreciate some insight on next steps -- of course other that setting up a ticket!
I also sent you a message regarding this
@PDalal I know for scheduled reports, you need to re-authenticate your Cognos credentials. You should have received a push message from Cognos 11 pointing you to the release notes that describe the steps for re-authenticating your credentials.
I did re-authenticate my credentials on Cognos 11 as per directions given in the FAQ.
However one of the recipients of a burst report scheduled every morning at 5 am is a generic IT email and not a live person -- There is no Concur account associated/linked to this email
Hoping for some resolution.
@PDalal what impact is this having on the bursted report? Is the generic email the only email listed in the burst recipients? If not, are the other recipients receiving the bursted report?
My Company is also facing multiple issues with Cognos upgrade.
One of the major issue we are facing right now is with Bursting.
We have a report which bursts notification to employees, But that report is just processing few records and then going into stuck state.
The report eventually shows failed status after a day or more.
Any suggestions/insights on such issues.
This is the frequent error received.
RQP-DEF-0177 An error occurred while performing operation 'sqlOpenResult' status='-237'. UDA-TBL-0004 There was a Write error while processing a temporary file. UDA-SOR-0005 Unable to write the file.
Somehow so lose and dont know what to do.
Hi Kevin, thanks for reaching out. I have reauthenticated all reports individually. I have added my email manually to the burst reports and I see that some burst reports are received with no data/content in them. In fact I made a cheatsheet and distributed to area admins to authenticate their burst reports. A few Reports work just fine but others are a pain point -- I ran the reports in different ways but to no avail. I have attached screenshots of the error response received when trying to run reports manually. So I agree with JEdgar2022 its a disaster.
both scheduled reports and reports running manually encountered issues. We have informed everyone to renew the credentials and myself too. However, the failure rate is still high. The report that has always run without issues before the upgrade now always return error.
Our upgrade to Cognos 11 has been a disaster! Jobs keep failing with "server crash" errors; reports don't get emailed or the email shows up without the report attached; edits to jobs are not sticking. It has been a nightmare. Keep submitting tickets for support, but Concur refuses to respond. No idea where to even start since help is completely unavailable.
@JEdgar2022 could you provide me the case number you have from submitting support tickets, please? I have a person on the reporting team that wants to follow up.
@JEdgar2022 I'll pass the case numbers on to my colleague. I'm going to send him your email address that you have listed here as well.
@JEdgar2022 I wish I had an update for you, but the latest I've heard is that we are still working with IBM to correct the issues.