Skip to main content

Problem installing Cognos Transformer for Connections on Windows



For a mistake the first time I ran and installed the cognos-setup.bat script inside CognosConfig package for connections 4.5, I installed both Transformer and BI Server on the same folder, E:\IBM\Cognos64.
I fixed the error into cognos-setup.properties ( Transformer into E:\IBM\Cognos and BI Server in E:\IBM\Cognos64)So I removed everything with uninstaller on E:\IBM\Cognos64\uninstall. Only the BI package was available for removal.




 If I try to run again the cognos-setup.bat script, the tiny Cognos Stream Installer in the upper left corner  was every time getting this exception

you cannot install this version of the product over a previously installed version

After checking and doublechecking (regedit show no presence of any transformer reference, and I also tried installing and removing Transformer with standalone installer on the wrong directory, to be sure everything is correctly removed from user registry or whatever).

At the end, I had an idea: the response file for perfoming installation was still held into the AppData/local/temp folder. I uninstalled everything with Cognos uninstaller, removed physically the folders where I was installing, and purged everyhing in here

C:\Users\Administrator\AppData\local\Temp

(If you can't see this folder with explorer, just type it in the path)

Now run again cognos-setup.bat and everything will install correctly


Comments

Post a Comment

Popular posts from this blog

Multiple controllers with Spring Boot

Remember, when you want to have multiple controllers with Spring Boot, you should always name them differently in the annotation, otherwise they will not work So these two together will NOT work (or just one of them will work) These two instead WILL work.
2 comments
Read more

Can't use the newest npm when node is installed with brew (MacOs)

Even though I installed and reinstalled node with brew, with last versione 11.8.0, apparently it kept using the last version fdecollibus$ npm install --global gatsby-cli npm WARN npm npm does not support Node.js v11.8.0 npm WARN npm You should probably upgrade to a newer version of node as we npm WARN npm can't make any promises that npm will work with this version. npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. npm WARN npm You can find the latest version at https://nodejs.org/ /usr/local/Cellar/node/11.8.0/bin/gatsby -> /usr/local/Cellar/node/11.8.0/lib/node_modules/gatsby-cli/lib/index.js + gatsby-cli@2.4.8 npm -v gave me back version 5.6.0. I've therefore noticed that  /usr/local/lib/node_modules had wrong permissions assigned to root:wheel. A chown did not fix the problem: I've had to manually delete the content of the folder (cd / usr/local/lib/node_modules and -careful - type rm -rf ...
Post a Comment
Read more