Hi All,
When user try to open the report (Cognos v 10.2 1) user getting error with : content manager is unable to process your request because it is running in standby mode.
Please provide solution to reslove this and explain why this error msg coming.
Thanks,
Naga
Hi,
It sounds like you have an issue in the way you have configured your instance. I'd guess that you have a multi-server architecture with an active and a standby content manager? I'd guess you have at least two application servers and that one of them is configured to use the standby content manager? I'd also guess that the report or user/group is referenced in a routing rule that utilises this server?
Of course, all of this is conjecture on my part. You haven't told us any details about your architecture so I'm wearing my clairvoyance hat. It is wrong far more often than it is right :)
MF.
Hi,
I have encountered the same issue. Two different/own content managers URIs configured for each app servers. I started receiving this error since the recent restart and only for few reports. Also in the logs am seeing CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.. I red some where that first started server's CM will become primary and later the stand by. Is this correct? Any way to track why the active CM failed.
Thanks,
Sreekanth
Quote from: snagaboina on 02 Aug 2017 12:38:05 PM
Hi,
I have encountered the same issue. Two different/own content managers URIs configured for each app servers. I started receiving this error since the recent restart and only for few reports. Also in the logs am seeing CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.. I red some where that first started server's CM will become primary and later the stand by. Is this correct? Any way to track why the active CM failed.
Thanks,
Sreekanth
Hi,
Whichever content manager is started first is the primary. The one that starts subsequently is the standby. That's how things remain unless the primary stops/dies, at which point the standby becomes the primary. To see why the originaly primary cm failed, you'd need to look in cogserver.log on that specific server, although if it was a power outage the Cognos instance may not have had the chance to log anything.
Cheers!
MF.