Troubleshooting
Problem
This technote explains why IBM® Rational® ClearCase® view creation results in an error, protection will be weak, along with suggestions to resolve the problem when working on Microsoft® Windows®.
Symptom
During view creation, the following error is generated:
%>cleartool mkview -tag my_test_view \\host1\cc_storage\views\my_test_view
noname: Warning: Can not find a group named "DOMAIN\User_name".
cleartool: Error: no group "clearcase" found; protection of 5♦╚┼w tΦ┼ YY├j$h` ┴wΦ`¿ will be weak
cleartool: Error: unable to create security descriptor for \\host1\cc_storage\views\my_test_view: No mapping between account names and security IDs was done.
cleartool: Error: Unable to create directory "\\host1\cc_storage\views\my_test_view": Invalid argument.
cleartool: Error: Unable to create view "\\host1\cc_storage\views\my_test_view".
Note: The characters in the error message are what actually appear in the error and are not a typo or glitch with the technote. Also, a similar message is also displayed when creating a view through the GUI.
OTHER SYMPTOMS:
- The view log shows the following error:
view_server.exe(4072): Error: Unable to remove ".new_db". Permission denied.
- The ALBD Log shows the following errors:
albd_server(1252): Error: Albd(1252): Error: Server view_server.exe (pid=4072) on "C:\cc_storage\view\my_test_view.vws" died on startup; marking it as "down".
albd_server(1252): Server view_server.exe(4072) exited with status 1
Cause
Some registry keys may have been set incorrectly either by editing the registry, or by specifying incorrect values during installation.
Resolving The Problem
Note: This solution contains information about modifying the system registry. Before making any modifications to the Microsoft® Registry Editor, it is strongly recommended that you make a backup of the existing registry. For more information describing how to back up the registry, refer to the Microsoft Knowledge Base article 256986 at http://support.microsoft.com/kb/256986.
Find the value:
32-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Atria\ClearCase\CurrentVersion\ClearCaseGroupName
64-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Atria\ClearCase\CurrentVersion\ClearCaseGroupName
Ensure that the key is correct and that the group listed there really exists.
Additionally check the value in the key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Albd\ObjectName
The account listed in this key should be the ALBD account and should be the same for all machines that have an ALBD service running in a given ClearCase environment. This user should also exist.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21225987