1

I have created a windows installer using wixtoolset but when I install it says access denied although I ran the installer with administrator permission. I have attached the access denied popup image and logs

Property(C): WIXUI_INSTALLDIR_VALID = 1
=== Logging stopped: 5/8/2021  12:06:41 ===
MSI (c) (7C:3C) [12:06:41:423]: Note: 1: 1708 
MSI (c) (7C:3C) [12:06:41:423]: Note: 1: 2205 2:  3: Error 
MSI (c) (7C:3C) [12:06:41:423]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708 
MSI (c) (7C:3C) [12:06:41:423]: Note: 1: 2205 2:  3: Error 
MSI (c) (7C:3C) [12:06:41:423]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 
MSI (c) (7C:3C) [12:06:41:423]: Product: Abc -- Installation failed.
MSI (c) (7C:3C) [12:06:41:423]: Windows Installer installed the product. Installation success or error status: 1603.
MSI (c) (7C:3C) [12:06:41:423]: Grabbed execution mutex.
MSI (c) (7C:3C) [12:06:41:423]: Cleaning up uninstalled install packages, if any exist
MSI (c) (7C:3C) [12:06:41:423]: MainEngineThread is returning 1603

enter image description here

Any clue why this would happen

vibhor Gupta
  • 103
  • 11
  • Does this happen on a clean test virtual? – Stein Åsmul May 08 '21 at 18:31
  • I think WiX creator Rob Mensching chose to remove the embedded Error table inside each MSI file because he prefers [the "fallback solution" described here](https://stackoverflow.com/a/3273365/129130). This sounds rational since this seems to yield localized (translated) error messages. There are probably other reasons that make sense as well - I don't have a full overview. – Stein Åsmul May 08 '21 at 19:24

1 Answers1

0

Logging: You might want to create a verbose log with debugging information:

msiexec.exe /i C:\Path\Your.msi /L*vx! C:\Your.log

Custom Actions: Are there any custom actions in your MSI? If so, try to disable them by setting the condition for them to run to 0 in the MSI (use Orca to tweak the MSI for testing) or compile a version of the MSI without custom actions. Just to test.

Anti-Virus: It could be that your MSI has been quarantined by your anti-virus as discussed here. Did you try to disable anti-virus before running your MSI?

Other Ideas: There are many possible causes. It can be weird interactions such as software installed on the box that causes problems - try on a clean machine or virtual first.

Some quick questions:

  • Is this a corporate machine with policies of all kinds?
  • Do you have any disk space issues?
  • Do you work off a network drive?
Stein Åsmul
  • 39,960
  • 25
  • 91
  • 164
  • I am providing a [link](https://github.com/pyxll/pyxll-installer/blob/master/templates/Product.wxs) of wxs file . Is this a corporate machine with policies of all kinds?(Yes) Do you have any disk space issues?(No) Do you work off a network drive?(No) – vibhor Gupta May 09 '21 at 08:25
  • I did run with your logging recommended way but the response was same – vibhor Gupta May 09 '21 at 08:47
  • I see you try to make a package that can run without admin rights. [Please check these restrictions for packages to function in this scenario](https://www.advancedinstaller.com/user-guide/single-package.html). – Stein Åsmul May 09 '21 at 18:02