Microsoft Office 2013 Forum

Hi. I've been auditing Crossover on a Fedora 25 desktop. I am able to install Office 2013 32-bit but it will not activate. After I enter my email and password a pop-up dialogue states "Sorry, we cannot connect to your account. Please try again later." Any help would be greatly appreciated.

Thank you

Also having this problem with office 2013 32-bit on ubuntu 16.04

Same. Running v16.0.0

:~$ /opt/cxoffice/bin/cxgetsysinfo  | head -100
#------------------------------------------------------------------------
#  System Information; Thu Feb 16 22:24:08 EST 2017
#------------------------------------------------------------------------
COMMAND uname -a
Linux HOSTNAME 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
----------
FILE /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"

Well, not exactly the same... for me, it seems like the Windows activation service is not running:
We're sorry. something went wrong and we can't do this for your right now. Please try again later. (0x80070426)

What's more annoying, is that even the telephone activation system is busted. Selecting my country (Canada), doesn't provide me with a telephone number (OK can Google that), but the "Installation ID" is blank, and stuck with a unpopulated variable "[installation code]".

In an attempt to manually activate using the command line,
http://helpdesk.maytechgroup.com/support/solutions/articles/3000005485-how-to-activate-office-2010-or-2013-from-command-line
https://technet.microsoft.com/en-us/library/ee624350.aspx

