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

 

Scheduled Cognos Report is not saving the report as an excel to the file system

Started by srinu1253, 18 Nov 2018 03:02:57 PM

Previous topic - Next topic

srinu1253

Hi,

I have created a report studio Cognos report and Scheduled it to save the report as an excel to a file system every day. But the Report is not saving as an excel to the file system consistently. How to troubleshoot this issue.

The Scheduler shows the same success message when it is saved or even for not saved.

thanks
Srinivas

Reinhard

Hi,

would check if the problem lies with the target location. Is it a network share? Try a local folder on the active content manager.

There are severyl deep logging options, IBM support could explain them.

Regards,
Reinhard

srinu1253

The network location is fine. The file has saved few days consistently but later it has failed.
I reviewed the Cognos Server Logs but It did not say why the report is not getting saved.


Thanks
Srinivas

srinu1253

The Scheduler to save the file is a daily schedule. But its not getting saved consistently. Can anyone suggest on this.


srinu1253

Hi,

I have figured out the scheduler is working fine. I am able to save the reports to the file system. But the issue is I have the dispatchers. So when the scheduler
gets activated the report is getting saved on the server associated to the dispatcher. How do I set for the report to get saved in one of the report server.


thanks
Srinivas

MFGF

Quote from: srinu1253 on 05 Dec 2018 12:34:40 AM
Hi,

I have figured out the scheduler is working fine. I am able to save the reports to the file system. But the issue is I have the dispatchers. So when the scheduler
gets activated the report is getting saved on the server associated to the dispatcher. How do I set for the report to get saved in one of the report server.


thanks
Srinivas

Hi,

The ideal solution is to use a single network folder that all servers (dispatchers) are configured to save to.

The alternative is to start using Routing Rules so that a single server handles all these requests, but then you lose your load balancing / failover capabilities for these reports.

Cheers!

MF.
Meep!

srinu1253

Problem is I cant sacrifice the load balancing capabilities just for this :)

MFGF

Quote from: srinu1253 on 06 Dec 2018 11:29:12 PM
Problem is I cant sacrifice the load balancing capabilities just for this :)

Hi,

As above, the ideal solution is to use a single network folder that all servers (dispatchers) are configured to save to. That way you don't sacrifice load balancing.

MF.
Meep!