Cognos Analytics with Watson

 View Only
Expand all | Collapse all

Cognos Analytics 11.1.4 is not stable

  • 1.  Cognos Analytics 11.1.4 is not stable

    Posted Mon October 31, 2022 11:16 AM
    Hi Team

    we have only one content manager and 7 dispatchers. We started facing one issue in Content manager. It started negotiating and looking for secondary content manager. it is happening every 5 min since when content manager is up. so found server where content manager is stable. So later, we created copy of that server and started content manager there. It was up for a week and later it started facing same issue. 

    in Cogserver.log we saw below errors- 

    CM-REQ-4355;An error occurred while executing an asynchronous connector request.
    CM-REQ-2378 A request was received to start the negotiation process to determine

    Please help asap

    Anand Kulkarni


  • 2.  RE: Cognos Analytics 11.1.4 is not stable

    Posted Tue November 01, 2022 02:27 PM
    Hi Anand,

    For these kinds of things you should definitely open a support ticket with IBM.

    I would also suggest you look at upgrading to 11.1.7, which is the "stable" long-term release of the 11.1.x branch.  Current FixPack is 6.

    When we migrated from 11.0.13 we had a lot of issues with 11.1.2, 11.1.3 and 11.1.4.  I honestly don't remember now what those issues were but on 11.1.2 and 11.1.3 they were complete showstoppers.  We were just starting to test 11.1.4 when 11.1.5 came out and IBM support pushed us on that version instead of 11.1.5, with regards to the issues we were having with Events on 11.0.13 (our whole reason for upgrading to 11.1.x).  The only issue we ran into with 11.1.5 is they broke single-signon, so they gave us an Interim Fix (IF004) which we've been on since.  I'm sure that made it into the first FixPack for 11.1.5.

    We're currently testing 11.1.7 FP6 ourselves - the 11.2 branch has been too unstable for us and we might look at it next year then the 11.2.4 long-term release is pushed out and it's had a few FixPacks.

    Obviously, test the bajeezies out of any new release.  We've been surprised what can get broken and slip through IBM's QA/QC testing, so it's up to you to cover your butt with testing before going live, since there's no rolling back without data loss.



    Wayne Westlake