Approval Server Sanity check failed each and every time when we start Health Check from "ARSystemMaintenanceTool.cmd or ARSystemMaintenanceTool.sh" |
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. 1) Check below lines related to approvals are present in ar.cfg file or not. Server-Plugin-Alias: ARSYS.ARDBC.PREVIEW ARSYS.ARDBC.PREVIEW <servername>:9999 Approval-Server-Suspended: F Alternate-Approval-Reg: T 2) Open pluginsvr_config.xml file present under ARServer Installation Dir/pluginsvr to confirm if below entries are present or not. <plugin> <name>ARSYS.ARDBC.PREVIEW</name> <classname>com.bmc.arsys.approval.main.ApprovalPlugin</classname> <filename>C:\Program Files\BMC Software\ARSystem\approval\bin\arasj91_build001.jar</filename> <pathelement type="location">C:\Program Files\BMC Software\ARSystem\approval\bin\arasj91_build001.jar</pathelement> <pathelement type="location">C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arcmnapp91_build001.jar</pathelement> <pathelement type="location">C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arutil91_build001.jar</pathelement> </plugin> 3) Open armonitor.cfg file and confirm if "C:\Program Files\BMC Software\ARSystem\approval\bin\armaskingImpl91_build001.jar" present under plugin process or not. "C:\Program Files\Java\jre1.8.0_91\bin\java" -Xmx512m -classpath "C:\Program Files\BMC Software\ARSystem\pluginsvr;C:\Program Files\BMC Software\ARSystem\pluginsvr\arpluginsvr91_build001.jar;C:\Program Files\BMC Software\ARSystem\approval\bin\armaskingImpl91_build001.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arcmnapp91_build001.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x <servername> -i "C:\Program Files\BMC Software\ARSystem" -m 4) Go to ARServer Installation Directory and confirm if ar.lck.390608 (approval lck file) and ar.lck.390609 ( Dispatcher lck file) is created or not. 5) Enable arjavaplugin.log in Debug Mode from ARSystem Administration Console --> System---> General--> Plugin Server Administration and select below - Plugin Server Instance which is using port _9999_ Click on Plugin Server Configuration Tab --> Logging Configuration and change Log Level: Debug 6) Then kill ITSM plugin process from task manager by going into server. Then open arjavaplugin.log from DB Folder and confirm if Approval Plugin is getting Loaded Successfully or not. > /* Mon Apr 03 2017 05:20:20.457 */ Adding path elements for the plug-in ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:20.457 */ Adding property location as C:\Program Files\BMC Software\ARSystem\approval\bin\arasj91_build001.jar > /* Mon Apr 03 2017 05:20:20.459 */ Updated XML config with the plug-in ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:24.226 */ Attempting to load Java Plugin ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:24.240 */ Number of URLs for plugin ARSYS.ARDBC.PREVIEW is 4 > /* Mon Apr 03 2017 05:20:24.240 */ URL1: file:/C:/Program%20Files/BMC%20Software/ARSystem/approval/bin/arasj91_build001.jar > /* Mon Apr 03 2017 05:20:24.240 */ URL2: file:/C:/Program%20Files/BMC%20Software/ARSystem/approval/bin/arasj91_build001.jar > /* Mon Apr 03 2017 05:20:24.260 */ No static init routine found, skipping init call - ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:24.261 */ Done to call init plugin ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:24.261 */ Successfully loaded Java Plugin ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:38.979 */ Attempting to Create an instance of the plugin ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:39.826 */ Thread 35 successfully created an instance of ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:42.151 */ Attempting to Create an instance of the plugin ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:42.151 */ <ARSYS.ARDBC.PREVIEW>Approval Plugin is already loaded > /* Mon Apr 03 2017 05:20:42.151 */ Thread 38 successfully created an instance of ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:43.170 */ Attempting to Create an instance of the plugin ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:43.171 */ <ARSYS.ARDBC.PREVIEW>Approval Plugin is already loaded > /* Mon Apr 03 2017 05:20:43.171 */ Thread 36 successfully created an instance of ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:44.383 */ Attempting to Create an instance of the plugin ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:44.383 */ <ARSYS.ARDBC.PREVIEW>Approval Plugin is already loaded > /* Mon Apr 03 2017 05:20:44.384 */ Thread 39 successfully created an instance of ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:45.593 */ Attempting to Create an instance of the plugin ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:45.593 */ <ARSYS.ARDBC.PREVIEW>Approval Plugin is already loaded > /* Mon Apr 03 2017 05:20:45.594 */ Thread 37 successfully created an instance of ARSYS.ARDBC.PREVIEW > /* Mon Apr 03 2017 05:20:46.846 */ <ARSYS.ARDBC.PREVIEW>Action Request System(R) Approval Server Version 9.1.02 201611252320 > /* Mon Apr 03 2017 05:20:48.274 */ <ARSYS.ARDBC.PREVIEW>The approval server suspended mode is = false Note: If above settings and parameters are good then follow below steps :-- 7) Enable Approval Debug logs from AP:Administration form from that server where Approval is ranked 1 in Operation Ranking form. 8) Go to ARServer Installation dir/arsystem/ and open ARSystemMaintenanceTool.cmd and click on Health Check and perform a sanity check. 9) Open approval Debug logs and check if you can see anything similar to this or not. > /* Mon Apr 03 2017 19:26:57.0792 */ Process a New-Details command > /* Mon Apr 03 2017 19:26:57.0804 */ The process name Issue Approval is ambiguous > /* Mon Apr 03 2017 19:26:57.0804 */ The number of active matching processes with name Issue Approval is 2 > /* Mon Apr 03 2017 19:26:57.0805 */ Please use one of the above mentioned process GUIDs > /* Mon Apr 03 2017 19:26:57.0897 */ 4502 Operation cancelled due to error 10) If yes then we have multiple processes running for AP-Sample2:Get Agreement form. To confirm the same open AP:Administration form. 11) Select Show For Process :-- Issue Approval and under the process it should be only 1 Active Process. If we have multiple then disable one and run sanity check again. 12. If Sanity check for Approval failed on 2nd server in server group then confirm if all the above points and if everything is OK then kill ITSM java Plugin process and run sanity check manually from ARSystemMaintenanceTool tool from 2nd server in server group. Note: For each and every application we need only one process as Active if we have multiple Processes are active then it will create an issue. |