|
|
|
Configuration Lock Errors in Verastream Host Integrator
Technical Note 10086
Last Reviewed 05-Dec-2008
Applies To
Verastream Host Integrator version 6.6 or earlier
Summary
Figure 1. Configuration is already locked: not locked locally or by remote AADS.
Technical Note 10086
Last Reviewed 05-Dec-2008
Applies To
Verastream Host Integrator version 6.6 or earlier
Summary
You may encounter certain "configuration lock" errors when attempting to install or configure servers in your Verastream Host Integrator (VHI) environment. This technical note describes how to resolve this problem.
Symptoms
Configuration lock errors may display during installation or configuration.
Installation Error
During installation of the Session Server component, Setup may be unable to perform install-time registration with the AADS server. On a UNIX/Linux system, Setup displays output similar to the following:
332 14:47:24.157 RegisterServer<wait 30 seconds ForConfigLock> attempting to lock332 14:48:24.174 RegisterServer<wait 30 seconds ForConfigLock> lastError=2820332 14:48:24.175 RegisterServer<run> unable to lock configurationSetup failed to register this server with the existing AADS, my_aads_name.The cause is indeterminate.Error return code = 33Error symbolic value is RC_AADSCONFIGLOCKALREADYLOCKEDPlease copy this error number, and the output fromthe server registration program (above) and contact Attachmate.Do you wish to [r]etry this step or [q]uit the setup? (r/q) [r] --->Configuration Error
In Administrative WebStation, when attempting to enter Config Mode, the following error is displayed.
Figure 1. Configuration is already locked: not locked locally or by remote AADS.Explanation
The configuration lock errors can occur in the following situations:
- Configuration is already in progress. For example, another Administrative WebStation console instance may be in Config Mode, or a model package is in the process of being deployed or undeployed (using activatemodel or deactivatemodel commands).
- An unexpected problem or ungraceful exit occurred during previous configuration or deployment, thus failing to release the configuration lock.
- In an AADS failover environment, the automatic replication of configuration data across multiple AADS servers may be out-of-synch.
Solution
To resolve this issue, do the following:
- Wait a few minutes and re-attempt your action. The error may be a momentary condition.
- If the problem continues, stop and start the AADS servers. To prevent problems in an AADS failover environment:
- It is recommended that you stagger startup of the AADS servers (separated by 5 minutes or so) to avoid any possible inter-communication circular wait condition.
- If an AADS server was previously stopped, make sure it is started last to avoid data corruption.
As an alternative workaround to restarting, you can manually release the configuration lock by running the following file in your VHI bin directory:
- Windows: releaseconfiglock.bat
- UNIX/Linux: sh releaseconfiglock.sh
