MS Office 2010 on Ubuntu 13.10 not installing

[ookimi]

I am using Wine 1.7.9. I tried the installation both through PlayOnLinux and through the manual creation of a 32-bit wineprefix (windows XP mode, msxml6 etc in the native setting). I even tried Crossover.

They all fail at the same place halfway through the installation, saying that the file {90140000-003D-0000-0000-0000000FF1CE}-C\SingleImageWW.msi is not found. However, when I check the contents of MSOCache in the wineprefix, that file is actually there.

Judging by the windows forums, that file is related to the trial versioning, and is sometimes a problem when a trial version was installed before. I do make sure to install to a clean prefix, though, and the product key is provided in the confix.xml.

I thought that the problem might be that it is not executable, and tried changing the permissions after it was created, but before the install failed. That did not work.

Here is the end part of the terminal output, if that helps:

Code: Select all

fixme:ole:NdrCorrelationInitialize (0xbc0def4, 0xbc0dfd0, 1024, 0x0): stub
fixme:rpc:NdrStubCall2 new correlation description not implemented
fixme:ole:NdrCorrelationFree (0xbc0def4): stub
err:rpc:I_RpcGetBuffer no binding
err:rpc:I_RpcGetBuffer no binding
fixme:ole:NdrCorrelationInitialize (0xa5dce74, 0xa5dcf50, 1024, 0x0): stub
fixme:rpc:NdrStubCall2 new correlation description not implemented
fixme:ole:NdrCorrelationFree (0xa5dce74): stub
fixme:ole:NdrCorrelationInitialize (0xa5dcea4, 0xa5dcf80, 1024, 0x0): stub
fixme:rpc:NdrStubCall2 new correlation description not implemented
fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self
fixme:ole:NdrCorrelationFree (0xa5dcea4): stub
fixme:ole:NdrCorrelationInitialize (0xa5dce64, 0xa5dcf40, 1024, 0x0): stub
fixme:ole:NdrCorrelationInitialize (0xa5dce44, 0xa5dcf20, 1024, 0x0): stub
fixme:ole:NdrCorrelationInitialize (0xa5dce24, 0xa5dcf00, 1024, 0x0): stub
fixme:rpc:handle_bind_error unexpected status value 1765
err:rpc:RpcAssoc_BindConnection rejected bind for reason 0
fixme:ole:NdrCorrelationInitialize (0x33cf14, 0x33cff0, 1024, 0x0): stub
fixme:rpc:handle_bind_error unexpected status value 1765
err:rpc:RpcAssoc_BindConnection rejected bind for reason 0
fixme:advapi:UnregisterTraceGuids 0: stub
fixme:advapi:UnregisterTraceGuids 0: stub

Any ideas, anyone?

[dimesio]

Do you have 32 bit winbind installed? Missing that is a common reason for the Office 2010 installer to fail.

(windows XP mode, msxml6 etc in the native setting)

I don't know what the "etc" is, but NO native dlls should be needed to install. Please try a clean wineprefix.

[ookimi]

Ok, just tried on a clean wineprefix, even changing anything. Same result.

I have winbind (2:3.6.18-1ubuntu3.1), libnss-winbind and libpam-windbind. There doesn't seem to be a separate 32-bit version in the repositories. If that is the issue, where can I get it?

[ookimi]

Thanks for the reply! I just tried with a clean prefix, without even installing dotnet and corefonts. Same result

I do have winbind, libpam-windbind and libnss-windbind. Synaptic does not say if that is 32 bit of 64 bit though.

I tried searching for the 32-bit version, and Debian wheeze reps seem to have one; but synaptic won't accept them (no public key error). If the 32-bit winbind must indeed be my problem, any suggestions on where to get it?

[dimesio]

Ask on your distro's support forum which package to install.

[ookimi]

Ok, I have removed everything samba-related and forced install of (apparently old - version 2:3.4.7~dfsg-1ubuntu3.13) winbind 32 bit from http://www.ubuntuupdates.org/winbind.
Now the installation of office does not even start, requiring msxml package version 6.10.1129.0. I cannot install it with winetricks to the 32 bit prefix, for it says that the package is not compatible with this processor type.

Here someone complained about a similar problem with MacOS: http://appdb.winehq.org/objectManager.p ... ngId=45082
The advice was to update wine to 1.7.5. But mine is 1.7.9 already...

I tried to setup the msxml both with winetricks and manually, installing the x86 version from Microsoft site. Both ways the result is the same. Here is the console output:

Code: Select all

env WINEARCH=win32 WINEPREFIX=~/.wine32
WINEPREFIX=~/.wine32 wine msiexec /i msxml6_x86.msi

wine: created the configuration directory '/home/infeld/.wine32'
fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
fixme:storage:create_storagefile Storage share mode not implemented.
ntlm_auth: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:iphlpapi:NotifyAddrChange (Handle 0xcce218, overlapped 0xcce230): stub
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:storage:create_storagefile Storage share mode not implemented.
ntlm_auth: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:iphlpapi:NotifyAddrChange (Handle 0xdce890, overlapped 0xdce89c): stub
wine: configuration in '/home/infeld/.wine32' has been updated.
fixme:storage:create_storagefile Storage share mode not implemented.
err:msi:ITERATE_Actions Execution halted, action L"LaunchConditions" returned 1603

[dimesio]

