Office 2013 - CTR

satanicguardian

satanicguardian

satanicguardian

Associate
Joined
20 Aug 2007
Posts
1,333
Location
Solihull
This is getting bloody ridiculous now - MS need to sort these kind of things out.

I'm trying to install Office 2013 suite from our E3 365 subscription on a PC, initially the software had gone corrupt on this one machine, so I uninstalled then reinstalled, got the usual errors about Click to run already being installed, so I ran the MS Fix it tool that it directed me to, same errors about it already being installed, repeated and then also deleted the registry keys for it.

This time the installation started but crashed almost instantly, giving me the ever helpful error message of "something went wrong".

At this point, I thought sod it and reinstalled windows from scratch, full partition delete, create and format, fresh windows 7 32bit on this machine. Installed necessary drivers and updated, I tried to install Office from the 365 portal again, Boom instantly I get this:



I kept trying to install it, deleting registry keys etc - the hyperlink in the above error takes me to the following page:

http://support.microsoft.com/kb/2827031

It tells me to use online repair via add/remove programs, slight problem..



There is literally nothing installed, there is also no registry keys at all under HKEY_LOCAL_MACHINE



Has anyone else experienced this before? I've had it a few times, but reinstalling windows will normally always fix this error as a last ditch attempt.

I'm getting reallyyyyyy p*ssed off at this error now, can anyone help?
 
I had something similar in the beta days, but blowing away Windows didn't fix it? That's pretty odd. Have you tried getting any support out of Microsoft?
 
Try the Windows Installer Clean Up utility (I've linked to a non-MS site as MS have replaced it with a fixit tool, which I've never used. Feel free to try it though.

The Installer Cleanup lists programs installed using Windows Installer, even on Windows 8, but I've no idea if it fixes issues still (for obvious reasons I'm not about to test it myself).
 
What's the state of the machine like? I'd give memtest a quick blast personally just to rule out the obvious. Also, you're not behind any sort of web proxy are you?
 
theheyes said:
What's the state of the machine like? I'd give memtest a quick blast personally just to rule out the obvious. Also, you're not behind any sort of web proxy are you?
Click to expand...

AHHHHHHH you may be onto something here, I have recently fitted a watch guard firewall into the server rack because of some nasty hackings recently, I have a feeling that streaming launchers do not like firewalls! :O
 
Having a similar problem myself, it should have installed office in "offline" mode but always streams when i start any office application for the first time of the day.
 
I would check the device subscription on the O365 portal to see if it lists that device. If it does, remove the association with the device and then re-install again
 
satanicguardian said:
This is getting bloody ridiculous now - MS need to sort these kind of things out.
Click to expand...

satanicguardian said:
Yup it was the [watchguard, hardware] fire wall :)
Click to expand...

Seems to me like you owe MS an apology ;)

There have been a number of "problems" with O365, mainly surrounding migration from an old domain (in our case, 2008R2, Exchange 2010) to a new domain (no trust, 2012, exchange 2013 in hybrid). There was also an issue with licensing and adding your newly acquired (volume) licenses to an expiring trial, but they have been addressed whist we have been working closely with CoreGB and MS over the last few months.
 
I'm not out of line saying that it needs sorting still :P I should be able to complain, I've lived and breathed MS for the last 10 years, even my bloody phone is windows :D

The streaming launcher does have it's fair share of problems in fairness
 
paradigm said:
Seems to me like you owe MS an apology ;)

There have been a number of "problems" with O365, mainly surrounding migration from an old domain (in our case, 2008R2, Exchange 2010) to a new domain (no trust, 2012, exchange 2013 in hybrid). There was also an issue with licensing and adding your newly acquired (volume) licenses to an expiring trial, but they have been addressed whist we have been working closely with CoreGB and MS over the last few months.
Click to expand...

To me, that's pretty much the standard migration route for most O365 tenants. Shove in 5 additional servers (azure would be good here), migrate, job done.

Licensing is still a pig, but if you have SA or EA then it's a lot easier to work out the kinks
 
You must log in or register to reply here.
Back
Top Bottom