Tracing the Launch of Server Control Client

When you try to launch Server Control Client from Operations Sentinel Console and certain errors occur, a dialog box appears telling you to look at the Windows Application Event Log for more detailed information. As a supplement to this information, the Unisys Support Center may ask you to set some environment variables to trace the launch of Server Control Client from Operations Sentinel Console.

Use the following instructions to turn on tracing for the Server Control Client on an Operations Sentinel workstation. Perform this procedure only after consulting with the Unisys Support Center. Extra system resources are required once tracing is turned on, so it is recommended that you use this procedure only for debugging.

  1. Double-click My Computer.

  2. Double-click Control Panel.

  3. Double-click System. The System Properties window opens.

  4. Click the Advanced tab, and then click Environment Variables.

  5. Click New in the System Variables pane of the Environment Variables window. The New System Variable dialog box appears.

  6. Type 

    SPOLAUNCHWINEXE_DBG

    in the Variable Name box.

  7. Type 

    on

    in the Variable Value box.

  8. Click OK. You should see SPOLAUNCHWINEXE_DBG as an environment variable with the value on in the System Variables section.

  9. The folder where the debug file for SPOLAUNCHWINEXE_DBG is located is named by the TEMP or TMP environment variable. If you do not have an environment variable named TEMP or TMP on your Operations Sentinel workstation, perform the following steps:

    1. Repeat the procedure beginning with step 1 through 5.

    2. Repeat step 6 specifying TEMP or TMP for the Variable Name.

    3. Repeat step 7 specifying the location of a temporary folder, such as C:\TEMP or C:\TMP for the Variable Value.

    4. Click OK. You should see TEMP or TMP as an environment variable in the System Variables section with the value you have specified.

  10. Create the SPOGETHTTPCODEDBG environment variable as follows:

    1. Repeat steps 1 through 5.

    2. Repeat step 6, specifying SPOGETHTTPCODEDBG for the Variable Name.

    3. Repeat step 7.

    4. Click OK. You should see SPOGETHTTPCODEDBG as an environment variable with the value on in the System Variables section.

  11. Reboot the Operations Sentinel workstation.

  12. Reproduce the error.

    If SPOLAUNCHWINEXE_DBG equals on, you have turned on traces to the \temp\LOG_SpoLaunchWinExe-date.txt file, where temp is the value of environment variable TEMP or TMP, and date is today’s date. You can view the file using any text editor, such as Windows Notepad or Microsoft Word.

    If SPOGETHTTPCODEDBG equals on, you have turned on traces to the installation-folder\output\client_http-pid-error.txt file. Regardless of whether the environment variable is set, all errors are logged to the installation-folder\output\client_http-pid-error.txt file. You can view the file using any text editor, such as Windows Notepad or Microsoft Word.

  13. After you have retrieved the information from the log file, it is recommended you turn off tracing. Do this by deleting the SPOLAUNCHWINEXE_DBG and SPOGETHTTPCODEDBG system environment variables from your workstation.