How to make an app - Andromo App Maker

Announcement

Collapse
No announcement yet.

Installing Application using SCCM results in an error.

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

  • Installing Application using SCCM results in an error.

    I have a customer that is installing our software on Windows 10. Our software uses the latest version of Setup Factory. Our customer uses Microsoft's Software Center Configuration Manager (SCCM) to install our software using the Windows system account. During the install process, we display a setup screen for the user to select the location for user files. After the Next button is pressed, the install process hangs. Looking at Task Manager, the process irsetup.exe continues to run and accumulate system memory until it throws an error. Any idea what may be causing this?

    When installed outside of SCCM, everything works as expected and there is no issue.

    Thanks,
    Mark

  • #2
    This sounds like the System account cannot write to the path which was selected. User files most likely shouldn't be deployed by the elevated account or System, instead I believe that they could be copied to the common application data folder (typically C:\ProgramData), and on the first execution the application checks for the existence of the user files. If they already exist, use them. If they don't exist, copy them from ProgramData, already using the proper account (and security settings), and then use them.

    Ulrich

    Comment


    • #3
      I have a similar experience with a product called Dialux evo 7.1
      When installed as system user, the program fails with error code 5 (setup cancelled by user according to https://www.indigorose.com/webhelp/s...turn_Codes.htm)
      However when the same setup is run as user, but interactively (means it shows stuff in the current local session instead of session zero), it works.
      I'm currently stuck, as I can't figure out what causes the cancellation. I've checked every name not found and path not found error caused by the program using procmon and created the nessecary folders in the systemusers' profile. Some msi based installers fail when these don't exist when they construct their directory lists. This doesn't seem to fix the issue however.

      Is there a way to enable a log file, so we can see what is going on? Or is there a switch we need to use when using the system account like in ms sql perhaps?
      I've tried both /S and /S/W switches for install.

      Background:
      I'm building deployment packages for SCCM as part of my job, and am using psexec from systemtools to test installers as if they were deployed with the SCCM client. This is done on a Windows 10 x64 enterprise system in an esx environment. The OS has no antivirus or other products installed, with the exception of an old version of Symantec's Wise package studio.
      I test on Win7 as well, but not until Win10 works - and we've not gotten there yet with this product.

      Comment


      • #4
        Neiro - An installation log file can be generated for the install by going to Project > Log Files. There you can enable it and define it's location, filename, and error detail. If it ends up bombing out before the log file creation, it could be related to where the setup is trying to extract it's temporary files. In that case you could try using the /T command line option with a custom temporary directory as a test:

        https://www.indigorose.com/webhelp/s...ne_Options.htm


        ruthema - In addition to what Ulrich suggested, you may also want to generate an installation log file if you aren't currently. It's possible it will contain some further clues.
        Darryl
        Indigo Rose Corporation

        Product Guides: AMS80 | SUF9 | TU30 | VP30 |MSIFACT |DeltaMAX

        Comment


        • #5
          Ulrich: I confirmed with the customer that the hang occurs after the next button is pressed on screen that prompts the users for a location on where to install the user files. The only script that gets executed on the "On Next" action is the location selected by the user is captured in a session variable. The default location is the user's mydocuments or documents folder. That location is written to the registry at the very end of the install. In addition, user files are written to that location when setup factory begins the writing of files.

          I like your idea of using the ProgramData folder and will try that. This will solve several other related issues as well.

          Darryl: I have the logging turned on, but apparently Setup Factory doesn't get the chance to write it out just yet.

          Will post what I find.

          Thanks for your help!

          Comment

          Working...
          X