AR System Midtier2002Patch001 is failing to Deploy Payload with following error: ==== Filedeployer.log:- [main] INFO com.bmc.arsys.filedeployer.PayloadProcessor - Stopping process BMC:MidtierWebServer [main] INFO com.bmc.arsys.filedeployer.PayloadProcessor - Process BMC:MidtierWebServer is already stopped. [main] ERROR com.bmc.arsys.filedeployer.PayloadProcessor - Failed to backup original file D:\Program Files\BMC Software\ARSystem\midtier\WEB-INF\lib\Config.jar. The file might be locked by another process. [main] ERROR com.bmc.arsys.filedeployer.PayloadProcessor - Failed to backup original file D:\Program Files\BMC Software\ARSystem\midtier\WEB-INF\lib\arapi91_build009.jar. The file might be locked by another process. [main] ERROR com.bmc.arsys.filedeployer.PayloadProcessor - Error while deploying payload with DEPLOYMENT ID IDGAA5V0G8H8FAQ5PGLFQ4QX3BHMQ3 : Errors while backup and rename downloaded files. [Errors while extracting zip file midtier_common.zip. [Failed to backup original file D:\Program Files\BMC Software\ARSystem\midtier\WEB-INF\lib\Config.jar. The file might be locked by another process. armonitor.log:- <MNTR> <TNAME: RMI TCP Connection(7098)-10.230.2.156> <ERROR> <ProcessController > < ProcessController.java:1219 > /* Mon Aug 31 2020 15:19:39.0954 */ Unable to execute command Process[BMC:MidtierWebServer] Command[D:\Program Files\Apache Software Foundation\Apache-Tomcat-8.5.32\bin\shutdown.bat] ==== This is rolling back the deployment payload. |
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. ** This use-case is applicable to users who upgraded Mid tier from '9.1.04 to 20.02' OR '9.1.04 to 1805/1902/1908 then 20.02' ** Please follow below steps to successfully deploy the AR System Midtier 20.02 patch1/patch2 on windows operating system:- 1) open armonitor.conf (located under file Midtier>>deployer>>conf folder)file and comment out below line:- Example:- #External-Process: process-type = BMC:MidtierWebServer, start-command="D:\Program Files\Apache Software Foundation\Apache-Tomcat\bin\startup.bat", stop-command="D:\Program Files\Apache Software Foundation\Apache-Tomcat\bin\shutdown.bat", status-command="D:\Program Files\BMC Software\ARSystem\midtier\filedeployer\statusCheck.bat" Make sure below entry is not commented:- External-Windows-Service: process-type = BMC:MidtierWebServer, service-name="service name" Example:- External-Windows-Service: process-type = BMC:MidtierWebServer, service-name="Apache-Tomcat" Save the file. Ensure that tomcat services is running through Windows Services console. 2) Restart File deployer services. 3) Now open AR System Monitor form and make sure it has correct Midtier server entry with rank where you will be deploying the patch. 5) [Optional] Now open Remedy Management console(From Applications>>Remedy Management Console>>AR System Server Group Console>>Manage Process>> check type Midtier and make sure the status of BMC:MidtierWebServer is running. 6) Now you can start the patch deployment from Deployment Management console. NOTE: · If you already have the patch 1 deployed which got Rollback or Deployment Failed, you need to completely rollback the package before applying above steps. · If Rollback fails, follow steps from KA# How To Rollback D2P package in Server Group Environment, navigate to the section "Steps to Cleanup when Rollback fails” before applying above steps. |