Are there any MSI-gurus in here? I'm working to build MSI-packages for Office 2013 (among other Applications) and in order to do this I'm using EMCO Msi Package Builder Enterprise - which seems to do the job well. I've used this to build several smaller sized MSI-packages successfully. This software successfully builds the MSI-package for Office 2013, but installation fails With the failure code: 2356. Then I proceeded to try again with logging, and find the following: DEBUG: Error 2356: Couldn't locate cabinet in stream: Data1.cab So I've googled, read hundreds of forum posts and whatnot, but I am still no closer to a solution. I've tried rebuilding the MSI-package several times with varying properties, but still no go. So therefore I turn to you good folks of Bit-Tech; does any of you guys have some advice for me so that I might keep whatever hair I have left?
One thing to clarify first - are you repackaging Office 2013 via the Snapshot method, or are you attempting to use Microsoft's Office Customisation Tool to deploy an image? Repackaging is usually not recommended for Office installations due to the complexity of the application (I'm assuming that this is the method that you are using, from the original text). If that is the case, it's probably best to use the Customisation Tool for creating an automated installation, using the original Setup.exe file
Yes, I figured the problems I'm having are due to the complexity of the installation required. I have not tried using the customisation tool in order to do this, and I just might try that. However, what I need is the ability to provide a single file for installing the entire Office package in order to make this process simpler for our students (roughly 21000 licenses have to be rolled out) - and that's why I first reached for an MSI-package. I'll take a look at the customisation tool. Thank you for your input.
You mention the requirement for a single file - are they going to be running the installation from a network, or will the final deployment be provided to them to copy & take away. If it's the former, then you could provide them with a single batch / script file, which will in turn look over the network for the Office deployment and run the relevant launch string. The other problem that you could potentially run into with a full repackage is updates - if the Office updates look for the original MSI and can't find it, the chances are it won't install properly. If you really have to deploy as a single MSI file, the only thing I can think of from the top of my head is: 1. Create a deployment using the office tool. 2. Put the deployment into a single MSI 3. Use the new MSI to put down the Office deployment locally (e.g. C:\Office2013Source) Then either use a custom action to run the deployment, or give the user a desktop shortcut to install it when ready. That way you'll get the full Office installation, using a more supported method (i.e, the original one) - the MSI that you make would just act as a delivery wrapper. This does have some drawbacks. If you use a CA to launch the deployment, you'd be effectively running an MSI, from an MSI - this is generally a bad move for various reasons. (and well documented as a bad move) If you give the user a shortcut to run the installation, then they'll probably moan about having to click two things to install the application. Bear in mind that it's 09:15 over here and I've only had one coffee. I'll probably think of either another method, or some critical drawback with the above later...
