I am playing with some post-installation tasks for Crystal Reports Runtime x86 and x64.  They are both MSI files and I have them each as their own Post-installation task, I can launch the msi just fine from my machine but the task fails when running from the K2000.  I have CRRuntime_64bit_13_0_3.msi typed in the Parameter box and nothing else.

Any suggestions as to why this fails?

Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment

Answer Chosen by the Author

The command to install an MSI silently is
msiexec /qn /i <name of MSI file>

Just calling the msi file works in the GUI but not in a command line mode.

Also, did you upload the files to the K2 in a zip file? If you did then depending on how you created the zip file it may be contained in a folder. I always select the actual files and use Send To, Compressed Folder. If you select the folder containing the files and then compress them the folder structure will be preserved and when the K2 extracts the files that top level folder will be present.

Answered 05/11/2016 by: chucksteel
Red Belt

  • I didn't zip the application, just uploaded the MSI directly. I ran the task again and it gave an unknown error this time. I opened the command window from the deployment and tried to launch the msi directly and it just blinked. When I take out the /qn it displays an error: "The installation package could not be opened. Verify that the package exists and that you can access it. Or contact the application vendor to verify this is a valid Windows Installer package."
    • Check the peinst SAMBA share to see what the file looks like after it was uploaded. The peinst share is hidden so you need to mount \\k2000\peinst and login with the correct credentials (that's assuming your hostname is k2000). On that share you will find an applications folder, then open the folder of the ID for your post-install task.

      Another option is to check the tasks.xml file. When the post-install tasks fails you should get an option to look at the tasks.xml file. There are entries for each task in the sequence and you can see what the command line looks like. You can also open a command prompt and check things out.
      • I just created a new scripted install and added my Crystal Reports Post-installation tasks and they succeeded. I didn't change anything on the SAMBA share, didn't really get a chance to look at it honestly. I wonder if the old scripted install just didn't like that task. Thanks for your help Chuck.
Please log in to comment


Hi good to see it worked for you. I don't know if this applies to your case but just for the record, it once happened to me that I uploaded a file being a .msi and tried to call it as for example Office.Msi in the post installation task command. The task was constantly failing until I realized that the appliance runs on a Linux and Linux is case sensitive... I replaced the call to Office.msi and it worked.
Answered 05/13/2016 by: Glaporte
Senior Yellow Belt

  • I thought about that also, which is why I did a rename of the file and copied the name via CTRL - C and pasted into K2000 but still failed. So far the command line is working; I will just leave it as it is.
Please log in to comment
Answer this question or Comment on this question for clarity