These steps, unfortunately return "empty" results (nothing seems to work)
(within the Office bottle, Run Command -> "cmd", which opens a good ole' Windows terminal)

cd "C:\Program Files\Microsoft Office\Office15"

cscript ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript ospp.vbs /act
cscript ospp.vbs /dstatus 

Seems like the cscript ospp.vbs doesn't quite work in the bottle...

c:\Program Files\Microsoft Office\Office15>cscript -h
c:\Program Files\Microsoft Office\Office15>cscript /?
c:\Program Files\Microsoft Office\Office15>cscript /h
c:\Program Files\Microsoft Office\Office15>cscript foo
c:\Program Files\Microsoft Office\Office15>cscript ospp.vbs /help
c:\Program Files\Microsoft Office\Office15>cscript ospp.vbs /h
c:\Program Files\Microsoft Office\Office15>cscript ospp.vbs /?

The local file shows how to use it, but clearly she's broken; (anyone else?)
file:///home/$USER/.cxoffice/Microsoft_Office_2013/drive_c/Program%20Files/Microsoft%20Office/Office15/OSPP.HTM

Finally, I just light-bulb connected with this: https://www.codeweavers.com/support/forums/announce/?t=24;mhl=193570;msg=193570#msg193570

  * Fixed a problem which could prevent Microsoft Office 2010
    from completing online activation.

So /hopefully/ cxoffice 16.1.0 fixes this issue?

As a further note, we should clarify if we're trying to activate KMS vs. MAK. KMS is corporate and requires a local server, MAK is Micrsoft activation directly.
(I'm trying for MAK, I have a retail key)

Hi Matt,

Would you please elaborate on how you managed to activate? I follow the link you posted but it only redirects me to the Crossover 16 announcement.
I'm not sure about you but I'm already running CrossOver 16 and stil am unable to activate.

Cheers

To be clear, I have yet to successfully activate.

In fact, I recently had sales/support bump my version/download access to 16.1.0 so that we could test the fix, but the same issue persists.

Even running 16.1.0, Microsoft Office 2013 fails to activate with the same behaviour as I described above from 16.0.0.
(despite the 16.1.0 release claiming to fix the issue)

I hope codeweavers support can comment.

I'm in the same boat. My trial ended yesterday. I'm very eager to buy this if I can get Office to activate.

Hey everyone!

If you are having activation issues, I would encourage you to submit a support ticket. We have seen this issue occur with a few of our other users but it looks like it can be a variety of things that are causing MS Office 2013 not to activate.

https://www.codeweavers.com/about/contact-us#support

Some things you can try in the mean time: I would suggest attempting a login on your Microsoft account, and checking the number of activations you have left though. We have found that some users don't have enough activations left because a OS upgrade counts as a 'new computer' in some cases.

Other useful information you can provide in your ticket is either a system report (Mac) or glxinfo into your terminal (Linux), as well as a debug log.

https://www.codeweavers.com/support/wiki/mac/mactutorial/submittechsupportlog (Mac)
https://www.codeweavers.com/support/wiki/linux/linuxtutorial/debug (Linux)

In the 'Extra Logging Channels' input: +seh,+tid

And a screenshot of the error you're seeing. Add these to your ticket and we'll take a look! :)

I'm also having issues. I cannot sign in, and i cannot use the 'activation key' either. The dialog box does not allow me to enter certain characters for some reason.

Thanks Katie. Here's a screenshot. My 14-day test period ran out so I'm afraid I can't trouble shoot it more.

Just an update. Also tried on 16.1. No dice. Filed a support ticket.

Another update. Thanks to Andrew and Katie at Codeweavers support, a work around has been found. They really were very responsive and helpful in identifying the issue and creating a fix. I'm told there will be a patch in upcoming 16.2 roll out.

Was this a very detailed workaround? Any way to share?

Retested on v16.2.0, using KMS. Activation fails for corporate Internet activation.

16.2.5

I tried with the same regedit trick for office2010
Nothing;

I tried from linux terminal with:

/opt/cxoffice/bin/wine --bottle Microsoft_Office_2013 ~/.cxoffice/Microsoft_Office_2013/drive_c/windows/system32/cscript.exe ./Program\ Files/Microsoft\ Office/Office15/OSPP.VBS /act

&
/opt/cxoffice/bin/wine --bottle Microsoft_Office_2013 ~/.cxoffice/Microsoft_Office_2013/drive_c/windows/system32/cscript.exe ./Program\ Files/Microsoft\ Office/Office15/OSPP.VBS /sethst:kms01:MYcorporateserver.edu

I tried opening cmd through wine with the same commands and nothing.
I will try to see in a windows installation what are the reg keys.

[/code]

Also trying to activate. I have opened a ticket. No luck so far.

Debian Stretch 9.2, Crossover 16.2.5, Microsoft Office 2013 32 bit VLK. After installation of MSOffice, at Account -> Product Information I introduce the serial number. A message confirm that's OK. After restart, appear a wizard with activation with 2 options: activate over internet or by telephone. Over the internet, the same message "We couldn't contact the server ...", and by telephone it is impossible because "Telephone activation is no longer supported for your product".

I confirm that I have the same problem described above.

Serial number is ok because I used yesterday on MSOffice on Windows.

Les comparto mi experiencia: a mi no me funciono el comando regedit dentro de la botella de office 2013, pero le di clic a panel de control, administrador de tareas, archivo, nueva tarea y ahí escribí regedit y me funcionó! de ahí seguí los pasos para el registro de office, en local machine, software, office, 15 y eliminé registration y listo, funciono!! espero les sirva

I can confirm, that this problem still exists with Crossover 17.5.1. Activation using a corporate server is not possible. The cscript commands simply seam to have not effect at all.

Hi!

I'm trying to active Office 2016 by using the KMS strings in registry. No success. So this is still a problem in wine? Or is there a component missing.
Is there a way to debug this?

When I execute "cscript ospp.vbc /act" (in folder ...\Office16), I retrieve following debug output (after installing IE 8 😊 ):

016c:fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
016c:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
016c:err:ole:CoGetClassObject class {6c736db1-bd94-11d0-8a23-00aa00b58e10} not registered
016c:err:ole:CoGetClassObject no class object {6c736db1-bd94-11d0-8a23-00aa00b58e10} could be created for context 0x1
016c:fixme:ole:CLSIDFromProgIDEx L"Scripting.FileSystemObject",0x33ef90: semi-stub
016c:fixme:wbemdisp:factory_QueryInterface interface {0000011a-0000-0000-c000-000000000046} not implemented
016c:err:ole:apartment_getclassobject DllGetClassObject returned error 0x80004002
016c:err:ole:create_server class {172bddf8-ceea-11d1-8b05-00600806d9b6} not registered
016c:fixme:ole:CoGetClassObject CLSCTX_REMOTE_SERVER not supported
016c:err:ole:CoGetClassObject no class object {172bddf8-ceea-11d1-8b05-00600806d9b6} could be created for context 0x15
016c:fixme:wbemdisp:WinMGMTS_ParseDisplayName ignoring security settings
016c:err:winediag:wined3d_dll_init Disabling multithreaded command stream.
016c:err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version to 3.2.
016c:trace:winsock:DllMain 0x7d960000 0x1 (nil)
016c:fixme:wbemdisp:services_QueryInterface interface {fc4801a3-2ba9-11cf-a229-00aa003d7352} not implemented
016c:fixme:wbemdisp:services_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:services_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:objectset_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:objectset_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:enumvar_QueryInterface interface {00020400-0000-0000-c000-000000000046} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:services_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:services_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:objectset_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:objectset_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:enumvar_QueryInterface interface {00020400-0000-0000-c000-000000000046} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:object_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:services_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:fixme:wbemdisp:services_QueryInterface interface {a6ef9860-c720-11d0-9337-00a0c90dcaa9} not implemented
016c:err:wbemprox:wql_error syntax error, unexpected TK_NULL, expecting TK_FALSE or TK_TRUE or TK_INTEGER or TK_STRING
016c:fixme:ole:CLSIDFromProgIDEx L"Msxml2.DOMDocument.6.0",0x33e680: semi-stub
0172:trace:winsock:DllMain 0x7d960000 0x2 (nil)
0173:trace:winsock:DllMain 0x7d960000 0x2 (nil)
016c:trace:wininet:DllMain 0x7cd70000,1,(nil)
016c:trace:wininet:InternetCrackUrlW (L"file:///c:/Program%20Files/Microsoft%20Office/Office16/slerror.xml" 0 0 0x33e16c)
016c:trace:wininet:set_url_component (null) (0)
016c:trace:wininet:GetInternetSchemeW L"file" 4
016c:trace:wininet:set_url_component L"file" (4)
016c:trace:wininet:set_url_component (null) (0)
016c:trace:wininet:set_url_component (null) (0)
016c:trace:wininet:set_url_component (null) (0)
016c:trace:wininet:set_url_component L"/c:/Program%20Files/Microsoft%20Office/Office16/slerror.xml" (59)
016c:trace:wininet:InternetCrackUrlW L"file:///c:/Program%20Files/Microsoft%20Office/Office16/slerror.xml": scheme(L"file") host((null)) path(L"/c:/Program%20Files/Microsoft%20Office/Office16/slerror.xml") extra((null))
016c:trace:wininet:InternetCrackUrlW (L"file:///c:/Program%20Files/Microsoft%20Office/Office16/slerror.xml" 0 0 0x33e024)
016c:trace:wininet:set_url_component (null) (0)
016c:trace:wininet:GetInternetSchemeW L"file" 4
016c:trace:wininet:set_url_component L"file" (4)
016c:trace:wininet:set_url_component (null) (0)
016c:trace:wininet:set_url_component (null) (0)
016c:trace:wininet:set_url_component (null) (0)
016c:trace:wininet:set_url_component L"/c:/Program%20Files/Microsoft%20Office/Office16/slerror.xml" (59)
016c:trace:wininet:InternetCrackUrlW L"file:///c:/Program%20Files/Microsoft%20Office/Office16/slerror.xml": scheme((null)) host((null)) path((null)) extra((null))
016c:fixme:heap:RtlSetHeapInformation 0x110000 1 (nil) 0 stub
016c:fixme:wer:WerRegisterMemoryBlock (0x10009b9c 4) stub
016c:fixme:vcruntime:__telemetry_main_invoke_trigger (0x10000000)
016d:trace:wininet:DllMain 0x7cd70000,3,(nil)
016d:trace:winsock:DllMain 0x7d960000 0x3 (nil)
016c:fixme:vcruntime:__telemetry_main_return_trigger (0x10000000)
016c:trace:wininet:DllMain 0x7cd70000,0,0x1
016c:trace:winsock:DllMain 0x7d960000 0x0 0x1

The script reports "ERROR DESCRIPTION: An unknown error occurred"

When I execute ""cscript ospp.vbs /sethst:1.2.3.4" (1.2.3.4 is a dummy ip adress for our company KMS server), I get similar wine output and the script returns:

"No Office KMS licenses were found on the system."

Is there anything I can do to further debug or analyse the problem?

I have an Office 2013 installer with a KMS key. It works on CrossOver 17.5.1 but not 18.0
Entering the licence key prompts me to seek internet verification of the key which fails, and then it wants me to call support to get a installation confirmation number.
I actually did this, and the Microsoft support staff told me the key was valid, but I needed help from the corporate team, so she forwarded me ... but the destination was out of office hours and end of call.

So I'm back to to 17.5.1, which accepts the key as soon as I enter it.

Hi all, mine is slightly different, I have installed MS Office 2013 (Word, Excel, Powerpoint Outlook) everything is working except I can not 'Sign in to Office' with my microsoft account and therefore the software can not be verified. When I attempt to sign in, I get to the first screen where i enter my email address and then it gets to the next screen where i should type in my password and it is a blank screen.

Hello Jody,

Are you using the latest release of CrossOver? The blank password-entry sounds like a bug we resolved for Office 365 in CrossOver 18.5.

Hana

Hello,

Yes running 18 latest version.

I'm on trial version 18.0.0, how do i get version 18.5

Hi, i have just purchased crossover, how do i get version 18.5?

Hi Jody,

You should be able to download a copy of CrossOver 18.5 from this website. In the top right corner, hovering over "My Account" creates a drop-down menu. Click on "My Downloads" and you will be able to download the latest version of CrossOver there.

Thanks,
Anna