Announcement

Collapse
No announcement yet.

IRMakeBootstrap.exe returned error: 7

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • IRMakeBootstrap.exe returned error: 7

    I can't combine my two MSI files into one executable. It works *sometimes* and other times it doesn't work. One minute it will be working, then the next compile I do gives the bootstrapper error 7 above. I change NOTHING in the .msifact file and it just dies at error 7. Tens of GB of space and 40GB of free RAM.


    Here's the output:

    Generating bootstrapper...

    LZMA 9.38 beta : Igor Pavlov : Public domain : 2015-01-03

    LZMA 9.38 beta : Igor Pavlov : Public domain : 2015-01-03

    LZMA 9.38 beta : Igor Pavlov : Public domain : 2015-01-03

    LZMA 9.38 beta : Igor Pavlov : Public domain : 2015-01-03

    LZMA 9.38 beta : Igor Pavlov : Public domain : 2015-01-03
    Indigo Rose MSI Bootstrapper
    Copyright (c) 2015 Indigo Rose Corporation - www.indigorose.com
    Initialize folders...
    Loading configuration file...
    Copy setup executable stub...
    Writing Version Resources...
    Adding bootstrapper execution level manifest...
    Adding files...
    D:\Temp\mainscript.lua.tmp
    D:\Temp\_global_functions.lua.tmp
    C:\Test\setup\setupx86.msi
    C:\Test\setup\setupx64.msi
    Adding data marker...
    Adding manifest file...
    ERROR: Failed to open file: C:\test\setup\setuptest.exe
    Cleaning up temporary files...
    Bootstrap build failed: 7
    Error 1011: IRMakeBootstrap.exe returned error: 7
    Deleting temporary files

    Build FAILED! Error: 1011 - Error executing pre/post build step


  • #2
    I advise you to turn off your virus scanner, then try building again.

    Ulrich

    Comment


    • #3
      I believe that was it!

      Comment


      • #4
        Spoke too soon. That was not it. I turned off Real-time Protection in Defender and I exited out of Malwarebytes. Still getting error 7. Only in this .msifact file!

        Comment


        • #5
          Still getting this error. One minute it will allow it, but others it won't. Full reboot does not fix it either. I need help, please.

          Comment


          • #6
            Hello,

            Please make sure that you disable all third party malware and virus scanners, as well as Windows Defender.


            If you get the error "ERROR: Failed to open file: C:\test\setup\setuptest.exe" it is because another process is locking the file, typically such of those tools, or an open Windows explorer / File Explorer window, which may be attempting to gather information about the file. Make sure everything is closed when you build the MSI package and the bootstrapper.

            Ulrich

            Comment


            • #7
              I unloaded Malwarebytes and verified the service was stopped. I then followed the link above and turned off Realtime protection. I also verified Windows Antivirus service was stopped. Still getting Error 7...

              Comment


              • #8
                Only way I could get it to work was to move all bat and cmd and vbs files out of "setup" folder and just run .msifact

                Comment


                • #9
                  And even THAT fails occasionally. If I create a new folder where the .msifact is in (i.e. c:\!projects\product\version.minor\setup -> c:\!projects\product\version.minor\setup2), then compiling from setup2 folder works most of the time. So is it something in my .msifact file causing error 7? Completely disabling the AV does not fix error 7.

                  Comment


                  • #10
                    I clarified with the developers that indeed the error 7 is caused by something or some process interfering with the executable file being created, not allowing to be opened to append data to the file being constructed. I am not sure if you have yet another antivirus / anti-malware tool installed you are unaware of, or if something else is scanning / locking the file, but you may want try to investigate which process(es) is/are locking the file. Sysinternal's Process Monitor or a similar tool may be of assistance here. You may also want to change the output folder (different partition, etc.), and see if this makes a difference.

                    Ulrich

                    Comment


                    • #11
                      Yes, I noticed the EXE gets created at first for about 1.4MB, then it disappears. I definitely do not have any anti-virus running or anti-malware. I even tried it in a newly-created VM with Windows Defender protection disabled per your link above. I have multiple .msifact files in the "setup" folder.

                      Like I mentioned, if I create a new folder to put the .msifact in (i.e. c:\!projects\product\version.minor\setup -> c:\!projects\product\version.minor\setup2) and move the .msifact file to the setup2 folder, it runs without error. Almost like something is being cached somewhere, but deleting the %TEMP% folder and clearing IE and Chrome cache do nothing.

                      Comment


                      • #12
                        Furthermore, error 7 occurs when I am missing the mainscript.lua file from the folder. I am joining a 32-bit and a 64-bit file into one executable.

                        Comment


                        • #13
                          And when it fails when I combine the two, the combined MSI file is only 620k, which it should be about 45MB. So this is why the EXE is failing to generate, I believe. Any help with this?

                          Comment


                          • #14
                            You would need to share your two MSI files, any dependencies, and the files of the bootstrapper (XML, lua and batch files), so I could attempt to replicate the issue.

                            Ulrich

                            Comment

                            Working...
                            X