Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Problem

Info

When there are install or uninstall issues, check the logs.  The Adams ADAMS® version determines how to do that.

Solution

...

ADAMS v5.5.0 and Later

Starting with Adams 5.5.0, verbose logging is enabled by default.

Here is where to find the log files.

Manually Run

%userprofile%\AppData\Local\Temp

For example: C:\Users\<username>\AppData\Local\Temp

Run by Adams Update Service

...

...

Adams Update Service is run under the system user, therefore is uses the temp directory specified by Windows.

ADAMS 8.0+

C:\Windows\SystemTemp

ADAMS 7.x or earlier

C:\Windows\Temp

File Names

The log files are named with the following patterns:

  • MSI log file: <Adams application name>_<date and time>_setup<architecture>.log

  • EXE log file: <Adams application name>_<date and time>.log

Pre-Adams v5.5.0

Prior to Adams 5.5.0, verbose logging had to be enabled manually as follows:

If there are install/uninstall issues one of the first things to try is verbose logging.

Install EXE w/Log

<EXE_FILE_NAME> /v"/l*v \"InstallLog.txt\""

Install MSI w/Log

msiexec /i <MSI_FILE_NAME> /l*v "InstallLog.txt"

Uninstall EXE w/Log

<EXE_FILE_NAME> /v"/x /l*v \"InstallLog.txt\""

Uninstall MSI w/Log

msiexec /x <MSI_FILE_NAME> /l*v "UninstallLog.txt"

Repair Windows Files

If there are corrupt Windows' system files, then installers can fail.  To verify and repair Windows' system files, at an administrative command prompt (i.e. run as administrator), run this command:

sfc /scannow

Filter by label
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@8cd
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "install" and type = "page" and space = "FS"
labelsinstall

Page Properties
hiddentrue

Related issues