1.首先检查控制面板clearcase程序中的albd_service是否Running.
2.检查服务里Atria Location Broker服务是否启动,否则手动重新启动.如果不能启动请检查albd_service的输入密码是否正确.并请参考:
Error 1069
***********************************************************************************
C:\>net helpmsg 1069
The service did not start due to a logon failure.
***********************************************************************************
When this error occurs, one or more of the following issues is blocking the ALBD from starting.
ALBD account password changed.
ALBD account name is incorrect. This is most likely to occur in the middle of a domain migration, once the old domain is decommissioned.
ALBD account locked. (This may occur as a result of #1 above)
ALBD account does not have one of the following rights on the host:
Log on Locally
Log on as a Service
Note: In an Microsoft Active Directory® domain, a group policy may override the local policy setting. If to, the "Local Security Policy" control panel will show different results for "local" and "effective" policies after restarting the computer.
When trying to start the clearcase_albd service, the following error is displayed:
Could not start the Atria Location Broker service on \\MACHINE
Error 1069: The service did not start due to a logon failure.
The Atria Location Broker service cannot logon with the stored user name (SID) and password.
There can be a number of reasons for this: The most common are:
The stored SID is no longer valid - perhaps the clearcase_albd account has been deleted and re-created.
The password is not valid - perhaps there is password expiration enforced.
The account could be locked - too many attempts with an invalid password.
The clearcase_albd service account does not have 'log on as a service' right on the local machine.
The clearcase_albd service account does not have 'log on as a service' right on the Domain Controller where the account was created.
The system is a registry server, and the <ClearCase installation>\var\rgy directory is missing.
These resolutions correspond to the items above:
Contact your IT department to see if there were any changes to the clearcase_albd account or its password. If the password or the account itself has been changed, create a new site prep (netinst) area and have all users run the Setup program again to pickup the new password.
To check if there is a bad password, go to the Windows Services applet, click on Atria Location Broker, click on the Logon tab and re-enter the password. Attempt to start the albd service again.
Contact your IT department to insure that the clearcase_albd account password is set to never expire.
Have your IT department reset the clearcase_albd account.
The status of the "logon as a service" right can be determined by checking the rights assignments:
The domain qualified albd account (DOMAIN\clearcase_albd) should be displayed in the list of users who have the Log on as a service rights.
Both the Local Policy Setting and Effective Policy Settings boxes should be checked. If the Effective Policy Setting box is not checked for the clearcase_albd account, then the account rights assignment was not set correctly on the Domain Controller.
If you ensure that has the correct account name and password but the service still has logon problems then you need to seek the assistance of the Windows Domain Administrator to resolve the logon issue.
Create the directory <ClearCase installation>\var\rgy
Back to top
--------------------------------------------------------------------------------
Error 1067
***********************************************************************************
C:\>net helpmsg 1067
The process terminated unexpectedly.
***********************************************************************************
Check the application event log for errors from the ALBD. If there is a recent error from the ALBD reading Error: albd_server must run in the ClearCase group, one of the following issues has caused the ALBD server to refuse to start:
ALBD is being started while disconnected from the network. This is not a supported configuration as ClearCase is a network-based SCM application.
ALBD is starting before the network has fully initialized. In this event, the albd_server process cannot access a Windows domain controller to authenticate itself on the network. When this occurs, the albd_server process will log the above error and exit. In some cases it may "hang" instead of properly exiting. If this problem happens often enough try the following workaround to alleviate the symptoms:
Add the "Browser" and "Netlogon" services to the list of dependencies for the ALBD service.
WARNING: If you use the Microsoft Windows Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. IBM Rational Software cannot guarantee that you can solve problems that result from using the Microsoft Windows Registry Editor incorrectly. Use the Microsoft Windows Registry Editor at your own risk.
Open the registry with regedit
Go to the key -
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Albd
Double click on "DependOnService" The current hex value is:
52 00 70 00 63 00 53 00 73 00 00 00 54 00 63 00 70 00 49 00 70 00 00 00 00 00
(RpcSs TcpIp)
Edit it to a new hex value of:
52 00 70 00 63 00 53 00 73 00 00 00 54 00 63 00 70 00 49 00 70 00 00 00 62 00 72 00 6F 00 77 00 73 00 65 00 72 00 00 00 6E 00 65 00 74 00 6C 00 6F 00 67 00 6F 00 6E 00 00 00 00 00
(RpcSs TcpIp browser netlogon)
ALBD account is not a member of the ClearCase Server Process Group defined in the Windows registry. Examine the following registry key HKEY_LOCAL_MACHINE\Software\Atria\ClearCase\CurrentVersion\ClearCaseGroupName ensure that the ALBD account is a member of that group.
Note: It is possible to run the ALBD service as a non-privledged user, however, this is not a supported configuration on ClearCase servers since it will prevent the server from correctly executing administrative tasks.
The ALBD user account must have a valid password set and the ALBD user account password should be set to never expire
The Atria Location Broker Service startup is set to:
Startup Type = Automatic
Log On As = This account: <the albd account>
Note: If you are in a Domain, the <albd account> must be domain qualified
Example: DOMAIN\username
If machine is in a Domain, there cannot be a group called clearcase in the user manager for the Domain and in the user manager on the local machine. The local clearcase group must be removed.
The Domain name cannot be clearcase. This will cause problems starting the ALBD service.
The ALBD user must have read/execute permissions to the RATIONAL-HOME directory
Confirm that the ClearCase bin directory is at the beginning of the System path.
Confirm that the DOMAIN\clearcase_albd has log on as a service permissions on the Local Machine (Local User Manager)
WINDOWS, WINNT or WINNT35 and subdirectories have to allow the ALBD user to have at least read/execute permissions.
Give the albd user full control of the root drive c: (or where ClearCase is installed). Do not replace on subdirectories, because this will replace your entire c: drive, just the root.
The password for the albd may be corrupted. Go into the Control Panel > Services and double click on the albd service. Then re-enter the password on client machine. This will recreate the password if it is corrupt.
If all of the above fails, normally the clearcase_albd user does not need local admin rights, but if everything else has been checked, try adding the domain qualified clearcase_albd user to the local administrator's group.
Check if the system's hard drive is low on disk space or if the virtual memory is empty.
If the ClearCase registry was being tampered with (for example if you make a backup registry server the primary register server not using rgy_switchover, but by copying the info from the var/backup directory into the var directory and reboot) you will get error 1067. Resolution is to undo all that was previously done and revert back to the original registry server. Delete the info in var directory and making the system a backup registry server again.
Left over information in the "var" directory from the older install may be causing confusion with the newer version of ClearCase.
Follow these steps:
Stop ClearCase completely through Start > Setting > Control Panel > ClearCase > Services Startup tab.
CD to "C:\Program Files\Rational\ClearCase" or your installation directory.
Copy the "var" directory and put it on your desktop.
Go back to the "C:\Program Files\Rational\ClearCase\var" directory and remove all possible directories that you can.
Reinstall ClearCase to the original installation directory
Restart Windows
Login as the same user that did the install (This is critical)
Once logged back in CD into the "saved" var directory, then into the "rgy" directory and copy (into the Windows clipboard) all the information in this directory.
CD to the "C:\Program Files\Rational\ClearCase\var\rgy" and paste the copied information from the "saved" ...\var\rgy directory clicking yes to replace all.
Verify that all the ClearCase services are running from the Services Startup tab in the ClearCase control panel.
Back to top
--------------------------------------------------------------------------------
