I'm trying since days to Thinapp Office 2010 following the steps from this guide:
Well, I created a .msi file for installation with a seperat .dat file as data container. The .dat file is over 3 GB huge. The installation is successful under Windows XP, under Windows 7 (x86), the installation crashes with the following error message:
Error: 1310. Error attempting to create the destination file: C:\Program Files (x86)\office_2010std (VMware ThinApp)\office_2010std.dat System error code: 131
I thinapped Office 2010 with ThinApp version 5/6, under XP / Win 7, but the result was everytime the same. I'm suspecting that the .dat file is way to big for the installation. Could this be true? If yes, what can I do? Compression is already turned on.
Thanks in advance for your help.
Yeah, we seem to be hitting another .msi limit there. It works when you use "MSIStreaming=0" (include .exe/.dat in msi), since we basically extract the files ourselves. However, with MSIStreaming=1 we depend on the Windows Installer code to install files, and that doesn't seem to work when the .dat file is over 2GB.
I tried it with MSIStreaming=0, but this time I've got the following error message:
The system cannot open the device or file specified.
I attached an image from the folder, where the .msi file is placed, so you can have a look at the file size.
What's wrong this time? I captured and packed the whole project twice from scratch.
Thanks in advance.
Sorry for reviving a dead post. Did you find a resolution to this issue? I have just thinned Office 2010 and I'm having the same issue. I have to have Project and Visio installed and even after deleting the fonts, drive_c, etc, files that the quide tells you to do, my dat file is still over 3 GB as well. Streaming works fine, but the MSI file fails to install with the same error message of not being able to create destination file. I've searched this forum as well as support forums and was surprised to find that either no one else has had this issue or I'm still doing something wrong that everyone else has figured out on their own.
Could you please see if copying the entire bin folder (inclusive of the .DAT,.exes and .msi) onto the runtime machine and then installing it would solve the problem?
You could copy the .DAT file onto the installation directory of the thinapp on the runtime machine, remove the reference of .DAT file from the MSI (Using Orca) and then installing the MSI normally.
Sorry for the delay as I was out of the office yesterday. As with most projects, this all may be a moot point now. They are now wanting me to split this out into three different thinapps (office, visio, project) with the possibility of all three running on one machine at the same time. If I break them all out, it should drop me below the 2 GB size limit for the msi thereby negating all of this. Isn't I.T. fun sometimes?
I'm currently experiencing this currently with an Office 2010 package that has a 2.7GB dat file, using Thinapp Packager 4.7.3.
When I copy the DAT file locally when this error pops up and hit retry, the application installs and registers just fine. Any ideas on how to get this fixed besides reducing the DAT file below 2GB?
We've opened a ticket with VMware support, I will post back up with the answer. I've already tried using the following parameter in the Package.ini which definitely gets the package under 2GB. Peter Bjork recommeded this here Optimize the package size without deleting project content.. | VMware ThinApp Blog - VMware Blogs.
However, the problem is if I do this the Office Protection service breaks and Office will not activate. Works just fine as long as I include all the files captured originally. Even with the above compression parameter set, I still get at 2.7GB dat file.
And the official word from VMware is: With version 4.7.3 there is no support for DAT files larger than 2GB for streaming MSI thinapp packages.
Hopefully we'll see it in Thinapp 5.