Failed to update the registry if Analyst not run by install user

Technote (troubleshooting)


Problem(Abstract)

After installing Analyst, only the user that performed the installation can use Analyst.
All other users, even local administrators, cannot use Analyst as the following errors are generated :

1st Error:
Failed to update the registry
The system was trying to write to the key:
HKEY_CURRENT_USERS\Software\Cognos\Analyst
Possible reason could be insufficient rights to write to this part of the registry.

2nd Error (by answering OK to first error)
A Fatal error has occured in the startup section of the application.
The application will be terminated
Function name: SystemIniGet
Namespace: #.US
RegOpenKeyA returned a nonzero error code

This occurs on Windows 2008 64-bit and Windows 7 64-bit

Resolving the problem

1-Login to Windows as the user who installed Analyst :

2- From Start/Run menu of Windows, launch REGEDIT.EXE :
2.1- For Planning 10.1 :
- Export HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101 as *.REG
- Go to HKEY_CURRENT_USER\Software\Cognos if it exists, then on the right pane, note the value of string value called "Analyst" if this exists.
It should be pointing to the \bin directory (for example : C:\Program Files (x86)\ibm\cognos\c10\bin\)
2.2- For Planning 8.4.1 :
- Export HKEY_CURRENT_USER\Software\IBM\Cognos\Planning841 as *.REG
- Go to HKEY_CURRENT_USER\Software\Cognos if it exists, then on the right pane, note the value of string value called "Analyst" if this exists.
It should be pointing to the \bin directory of Cognos Planning installation.
2.3- For Planning 8.4.0 :
- Export HKEY_CURRENT_USER\Software\Cognos\Planning84 as *.REG
- Under HKEY_CURRENT_USER\Software\Cognos\, on the right pane, note the value of string value called "Analyst" : this should point to the \bin directory of Cognos Planning installation.
3- Open a Windows session as the user who is having errors :
3.1- For Planning 10.1 :
- Import the above *.REG registry export
- If applicable, create the string value "Analyst" under 'HKEY_CURRENT_USER\Software\Cognos\' and set it to <Install Location>\ibm\cognos\c10\bin\
3.2- For Planning 8.4.1and 8.4.0 :
- Import the above *.REG registry export
- If applicable, create the string value "Analyst" under 'HKEY_CURRENT_USER\Software\Cognos\' and set it to the full path of the \bin directory
4- Also assign the Local Users group Read/Write/Change access to the \bin directory of Cognos Planning installation.

For Windows 2008 64-bit, it is also necessary to create an additional registry key (string value "Analyst") under HKEY_CURRENT_USER\Software\Cognos\Analyst and set it to the full path of the \bin directory (i.e. for version 10 <Install Location>\ibm\cognos\c10\bin\).

For Planning Manager, it may be necessary to create the following additional key :
HKEY_CURRENT_USER\Software\IBM\Cognos\Planning101\Analyst\TableDefaults

--- The particular case of very restricted environments ---
In case the security policies do not allow user to access his own registry, then proceed that way once the *.REG has been created :
- Connect as a local administrator on the PC machine
- Open regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
- Execute a search on the login name of the user, so that to find the corresponding ID
- Let's assume this ID is S-1-5-21-3383517641-4076153820-3159048928-1000
- Edit the REG file that was previously created, and replace string HKEY_CURRENT_USER by HKEY_USERS\S-1-5-21-3383517641-4076153820-3159048928-1000
- Now save the REG file and double-click on it, so that to import the keys in the registry. This creates the Cognos Planning Analyst keys in HKEY_USERS for the right user.
- Now next time this user will log on to Windows, his HKEY_CURRENT_USER key will be filled with these same Cognos Planning Analyst keys.

Rate this page:

(0 users)Average rating

Document information


More support for:

Cognos Planning
Analyst

Software version:

8.4.1, 10.1

Operating system(s):

Windows

Software edition:

All Editions

Reference #:

1472649

Modified date:

2014-10-02

Translate my page

Machine Translation

Content navigation