Having trouble install MSI package

BatchPatch Forums Home Forums BatchPatch Support Forum Having trouble install MSI package

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #9204
    jsira7
    Participant

    Hello there… I have an interesting issue that I hope you can enlighten. I created a custom silent MSI package for Microsoft ReportViewer 2008. When I deploy it through Batch Patch it doesn’t complete. It either comes back as SUCCESSFUL or Exit Code 1619. When I execute the MSI file manually on a PC, it works just fine, installs silently, etc. I have even copied the script from Batch Patch Command to execute line and ran it manually from Command prompt on a PC and it installs:

    msiexec.exe /i “Microsoft Report Viewer Redistributable 2008.msi” /q

    It’s just when I run it from Batch Patch that it doesn’t work. I’ve tried selecting the box to Copying the entire directory contents… and Leave enter directory contents… but it still doesn’t install.

    Any suggestions?

    #11234
    doug
    Moderator

    I’m confused. You said it doesn’t complete but it comes back as either SUCCESS (exit code 0) or exit code 1619. Are you saying that even when it comes back as SUCCESS (exit code 0), the installation has not actually occurred? That’s certainly a weird one. Sounds to me like there is a problem with the MSI package.


    MSI exit codes are listed here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa376931%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

    1619 ==

    ERROR_INSTALL_PACKAGE_OPEN_FAILED

    This installation package could not be opened. Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package.


    To be honest, I’m at a bit of a loss here. This is the first time I have ever heard of an issue deploying a .MSI. I think the next step would be to test running the installation remotely with PsExec. Maybe that’s where the problem is occurring.

    Try putting the .MSI on the target computer in “C:Program FilesBatchPatchdeploymenttemp”

    Then from the BP computer try running the following two commands to see if either one works. BP would run the equivalent of the first command to perform the installation in the SYSTEM account for maximum permissions. The second command will deploy in the regular user account that you’re using.

    psexec \targetComputer -s -w "C:Program FilesBatchPatchdeploymenttemp" msiexec.exe /i "C:Program FilesBatchPatchdeploymenttempMicrosoft Report Viewer Redistributable 2008.msi" /q

    psexec \targetComputer -w "C:Program FilesBatchPatchdeploymenttemp" msiexec.exe /i "C:Program FilesBatchPatchdeploymenttempMicrosoft Report Viewer Redistributable 2008.msi" /q

    Let me know what happens.

    -Doug

    #11235
    jsira7
    Participant

    Yes… Even when it states SUCCESS it doesn’t install. I’ll try what you suggested and see if that works.

    #11236
    jsira7
    Participant

    Hey Doug… Another question. I get the same result when I run the .exe version of Report Viewer. I put in the /S for silent install but it doesn’t complete. On the target system I see Report Viewer.exe in Task Manager but it just hangs and doesn’t complete. I have installed .exe successfully before with Batch Patch. Any idea what I’m doing wrong?

    I also tried copying the file down and leaving it in the directory, but I get the same results.

    #11237
    doug
    Moderator

    If it just hangs indefinitely then that indicates that you are not executing a silent installation. What’s actually happening is that the package is being executed and presenting a GUI, but the GUI is hidden as a result of the non-interactive remote execution, and so it just hangs indefinitely waiting for input that it will never receive.

    When you say you “put in the /S for silent install” I would ask you where did you come up with /S ? What I mean is that all installers have different silent installation parameters. You can’t just assume that /S is a legitimate parameter. You have to first ascertain what the actual silent/quiet parameter is for a particular installation package. More on that at the following link:

    Understanding and Discovering the Silent Parameters Required to Remotely Deploy Software with BatchPatch

    I just downloaded the Microsoft ReportViewer 2010 Redistributable Setup from https://www.microsoft.com/en-us/download/details.aspx?id=6442&751be11f-ede8-5a0c-058c-2ee190a24fa6=True&fa43d42b-25b5-4a42-fe9b-1634f450f5ee=True (not sure if this is the same one that you are using or not), and then at the cmd prompt I ran

    ReportViewer.exe /?

    It showed me that the silent/quiet parameter is /q

    Microsoft ReportViewer 2010 Redistributable Setup.png

    #11239
    jsira7
    Participant

    Thanks a bunch for really looking into this… Totally appreciate it. I did as mentioned above (putting the /q as you mentioned) but it now comes back with exit code 1612. Any other suggestions?

    #11240
    doug
    Moderator

    Are you deploying the .msi or the .exe?

    I just successfully deployed the 2010 ReportViewer.exe from this link:

    https://www.microsoft.com/en-us/download/details.aspx?id=6442&751be11f-ede8-5a0c-058c-2ee190a24fa6=True&fa43d42b-25b5-4a42-fe9b-1634f450f5ee=True

    I used the settings shown in the screenshot below:

    Deploy Microsoft ReportViewer 2010 Redistributable.png

    The 1612 error you are receiving is described here as:

    ERROR_INSTALL_SOURCE_ABSENT 1612 The installation source for this product is not available. Verify that the source exists and that you can access it.

    I’m not quite sure what you’re doing. The fact that I just deployed this successfully without any problems on the first attempt leads me to believe that you are either not performing the deployment in the correct/proper way (as shown in my screenshot above) or that something in your environment is causing the 1612 error to occur. It’s hard for me to say what, but the error that you are receiving is coming from the installation package, not from BatchPatch. If you were to try to run that same deployment manually *without* BP from the command line of the target system, using just

    ReportViewer.exe /q

    I suspect you would encounter the same error since it’s being thrown by the installer from Windows, not by BatchPatch.

    -Doug

    #11241
    jsira7
    Participant

    Thanks again Doug… I went ahead and deployed it to another system and it worked. There must be something wrong with the test VM I have. Again, thank you so much for helping!!

    #11242
    doug
    Moderator

    No problem. Glad that you got it worked out.

    -Doug

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.