Computer Associates SQLSTQ99000600 Diagnostics Guide - Page 39

MSI packages, Installation Process Overview, Troubleshooting Installation and Migration

Get Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0 PDF manuals and user guides
UPC - 757943257441
View all Computer Associates SQLSTQ99000600 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 39 highlights

Installation Process Overview MSI packages For interactive installs log files can be found in the following folder %TEMP% For non-interactive installs (for example when using Infrastructure Deployment) log files can be found in the following folder %windir%/Temp The Windows® Installer uses a master MSI package which invokes other specific basic MSI packages for different Unicenter DSM components based on installer selections/parameters. The master setup writes to the following log file DSMSetup.log Unicenter DSM component MSI packages write to the following log files DSMSetupxxx.log where xxx stand for the component name (e.g., Manager, ScalabilityServer, AgentSD etc A return code of 1707 or 3010 at the end of these files indicates that everything went OK. The MSI installer log files are written by the MS Windows Installer and their format can be rather cryptic. Thankfully Microsoft provides a tool - wilogutl for analyzing MSI log files. Wilogutl analyzes a Windows Installer installation, and displays suggested solutions to errors that are found in a log file. Non-critical errors are not displayed. Wilogutl.exe can be run in quiet mode or with a user interface (UI). The tool generates reports as text files in both the UI and quiet modes. It works best with verbose Windows Installer log files, but also works with non-verbose logs. This tool is only available in the Platform SDK Components for Windows Installer Developers. For more information, consult the Microsoft support website. Chapter 5: Troubleshooting Installation and Migration 5-9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
Installation Process Overview
For interactive installs log files can be found in the following folder
%TEMP%
For non-interactive installs (for example when using Infrastructure
Deployment) log files can be found in the following folder
%windir%/Temp
MSI packages
The Windows® Installer uses a master MSI package which invokes other
specific basic MSI packages for different Unicenter DSM components based on
installer selections/parameters.
The master setup writes to the following log file
DSMSetup.log
Unicenter DSM component MSI packages write to the following log files
DSMSetupxxx.log
where xxx stand for the component name (e.g., Manager, ScalabilityServer,
AgentSD etc
A return code of 1707 or 3010 at the end of these files indicates that
everything went OK.
The MSI installer log files are written by the MS Windows Installer and their
format can be rather cryptic. Thankfully Microsoft provides a tool – wilogutl -
for analyzing MSI log files.
Wilogutl analyzes a Windows Installer installation,
and displays suggested solutions to errors that are found in a log file.
Non-critical errors are not displayed. Wilogutl.exe can be run in quiet mode or
with a user interface (UI). The tool generates reports as text files in both the
UI and quiet modes. It works best with verbose Windows Installer log files, but
also works with non-verbose logs.
This tool is only available in the Platform SDK Components for Windows
Installer Developers.
For more information, consult the Microsoft support
website.
Chapter 5: Troubleshooting Installation and Migration
5–9