Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users! 


#Product
#Analytics
#CognosAnalytics
#Analyticstools
#TechXchange Partner
#TechXchange Session
#TechXchange Presenter
#AI
 View Only
  • 1.  Wrong report version

    Posted 08/04/20 03:46 AM

    After upgrading from Cognos Analytics 11.1.4 to 11.1.6 we encounter errors on several reports. 

    'The report version "http://developer.cognos.com/schemas/report/15.4/" is not supported.
    Expected report version "http://developer.cognos.com/schemas/report/15.3/". '

    What have we done wrong? 




    ------------------------------
    Ber Hommelberg
    a.s.r.
    Netherlands
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: Wrong report version

    Posted 08/04/20 07:08 PM
    Hi,

    Did you upgrade your Cognos Gateway installation?

    ------------------------------
    JEAM COELHO
    Cognos Solution Architect

    Linkedin: https://www.linkedin.com/in/jeamcoelho/
    ------------------------------



  • 3.  RE: Wrong report version

    Posted 08/05/20 04:14 AM
    I have asked my collegue if he upgraded our Cognos Gateway installation and he says: yes.

    ------------------------------
    Ber Hommelberg
    a.s.r.
    Netherlands
    ------------------------------



  • 4.  RE: Wrong report version

    Posted 08/05/20 07:16 AM
    Hi Ber,

    My best guess would be that this is a multi-application server install and one was not upgraded. The reports that are failing are being processed by the one that is still on 11.1.4. The reports were upgraded so when they process on 11.1.6 they are ok.

    If you go to IBM Cognos Administration -> Status -> System, you can shut dispatchers down and determine which one is on 11.1.4 if you do not have server access.

    Cheers,
    Trevor

    ------------------------------
    TREVOR COMEAU
    ------------------------------



  • 5.  RE: Wrong report version

    Posted 08/06/20 05:52 AM
    Hi Trevor,

    Thanks. We have found the problem. 
    We have two servers and we could test them seperately by using the url http://[machinename]:[port]. Both worked fine. So it had to be the gateway part, like Jeam Coelho indicated. 
    Seems like the standard installation of an upgrade doesn't do the gateway-part and we had to do a custom installation for that. 

    After the upgrade I also had to delete my browsercache in Google Chrome (Ctrl-Shift-Del) to get it working. And now it looks fine.

    ------------------------------
    Ber Hommelberg
    a.s.r.
    Netherlands
    ------------------------------