Community Forums
Page 1 of 3 123 LastLast
Results 1 to 5 of 14

Thread: Error 1001. Installer Was Working, Now Isn't

  1. #1
    Join Date
    Oct 2013
    Posts
    10

    Error 1001. Installer Was Working, Now Isn't

    I have multiple projects, in separate solutions that are Windows Services written in C# using VS2012 and VS2013. InstallShield LE is the installer.

    These are projects that have been through QA and deployed, the installers worked. the ones built in the past still do. However, if I rebuild the projects now and run the installer, it will die.

    It runs long enough to create the folder & copy files into it. then it produces a dialog that says only "Error 1001." with no other information. I click on OK and it produces another dialog, same message. I click OK. the folder it created is deleted and installation fails.

    there have been no code changes. No changes to anything in the install project. simply get it from TFS, build it & watch it not install.

    If I simply run the last copy of the installer that was checked into TFS, it installs fine.

    This pattern is identical with 2 solutions that I've checked. I haven't been able to find anything about this that has worked. I'm guessing that somewhere, some setting has been changed but it's not at the project or solution level, as this repeats in both VS2012 and VS2013.

    A clean install of VS2013 and InstallShield LE on a laptop works fine.

  2. #2
    Join Date
    Nov 2004
    Posts
    47
    Have you checked the installer log file to see what file is causing the error? If you search these forums for "1001" you'll get a lot of hits.

  3. #3
    Join Date
    Oct 2013
    Posts
    10
    I have no idea where any such logs might be. I've looked but haven't found them.

  4. #4
    MichaelU's Avatar
    MichaelU is offline InstallShield Software Engineer
    Join Date
    Jan 2004
    Location
    Schaumburg, IL
    Posts
    4,683
    You may have luck changing what version of .NET you reference in Tools > Options. Referencing the 4.6 framework can result in a 1001 (fixed in late 2015 releases), and that could have changed outside of your project.
    Michael Urman - Staff Software Engineer - Flexera Software: InstallShield Team

  5. #5
    Join Date
    Oct 2013
    Posts
    10
    While I now have 4.6 installed, the build targets 4.0,. always has & this has not changed.

    The laptop on which it still works has 4.5 installed. I think the desktop got 4.6 when I installed VS2015.

Page 1 of 3 123 LastLast

Posting Permissions

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