This Readme document contains late-breaking NoticeCast issues. However, there were no known issues related to notification services when this document was published.
Note: The NoticeCast component is not used with Cognos 8.
Look here for readme information about closely-related components:
The Readme document also contains information about Features No Longer Supported in this release and those that will not be supported in subsequent releases.
To see Readme updates and information about deploying Cognos Enterprise Business Intelligence products, go to the Cognos support site (http://support.cognos.com).
Having a mixed install of Series 7 Version 3 (7.3) MR2 BI products and/or Cognos Planning or Cognos Finance 7.3 SP3 on the same computer as earlier releases of these 7.3 products may cause these earlier releases to fail. The problems occur due to backwards compatibility issues found in the following components: UDA, XALAN and Cognos Web Services (CWS) with Cognos Visualizer.
Note that you will not have these problems if the products on the same computer are all at 7.3 MR2 and SP3 level, or if you install 7.3 MR2/SP3 products on one computer and have other products running 7.3 pre-MR2 or pre-SP3 on a different computer. For example, having Upfront and PowerPlay 7.3 MR2 on MyServerA, drilling through or launching an IWR 7.3 MR1 report on MyServerB will not cause a problem.
If you cannot follow the corrective actions described below, then you must revert all products on the computer to their previous state by restoring them from the backup you made before installing the MR2 maintenance release or SP3 service pack.
The UDA problem may be experienced by the products in Table A, when only a subset of the installed products is upgraded to MR2 or SP3.
The symptoms experienced are varied - there is no common message that identifies the problem. Before working with Customer Support to isolate your specific problem you must eliminate this known UDA issue as being the root cause. Examples of symptoms that have been encountered with 7.3 pre-MR2 products include, but are not limited to:
The build numbers of the UDA component causing the problem are in the range 7.8.23148 to 7.8.24101. To check build numbers, review the contents of your cmplst.txt file located in the <install_location>\cognos\cer4 directory. UDA component build numbers can be found in the [Services] section of cmplst.txt. Note that this is only an issue if there are any products or components in the file that have a 7.3 pre-MR2 or pre-SP3 version.
To resolve this issue you must:
The XALAN problem will be experienced by the products in Table B1, when any of the products in Table B2 are upgraded to MR2 on the specified platforms.
The symptoms experienced depend on the upgrade scenario.
If PowerPlay Enterprise Server 7.3 is kept at the Initial or MR1 level, and any of the previously listed products in Table B2 is upgraded to MR2, then accessing a cube from Cognos PowerPlay Web Explorer using the Enhanced UI may either result in a blank screen or the following message:
Internal error - request failed.
Please contact your administrator
If Cognos Visualizer Server 7.3 is kept at the Initial or MR1 level, and any of the previously listed products in Table B2 is upgraded to MR2, then a Visualizer message is displayed:
Web Browser:
There was an error in the XSL Parse engine.
The return code was: -1
The data returned was:
The error occurred during loading the stylesheet (/viz/templates/en/ZFPIndexPage.xsl), please ensure the stylesheet is valid
Please contact your administrator
Table of Content:
There was an error in the XSL Parse engine.
The return code was: -1
The data returned was:
The error occurred during loading the stylesheet (TOC.xsl), please ensure the stylesheet is valid
Please contact your administrator
The build numbers of the XALAN component causing the problem are in the range 1.2.659 to 1.2.868. To check build numbers, review the contents of your cmplst.txt file located in the <install_location>\cognos\cer4 directory. XALAN component build numbers can be found in the [Third Party] section of cmplst.txt. Note that this is only an issue if the file also contains a pre-MR2 7.3 version of PowerPlay Enterprise Server or Cognos Visualizer Authoring or Server.
To resolve this issue you must request from Customer support a new post-MR2 hot site build for all the products in Table B2 that you want to upgrade to MR2.
The CWS problem will be experienced by the products in Table C1, when any of the products in Table C2 are upgraded to MR2 on the specified platforms.
Cognos Web Services, only when used with Cognos Visualizer Server |
The symptoms are experienced when Cognos Visualizer Server 7.3 is kept at the Initial or MR1 level, and any of the previously listed products in Table C2 is upgraded to MR2. The error messages displayed are dependent on the platform as follows:
On HP-UX the following message is displayed when you configure:
configcp ->/usr/lib/dld.sl: Unresolved symbol: XML_ParserCreateNS (code) from ./libvizxml.sl core file from 'vizwebcws' - received SIGABRT configcp ->/usr/lib/dld.sl: Unresolved symbol: XML_ParserCreateNS (code) from ./libvizxml.sl core file from 'vizwebcws' - received SIGABRT
On Solaris the following message is displayed when you run some CWS requests:
Application Error
The following error has occurred:
The request failed because the server timed out. No Query Processor was available to handle the request.
The build numbers of the Visualizer Server Dispatcher or Query and Report Processor components causing the problem is in the range 600 to 1005. To check build numbers, review the contents of your cmplst.txt file located in the <install_location>\cognos\cer4 directory. Visualizer Server component build numbers can be found in the [Main Applications] section of cmplst.txt.
To resolve this issue you must request from Customer support:
You will not experience this problem if you have a mixed install of RTM/MR1 and MR3 or MR2 and MR3.