Attempting to install Cognos BI 10.1 Fix Pack 1 may result in error if certain interim fixes are already installed

Problem(Abstract)

In instances where a Cognos BI 10.1 Interim Fix with a build number 10.1.4707.1055 to 10.1.4705.1077 has been applied, an error will occur during the installation of Fix Pack 1.
Symptom

This product is incompatible with your previously installed version.
Please choose another directory.
Resolving the problem

The cmplst.txt file for Cognos BI 10.1 interim releases within the build range 10.1.4707.1055 to 10.1.4705.1077 include two extraneous entries. The addition of these entries will result in an installation error upon performing any subsequent Cognos BI 10.1 interim or fix pack installations.

If the extraneous entries are present in the cmplst.txt file, the IBM Cognos 10 installer will fail with the following error at the Installation Location screen.


To correct this situation:

1.Locate the cmplst.txt file within the IBM Cognos install directory.
2.Create a backup copy of the cmplst.txt file
3.Open the cmplst.txt file using an editor of your choice.
4.Within the cmplst.txt file locate and remove the two lines that begin with ECLIPSEEQUINOX361_version and ECLIPSEEQUINOX361_name.

The following is an example of the two extraneous entries taken from a cmplst.txt file from a 32 bit Microsoft Windows install.

ECLIPSEEQUINOX361_version=ECLIPSEEQUINOX361-AW32-ML-RTM-.-ECLIPSEEQUINOX361_name=Eclipse Equinox
5.Save the changes to the cmplst.txt file and exit the editor.
6.Launch the installer and begin the installation.

Comments

Post a Comment

Popular posts from this blog

RSV-VAL-0032 expression is not valid. If the item exists in a query but is not referenced in the layout, add it to a property list. CRX-API-0005 An error ocurred at or near the position '0'.

Image
Problem: RSV-VAL-0032 The following expression is not valid: [AdjRowsReturned] = 0. If the item exists in a query but is not referenced in the layout, add it to a property list. CRX-API-0005 An error ocurred at or near the position '0'. The variable named '[AdjRowsReturned]' is invalid Resolution: You might have used the calculated data item in the variable, which needs to be added in the page properties. - Click on the page and go to properties. Make sure you see 'page' on the top of the properties. - Click on properties icon under data section, you'll get pop up icon - Check mark the data item which is used for variable calc. You are good to go.Find the snapshot. .
Read more

How can you extract all user information from Cognos Access Manager Namespace Report Utility and create Cognos Report out of it?

The AM_NamespaceReport Utility allows you to extract the namespace to an XML file. 1. Use the AM_NamespaceReport Utility to extract all users from the namespace to an XML file. am_namespacereport -h << host >> -p << port >> -r << basedn >> -n << namespace >> -D << username >> -w << password >> -f all -o << path to filename.xml >> e.g am_namespacereport -h cognoscamsevr -p 4004 -r o=cognos.com –n devcam -D admin -w admin -f all -o c:\temp\usrlst.xml 2. This will extract all user information to an XML file 3. Import the xml file into XLS spread sheet 4. Create ODBC connection using the ms-excel spread sheet driver 5. Create Data Source Connection and proceed creating FM Model & Publish 6. Create Report using Report Studio. 7. Save & Share the report The Access Manager Administration Guide (Appendix A) contains further information on this functionality.
Read more

BME-EX-0047 Unable to read preferences for the requested interface..

Issue When opening or creating a Framework Manager project the following error message is shown. Additionally, when attempting to create or open a report based on a package is made in Report Studio or Query Studio, the same error message is shown. Error BME-EX-0047 Unable to read preferences for the requested interface. Please use another repository and/or ProjectAccess Interface. Resolving the problem This happens due to a corrupt bmt.ini file in <Install Location>/c8/configuration directory. This issue can be resolved by extracting bmt.ini from last known good backup or even from installation files.
Read more