Results 1 to 3 of 3

Thread: Setup Interruption

  1. #1
    Join Date
    Jun 2003
    Posts
    2

    Setup Interruption

    Hi, I am new to InstallShield. We were using Wise Installer before but not quite happy with it so we decide to try IS Dev. I built a new setup of our VB project. Things are fine when I installed on XP and Windows ME. On Windows 2000, I will get the error Installation Wizard is interupted, no installations have been made on this machine (maybe not the exact word). I searched the posts of the forum and found that the sequence number of SetupInterupted =-2 will play a key role. So I check my setup and it did equal to -2 (User and Adm both). I was wonder what else could cause this problem?

    In the compile process there is no error no warning. Did I miss files which the Installer will look for?

    BTW, the error happens after the Windows Installer configuration dialog.

    Please provide me any help if you can. Thanks.

  2. #2
    Join Date
    Oct 2001
    Location
    Here and there
    Posts
    16,233
    You might create a log file (msiexec /i product.msi /L*v everything.log) and see what error occurs; that dialog box appears if some action failed. (Once you have an error number, then, you might search the MSI Help Library and the InstallShield Knowledge Base [http://support.installshield.com/kb] for possible reasons and solutions...)
    Robert Dickau - This and That - Flexera Software

    Want help? See Windows Installer white papers, training courses, newsletters, HelpNet, forum search, Knowledge Base, ...
    Want more help?
    See our InstallTalk blog.
    Want even more help? See our relatively new Advanced Windows Installer (MSI) training course.

  3. #3
    Join Date
    Aug 2002
    Location
    Pittsburgh, PA
    Posts
    73
    I would probably start by creating a verbose log of the setup on the Windows 2000 machine. Depending on the type of setup you created, you would create a log as follows:

    For StandardMSI
    ============
    setup.exe /verbose"c:\setup.log"

    For BasicMSI (from a setup.exe)
    ======================
    setup.exe /v"/lv"c:\setup.log""

    For BasicMSI (from a .msi file)
    ====================
    setup.msi /lv"c:\setup.log"

    This way you can see what error is occuring on the machine. If you don't get a log, it maybe a permissions issue when the setup is trying to startup the Windows Installer Engine.

    On that thought, what version of Windows Installer are you including with your setup (maybe 2.0)? If so, Windows 2000 came with Windows Installer 1.2, so your setup might be trying to "upgrade" the Windows Installer engine to 2.0 and is running into permissions problems.

    Well, there is a couple of avenues you can pursue.

    Good Luck!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •