Office 2013 with Wine 2.0

[pmorch]

I'm surprised that I can't find any posts anywhere about how to install Office 2013 in Wine 2.0. As I understand from the Wine 2.0 announcement, the main highlights are the support for Microsoft Office 2013 (and the 64-bit support on macOS).

Before I bore you with the details of the errors I'm seeing, first I'd like to see if there is some documentation or a howto I've missed. I see that crossover office has support for Office 2013, but can I expect that Office 2013 should just install and run under vanilla Wine 2.0 too?

I also don't understand why neither the appdb entry for Office 2013 (32 bit - installer only) nor the appdb entry for Word 2013 (32 bit) even mention 2.0, and Word 2013 is listed mostly as garbage, but otherwise has bronze support.

Here is what I tried, somewhat based on the only recent Office 2013 thread I could find: MS Office 2013 install STOP with Wine 2.0:

• Fresh Ubuntu Xenial 16.04 under VMware - dist-upgraded and with VMware tools installed
• Followed ubuntu installation from wiki
  • sudo dpkg --add-architecture i386
  • sudo add-apt-repository ppa:wine/wine-builds
  • sudo apt-get update
  • sudo apt-get install --install-recommends winehq-staging
• sudo apt-get install wine-mono winbind p11-kit:i386
• winecfg -> change to Windows 7
• sha1sum /mnt/hgfs/home/Downloads/OfficeProfessionalPlus_x86_en-us.img #36a70d4d1a2f42282f4d7175a37264a57da35a91
• sudo mount -o loop /mnt/hgfs/home/Downloads/OfficeProfessionalPlus_x86_en-us.img office2013
• wine setup.exe 2>&1 | tee ~/office2013.log

Result: A dialog box saying: "Microsoft Office Professional Plus 2013 encountered an error during setup." and a "Close" button. At the time the dialog box was shown, there were 11944 lines in the file (it grew further when I hit "Close"). Here is office2013.log.

What did I do wrong?

[dimesio]

can I expect that Office 2013 should just install and run under vanilla Wine 2.0 too?

The most recent AppDB test report suggests yes.

I also don't understand why neither the appdb entry for Office 2013 (32 bit - installer only) nor the appdb entry for Word 2013 (32 bit) even mention 2.0,

Because no one has submitted a test report for it.

Fresh Ubuntu Xenial 16.04 under VMware - dist-upgraded and with VMware tools installed

Test a real install. VMs introduce problems of their own, particularly with their graphics drivers. Office 2013 is affected by https://bugs.winehq.org/show_bug.cgi?id=38648.

[*] sudo apt-get install --install-recommends winehq-staging

Use the development release.

[*] sudo mount -o loop /mnt/hgfs/home/Downloads/OfficeProfessionalPlus_x86_en-us.img office2013

Instead of mounting the image, try extracting the files to a directory and running setup from there.

I don't see where you created a clean 32 bit wineprefix. You need to.

[moreje]

well, a full tutorial would be welcome

[marin]

Hi guys,

I have tried it also on elementary os 0.4 which is based on ubuntu 16.04 on physical hardware.
I have created clean 32 bit wine prefix, I am running wine-devel_2.0.0~ubuntu16.04.1_amd64 from the official winehq repo.
I ran the setup.exe both from mounted and from extracted .iso of Office 2013 Pro 32 bit.
I have tried with both windows 7 and windows 10 as platform setting in wine config with the same outcome.
The installation progress meter reaches almost half and then the install fails as in pmorch's report.

Seems we're both missing something which might be obvious to more experienced users of wine but I will be really grateful if I can get another hint...

Thank you!

[dimesio]

Have you tried the workaround from https://bugs.winehq.org/show_bug.cgi?id=38648#c22?

[marin]

Hi dimesio,

I have just tried it. I created the key following the bug tracker suggestion and the wiki article (https://wiki.winehq.org/Useful_Registry_Keys).
This is how my Registry looks like:

Unfortunately I still got the same error:

Looking at the console output seems there is not much change.
Below are the last few lines when error occurred, before I clicked the "Continue" (or whatever it was) button:

Code: Select all

fixme:rpc:handle_bind_error unexpected status value 1765
err:rpc:RpcAssoc_BindConnection rejected bind for reason 0
fixme:msi:MsiEndTransaction 0
fixme:advapi:EventProviderEnabled deadbeef, 4, 2: stub
fixme:d3d11:d3d11_immediate_context_OMSetBlendState Ignoring blend factor {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}.
fixme:advapi:EventProviderEnabled deadbeef, 4, 2: stub
fixme:advapi:EventProviderEnabled deadbeef, 4, 2: stub

Did I omit something or did something wrong for the registry key creation ?
Also since people are discussing videocards and drivers - does it matter what I have ? I run old nVidia 8600GT with nvidia 340.101 proprietary driver.

Thanks again!

[zjhzxhz]

Hi dimesio,

I have just tried it. I created the key following the bug tracker suggestion and the wiki article (https://wiki.winehq.org/Useful_Registry_Keys).
This is how my Registry looks like:

Unfortunately I still got the same error:

Looking at the console output seems there is not much change.
Below are the last few lines when error occurred, before I clicked the "Continue" (or whatever it was) button:

Code: Select all

fixme:rpc:handle_bind_error unexpected status value 1765
err:rpc:RpcAssoc_BindConnection rejected bind for reason 0
fixme:msi:MsiEndTransaction 0
fixme:advapi:EventProviderEnabled deadbeef, 4, 2: stub
fixme:d3d11:d3d11_immediate_context_OMSetBlendState Ignoring blend factor {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}.
fixme:advapi:EventProviderEnabled deadbeef, 4, 2: stub
fixme:advapi:EventProviderEnabled deadbeef, 4, 2: stub

Did I omit something or did something wrong for the registry key creation ?
Also since people are discussing videocards and drivers - does it matter what I have ? I run old nVidia 8600GT with nvidia 340.101 proprietary driver.

Thanks again!

The same here... running with Wine 2.3 in ArchLinux.
Please help me.

[marin]

For the record, I have changed videocard to:
[AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM]
I am using the open source Radeon driver. No change in the outcome though.

[marin]

FYI repeated the test with 2.4 ,same results.
Oddly (or expectedly) when I ran wine it re-downloaded Mono. I assume all my prefix settings are intact still?
I tend to think right now that announcing the Office 2013 compatibility was just a marketing trick to get attention...

rant:
Generally I don't mind going for Crossover Office and eventually I will, just wonder how ethical it was to mislead me (and obviously number of other folks) with this claim to spend time definitely worth more than the software price (the crossover office).
As we're all here in the open source world primarily on the grounds of ethics, I would like to believe.

[Bob Wya]

FYI repeated the test with 2.4 ,same results.
Oddly (or expectedly) when I ran wine it re-downloaded Mono. I assume all my prefix settings are intact still?
...

Simple...
Wine version 2.4 moves to targeting Wine Mono version 4.7.0.
Wine version 2.0-2.3 targets Wine Mono version 4.6.4.

Wine Mono, if installed, represents a seperate application installation in each WINEPREFIX. As such it will show up, in your list installed applications, if you run:

Code: Select all

wine uninstaller

for a given WINEPREFIX.

Bob

[dimesio]

File a bug for your problem installing Office 2013.