Now the installation of office does not even start, requiring msxml package version 6.10.1129.0. I cannot install it with winetricks to the 32 bit prefix, for it says that the package is not compatible with this processor type.

The Office installer should work with Wine's builtin msxml6. As for the message about the "processor type," no one's ever reported getting that. Wine will only work with x86 processors, but if you didn't have one, nothing would work at all. Are you sure the message wasn't about the architecture?

Code: Select all

err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

The winbind package you installed is apparently not the right one, or not installed properly.

[ookimi]

Yes, the Windows installer error message was indeed about the processor type. I was also surprised to see it. Maybe the guys from MS meant "architecture"

Anyways, I removed the broken winbind isntallation and tried the one from here: http://packages.ubuntu.com/saucy/i386/winbind/download
I downloaded the 32-bit version and installed it automatically with gdebi. It went ok, all dependencies were also installed. Now I have winbind:i386, version 2:3.6.18-1ubuntu3.1.

Now installing to a clean 32-bit prefix gives me this message:


Setup is unable to proceed due to the following error:
TO install and use this product, you must be running one of the following operating systems:
x86 platform
-Windows 7
- Windows Vista SP1
- Windows XP SP3
- Windows Server 2003 SP2

That is, the installation does not even start.

The terminal log is this:

Code: Select all

user@computer:~/!Office_temp$ p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:advapi:RegisterTraceGuidsA (0x2e034e56, 0x2e0b3d78, {8736922d-e8b2-47eb-8564-23e77e728cf3}, 1, 0x33fd08, (null), (null), 0x2e0b3d78): stub
fixme:process:GetSystemDEPPolicy stub
fixme:process:SetProcessDEPPolicy (1): stub
fixme:advapi:RegisterTraceGuidsA (0x101f59cc, 0x103a5908, {8736922d-e8b2-47eb-8564-23e77e728cf3}, 1, 0x33ee44, (null), (null), 0x103a5908): stub
fixme:system:SetProcessDPIAware stub!
fixme:htmlhelp:HtmlHelpW HH case HH_INITIALIZE not handled.
fixme:richedit:REExtendedRegisterClass semi stub
fixme:richedit:ME_HandleMessage EM_SETEDITSTYLE: stub
fixme:richedit:ME_HandleMessage EM_SETBIDIOPTIONS: stub
fixme:richedit:ME_HandleMessage EM_SETEDITSTYLE: stub
fixme:richedit:ME_HandleMessage EM_SETBIDIOPTIONS: stub
fixme:richedit:ME_HandleMessage EM_SETEDITSTYLE: stub
fixme:richedit:ME_HandleMessage EM_SETBIDIOPTIONS: stub
fixme:richedit:ME_HandleMessage EM_SETEDITSTYLE: stub
fixme:richedit:ME_HandleMessage EM_SETBIDIOPTIONS: stub

If I change the wine setting to Windows7 with winecfg, the installer is back to the initial behavior, with the "SingleImageWW.msi file not found" error.

[dimesio]

Setup is unable to proceed due to the following error:
TO install and use this product, you must be running one of the following operating systems:
x86 platform
-Windows 7
- Windows Vista SP1
- Windows XP SP3
- Windows Server 2003 SP2

Was the Windows version set to XP in winecfg? (I figure it was, just want to check.)

Are you sure the wineprefix is really 32 bit? Looking back at what you posted earlier:

Code: Select all

env WINEARCH=win32 WINEPREFIX=~/.wine32
WINEPREFIX=~/.wine32 wine msiexec /i msxml6_x86.msi

wine: created the configuration directory '/home/infeld/.wine32'

If you entered those commands in the terminal exactly as you posted them here, then you did not create a 32 bit wineprefix. Nothing would be created by the first line, because you didn't run Wine. The second line is what created the wineprefis, and the architecture wasn't specified there, so it would default to 64 bit.

What subdirectories are listed in drive_c of the wineprefix you think is 32 bit? If there's one called Program Files (x86), it is not 32 bit.

[ookimi]

Thanks for the reply! Indeed, my supposedly 32-bit wineprefix was actually 64-bit. That was stupid of me indeed. It was the Windows XP setting, though.

I tried these commands now:

Code: Select all

WINEARCH=win32 WINEPREFIX=~/.wine32 winecfg
WINEPREFIX=~/.wine32 wine setup.exe

Now the office starts to be installed to the right Program files folder (there is no Program files(x86)). But it crashes with the same SingleImageWW.msi-not-found error. I don't understand... that file DOES get unpacked to where it is supposed to be, and before the installer craches!

Moreover, yesterday wine was giving me those error messages about p11-kit-trust.so and gnome-keyring-pkcs11.so. This seems to be a common problem with wine. So I googled it up and solved it by putting the right .so files where wine thinks they should be. No more error messages about them. But - alas - this doesn't help the installation at all!

[ookimi]

The most annoying thing is that the damn SingleImageWW.msi file actually does get unpacked to where it needs to be!

It looks like people on Windows get that error too, when they try to install office over a previous trial installation. It happens when something in the registry is not cleaned up or something. But with the wine we are creating a brand new hard disk, it cannot have any traces of the previous attempts. Right?

I now have Crossover and PlayOnLinux installed, too. And they, too, supposedly performed their attempts by creating separate wine prefixes. Could it be that they somehow interfere with one another, or that something gets changed in the general wine installation and later influences the new prefixes?