Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

MSI error 1606/1603

Hi all, apologies if this is the wrong place for this query.

Currently having issues trying to remotely install a new piece of software (PRIME 2017, by Drake Lane). We're encountering a 1603 error, which on opening the output log turns out to be:

MSI (s) (9C:E0) [11:06:48:858]: Product: PRIME 2017 -- Error 1606. Could not access network location temp.

The error is encountered when run as our PDQ service account user (no profile, admin rights), the logged on user (myself, with admin rights) and when manually running the parameters through the command line.

To attempt to resolve it I've created an entry for "temp" under User Shell Folders, for both current user and local machine, and there's still no change there.

Documentation for the software is available here, page 10 references the MSI parameters required. Using their parameters (with an additional log added in) gives the same error.

 

The deploy will end up being for around 15 machines for various department heads, so a background install would definitely be preferable to trying to chase down times that their machines are accessible.

Many thanks!

0

Comments

3 comments
Date Votes
  • Check your TEMP environment variable to see if it points to a UNC path.

    PowerShell: $env:TEMP

    CMD: ECHO %TEMP%

    0
  • For both a standard user and the PDQ service account, the variable points at (the user equivalent of):

    C:\Users\THOMAS~1.000\AppData\Local\Temp

    0
  • Most of the users are concerning towards this site to have the answers. Therefore you need to move towards is bid4papers legit that is showing the informational techniques.

    0