1. PyPA
  2. Python Packaging Authority Projects
  3. pylauncher
  4. Issues
Issue #10 invalid

MSI not found error when attempting reinstallation

iainn
created an issue

If you attempt a re-installation (using a different copy of the msi), the installer attempts to look for the msi file from the initial installation. This original msi might not exist any longer. Regardless, the msi you're using for the re-installation attempts to look for the original msi in the wrong directory.

Steps to reproduce

echo This also works with at least launcher=launcher.msi

launcher=launchwin.amd64.msi

cd "c:/Documents and Settings/username/Desktop"

wget "https://bitbucket.org/vinay.sajip/pylauncher/downloads/${launcher}"

mkdir A B

cp ${launcher} A/A${launcher}

cp ${launcher} B/B${launcher}

cd A/

msiexec /i A${launcher}

cd ../B/

msiexec /i B${launcher}

Actual results The re-installation fails with message box: A network error occurred when attempting to read from the file: C:\Documents and Settings\username\Desktop\B\Alauncher.msi

Comments (3)

  1. Vinay Sajip

    I'm not sure this is something I can do anything about, since the location of the original MSI is not something that is configured in the MSI itself, and AFAIK determined by Windows Installer in some other way. I normally uninstall the product (if the original MSI is missing, you can still remove it using Add/Remove Programs) before installing using a fresh MSI. As a workaround, you can do this.

    As the focus of this project is the launcher itself rather than the installer for it, I am not sure I will have the time to investigate this issue in detail. However, if you or any one else can identify any simple change to the MSI which will avoid the problem you're getting, I'll certainly look at implementing it.

  2. iainn reporter

    Fair enough.

    Internet searching suggests that there may be a particular reason it's looking for the original installer---say to exec those exe files (?). FWIW, I tried a couple things, but I was stumbling in the dark and it was to no success. Oh well.

  3. Log in to comment