Veritas NetBackup™ OpsCenter Administrator's Guide

To troubleshoot silent installation issues

1. After the silent installation ends, navigate to the following location:

   %ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS.

2. Check if a file named OpsCenterInstallLog.htm is present. If OpsCenterInstallLog.htm is not present, see 7.
3. Open OpsCenterInstallLog.htm and check the timestamp and the OpsCenter component it is for to ensure that it is the appropriate log file.

   You must check the timestamp because OpsCenterInstallLog.htm may have been generated as a result of previous silent installations.

   In addition, the same OpsCenterInstallLog.htm file is generated when you install OpsCenter server, or View Builder. Hence you must check the specific OpsCenter component that is associated with OpsCenterInstallLog.htm.

4. You can check the timestamp by opening OpsCenterInstallLog.htm and seeing the first line in the file. For example, the following is the first line from a sample OpsCenterInstallLog.htm file:

   01-19-2010,13:35:30: -Silent _RespFile "C:\Documents and Settings\Administrator\Ops-19-01-10-13-04-21.xml"

   In this example, the timestamp is 01-19-2010, 13:35:30.

5. To know the OpsCenter component the log file is associated with, search for the following keywords in the OpsCenterInstallLog.htm file:

   OpsCenter Server	You will find matches when you search for OpsCenter Server in the file. This means that the log file is for OpsCenter server.
   View Builder	You will find matches when you search for View Builder in the file. This means that the log file is for View Builder.

   Note:

   If you have checked the timestamp and the OpsCenter component associated with all present OpsCenterInstallLog.htm files and do not find a valid OpsCenterInstallLog.htm file, see 7.

6. Use the OpsCenterInstallLog.htm file to troubleshoot silent installation issues. Open the OpsCenterInstallLog.htm file to see if the installation was successful or to understand why the installation failed. This file shows the installation status at the end. Installation errors are flagged in this file in red color. You may also see a description about why the error occurred and troubleshoot accordingly.

   Ignore the subsequent steps of this procedure.

7. If OpsCenterInstallLog.htm is not present or you cannot find a valid OpsCenterInstallLog.htm file, check if OpsCenter<Product>InstallLog.htm file is present. In OpsCenter<Product>InstallLog.htm, <Product> can be Server, or View Builder depending on the OpsCenter component that you are installing.
8. Always ensure that the OpsCenter<Product>InstallLog.htm file is appropriate by checking the timestamp. You can check the timestamp by opening the OpsCenter<Product>InstallLog.htm file and seeing the first line of the file. For example, the following is the first line from a sample OpsCenter<Product>InstallLog.htm file:

   01-19-2010,13:35:30: -Silent _RespFile "C:\Documents and Settings\Administrator\Ops-19-01-10-13-04-21.xml"

   In this example, the timestamp is 01-19-2010, 13:35:30.

9. Use the OpsCenter<Product>InstallLog.htm file to troubleshoot silent installation issues. You can open the OpsCenter<Product>InstallLog.htm file to see if the installation was successful or to understand why the installation failed. This file shows the installation status at the end. Installation errors are flagged in this file in red color. You may also see a description about why the error occurred and troubleshoot accordingly.