Software Deployment Question

how to deal with 1606 error in msi

01/05/2019 361 views

error 1606: Could not access location [2]

0 Comments   [ + ] Show comments


Community Chosen Answer


That is certainly an error...

A 1606 error.

Enabling (MSI) logging and producing that error again would greatly help you, to help us, to help you.
Do not paste it here, upload it to pastebin or something like it.

Answered 01/06/2019 by: rileyz
Red Belt

All Answers


that is typically a rights problem.  If were installing as system that could be the issue, some software needs the users structure to write temp files to.  Like rileyz stated need the logs

Logging Options
    /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
        i - Status messages
        w - Nonfatal warnings
        e - All error messages
        a - Start up of actions
        r - Action-specific records
        u - User requests
        c - Initial UI parameters
        m - Out-of-memory or fatal exit information
        o - Out-of-disk-space messages
        p - Terminal properties
        v - Verbose output
        x - Extra debugging information
        + - Append to existing log file
        ! - Flush each line to the log
        * - Log all information, except for v and x options
    /log <LogFile>
        Equivalent of /l* <LogFile>

Answered 01/07/2019 by: SMal.tmcc
Red Belt


You will get this error when the WI engine is unable to resolve directory paths, e.g. if you have a bad value in the 'Directory' table.

As stated, logging will help you determine that but, in the first instance, validating the MSI will flag table errors.

Answered 01/08/2019 by: VBScab
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