CAPS 5.1.0 to 5.1.1 in-place upgrade

Running on Windows 2003 Server R2 Enterprise:

All SAR files appear to be updated successfully except egate.sar. I receive the following error message:

BUILD FAILED

file:D:/JavaCAPS51/repository/work/1156805377055/install.xml:23: com.stc.repository.RepositoryException:

Could not checkout EnvironmentTemplate the latest version 1.1 has been locked by user jrieke

Exception Name: com.stc.repository.versioncontrol.impl.RepositoryVersionLockedException

Message: Could not checkout for write file: ModuleManager/ConfigurationTemplate/{38000000-AE3C31590C0100-81DA8220-01}.xml the latest version: 1.1 has been locked by user: jrieke

Stack Trace: Message:

Could not checkout for write file: ModuleManager/ConfigurationTemplate/{38000000-AE3C31590C0100-81DA8220-01}.xml the latest version: 1.1 has been locked by user: jrieke

Stack:

com.stc.repository.versioncontrol.impl.RepositoryVersionLockedException: Could not checkout for write file: ModuleManager/ConfigurationTemplate/{38000000-AE3C31590C0100-81DA8220-01}.xml the latest version: 1.1 has been locked by user: jrieke

[1135 byte] By [jqrieke1] at [2007-11-26 9:48:22]
# 1
If I recell correrctly, a similar error happened to me. The Repository had run out of memory and I upped the JVM heap to 1GB and was fine afterwards.
ldeavila at 2007-7-7 0:56:04 > top of Java-index,Java Enterprise System,Java Composite Application Platform Suite -- General Discussion...
# 2

As the error shows, the installation failed because a user jrieke has a components locked that needs to be updated by the installation script. You could either log in as user jrieke and check in all components (it seems that the culprit is the environment template) or you can use the cleanupWorkspace script in the repository\util directory to clean out the workspace of user jrieke and thus unlock all objects that this user has locked.

Frederik@NL at 2007-7-7 0:56:05 > top of Java-index,Java Enterprise System,Java Composite Application Platform Suite -- General Discussion...