No longer able to access GLV after swapping from one AP server to another.
search cancel

No longer able to access GLV after swapping from one AP server to another.

book

Article ID: 417929

calendar_today

Updated On:

Products

Automation Point

Issue/Introduction

We are not able to access GLV correctly on prod server after roleswap. Below is the log from ASOTRACE - 

15:30:22.273 S0 P5512 T2920 S: Started 11/09/2025: Sev=4, Cat=ffffffff, Ver=11.7.3.1 Rev=UnofficialBuild Apr  3 2024
15:30:23.835 S0 P3896 T10656 C=NA Sev=I [AsoClass::Configuration::SynchActiveDefset] [cfg:00217AB8] Updated definition set value to 'sc_Sessions~Set~3270.apm'
15:30:25.854 S3 P836  T5668 C=NA Sev=I UTIL: DLL termination: "D:\Program Files (x86)\CA\CA Automation Point\Bin\ApStartSvcs.exe" /Node
15:32:42.638 S0 P11400 T1128 C=NA Sev=I Name of rexx to run D:\ProgramData\CA\CA Automation Point\Site\MyFiles\REXX\mybatch.rex
15:32:42.638 S0 P11400 T1128 C=NA Sev=I Arguments to pass to program: LIST_BATCH_VARS
15:34:25.879 S0 P11400 T1128 C=NA Sev=D UtilRexxIsRegistered: Host name GLV does not exist in Rexx Host Table.
15:34:25.879 S0 P11400 T1128 C=NA Sev=D UtilRexxIsRegistered: Host name GLV does not exist in Rexx Host Table.
15:34:26.895 S0 P11400 T1128 C=NA Sev=I UTIL: DLL termination: asorexx.exe mybatch.rex LIST_BATCH_VARS

Cause

 Customer was attempting to perform an EXPORT and IMPORT function between the DR server and PROD server.  There was some third party software that was contributing to the problems, and causing the LOAD to run slower than normal and eventually failing.

Resolution

 

To resolve:

Shutdown all AP tasks.   Check the server's task monitor to ensure everything was closed.

Issue STOPAP on the server's DOS Command Prompt.    

     (In this issue the STOPAP command failed to stop the REXX script running that caused the issue, so we had to kill that task separately and then do the STOPAP again).

Do a restart by going first to the Configuration Manager/Third Party Software/REINSTALL which will first uninstall before it installs again.

Then started the AP service and the problem was resolved.