Troubleshooting installer failure during upgrade
During upgrade, a group of background processes are disabled until the upgrade completes. See Processes automated during upgrade.
This is handled by the Operating-Mode server setting. During upgrade, the value of Operating-Mode is set to 1 or 2 based on whether the installer is running on the primary or secondary server, respectively. This is applicable to all Remedy installers. However, if the installer crashes or aborts unexpectedly, the background processes may not be restored to their pre-upgrade settings. This requires that the Operating-Mode is set to value 0, the normal mode of operating.
To restore the background processes to their pre-upgrade values
- Double-click the javadriver.bat (Windows) and javadriver.sh (Unix) file. The file is located at the following location:
- (Windows) <InstallDirectory>\ARSystem\Arserver\api\lib
Ensure that the JAVA_HOME environment variable points to the JRE path.
- To initialize, enter the
- To log on, enter the
logcommand and provide details such as user name, password, and server name.
- If you are not using the port mapper, enter the
ssp(Set Server Port) command and then enter the server port number.
- Enter 0 or a blank for Using private socket.
- Enter the
vercommand to verify the login information.
- Enter the
ssi(Set Server Info) command and perform the following:
- Enter 1 for the Number of server info operations that you want to perform.
- Enter 463 as the Operation number to set the server to the operating mode.
- Enter 2 for integer as the Datatype.
- Enter 0 or 1 as the Integer Value.
Command: ssi SET SERVER INFO Number of server info operations (0): 1 Operation (1-605) (1):463 Datatype Null/Key/Int/Real/Char/DiaryList/Enum/Time/Bitmask/Byte Decimal/attach/currency/date/timeofday/join/trim/control/Table/Column/ulong/ coords/view/display (0 - 14, 30-34, 40-43) (0): 2 Integer Value (0): 0 Set Server Information Status ReturnCode: OK Status List : 0 items
The ar.cfg is populated with pre-upgrade values.