Products | Versions |
---|---|
TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) | - |
Not Applicable | - |
Description:
On Windows, the upgrade from TIBCO ActiveMatrix BPM 2.0,2.1 to TIBCO ActiveMatrix BPM 2.2,3.0,3.1 fails at tibcohost upgrade with the error, "TIBCO-AMX-INFRA-002126: error renaming...."
Symptoms:
The upgrade from TIBCO ActiveMatrix BPM 2.0,2.1 to TIBCO ActiveMatrix BPM 2.2,3.0,3.1 fails with the above error. It happens while using TIBCO Configuration Tool (TCT) option :Upgrade TIBCO ActiveMatrix BPM Instance.
The upgrade fails while upgrading tibcohost. In the "upgrade.tibcohost" log present at <CONFIG_HOME>\tct\bpmupgrade\<date-time>\logs, the following error is seen :
TIBCO-AMX-HPA-CLI-000104: error converting existing host to new version
at com.tibco.amf.hpa.client.cli.commands.ConvertHostCommand.execute(ConvertHostCommand.java:134)
at com.tibco.amf.hpa.client.ant.tasks.HPAClientTask.execute(HPAClientTask.java:195)
at com.tibco.amf.hpa.client.ant.tasks.UpgradeHostTask.execute(UpgradeHostTask.java:52)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
..
Caused
by: TIBCO-AMX-INFRA-002124: error preparing for rename of
E:\ProgramData\BPM-2.1-XX\tibco\data\tibcohost\Admin-AMX BPM-AMX BPM
Server\host to E:\ProgramData\BPM-2.1-XX\tibco\data\tibcohost\Admin-AMX
BPM-AMX BPM Server\data_3.2.x\host
at com.tibco.neo.util.FileChangeRecord.renameFile(FileChangeRecord.java:201)
at com.tibco.amf.hpa.core.common.store.StoreManager.convert(StoreManager.java:301)
... 109 more
Caused
by: TIBCO-AMX-INFRA-002126: error renaming
E:\ProgramData\BPM-2.1-XX\tibco\data\tibcohost\Admin-AMX BPM-AMX BPM
Server\host to E:\ProgramData\BPM-2.1-XX\tibco\data\tibcohost\Admin-AMX
BPM-AMX BPM Server\host.tmp0
at com.tibco.neo.util.FileUtils.simpleRenameFile(FileUtils.java:532)
at com.tibco.neo.util.FileChangeRecord.renameFile(FileChangeRecord.java:185)
... 110 more
Cause:
The error is because the upgrade script is not able to rename the <CONFIG_HOME>\tibcohost\<instance name>\host folder to <CONFIG_HOME>\tibcohost\<instance name>\host.tmp0. On Windows, typically a lot of customers start the tibcohost using the command prompt. The upgrade script first stops the tibcohost and then tries to rename the folder as part of upgrading the host from 3.1.5 to 3.3.0. It fails to rename the folder as the command prompt (from which tibcohost is started) holds the lock of the folder. In Windows, a folder is considered locked if it is displayed in Windows Explorer or if a command shell is open with the folder as the current directory.