I see: when Apple rolls-out a quick fix then it's praise all 'round. "Kudos to Apple for reacting so fast, thanks Steve". When Microsoft however does the same it's because of their crap software. Am I correct? Are you of the first school?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Microsoft Releases Office 2011 14.0.1 Update
- Thread starter MacRumors
- Start date
- Sort by reaction score
I see: when Apple rolls-out a quick fix then it's praise all 'round. "Kudos to Apple for reacting so fast, thanks Steve". When Microsoft however does the same it's because of their crap software. Am I correct? Are you of the first school?
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_1 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8B117 Safari/6531.22.7)
The update won't install if you have at any point moved office 2011 from the applications folder - it says it cannot find office on Macintosh HD to do the upgrade. I like to keep third-party applications in a folder inside my applications folder so I'm SOL. Microsoft say this is a known bug, and apparently have no intention of fixing it. Their fix: uninstall office, reinstall it from scratch, don't move it again. That's just effing lazy.
The update won't install if you have at any point moved office 2011 from the applications folder - it says it cannot find office on Macintosh HD to do the upgrade. I like to keep third-party applications in a folder inside my applications folder so I'm SOL. Microsoft say this is a known bug, and apparently have no intention of fixing it. Their fix: uninstall office, reinstall it from scratch, don't move it again. That's just effing lazy.
Obviously you didn't read the second half of my comments, and haven't been using Microsoft products on a Mac for very long. The MacBU is perpetually in the dark when it comes to keeping release and feature parity with the Windows versions of Office, and they've been botching up parts of Office on Mac ever since Outlook Express on OS9.
After installing the stupid update all my Address Book contacts are gone. Thank God for iPhone backup...
After the early officemac 2008 debacle (constant crashes, glitches, etc) I'm finally sitting on a nice stable software package after a ton of updates.
No way I'll even attempt to install 2011 until, eh, a year from now at least. Lessons learned are hard to shake off.
No way I'll even attempt to install 2011 until, eh, a year from now at least. Lessons learned are hard to shake off.
Okay. How about Mac OS 10.6 Snow Leopard. Relased August 28th, 2009.
Mac OS 10.6.1 released September 10, 2009.
I too have no contacts and like you am gratefull for my iphone sync. Holy crap office! WTF happened?
Nope not gonna rant. Pretty happy so far with Office 2011, but wiping my contacts? thats 1800 i would have to re-enter.
I also have backups but faster to re-sync.
I see: when Apple rolls-out a quick fix then it's praise all 'round. "Kudos to Apple for reacting so fast, thanks Steve". When Microsoft however does the same it's because of their crap software. Am I correct? Are you of the first school?
No, I am in school that installed office 2011 and noticed that 2008 was still there. Not even an option to remove it. I lay blame where it's due. Yes Apple has been screwing up a bit as well. I am pretty much forced to use the MS Office because my clients send me files using it, and office 2011 is an improvement.
BTW why does the new MS installer still spin the ancient black and white mac ball. Is that Rosetta thing?
Problem that update don't repair
Something happens...
11/11/10 21:23:39 Microsoft Excel[1285] Cannot find function pointer ExcelPrintPDEPluginFactory for factory A51FBA8C-FBAF-11D4-A260-0030656AD6FE in CFBundle/CFPlugIn 0x237f7f40 </Applications/Microsoft Office 2011/Microsoft Excel.app/Contents/PlugIns/ExcelPrintPDE.plugin> (bundle, loaded)
and the update don't repair this...
(can't print page ranges, like 10 to 12)
Something happens...
11/11/10 21:23:39 Microsoft Excel[1285] Cannot find function pointer ExcelPrintPDEPluginFactory for factory A51FBA8C-FBAF-11D4-A260-0030656AD6FE in CFBundle/CFPlugIn 0x237f7f40 </Applications/Microsoft Office 2011/Microsoft Excel.app/Contents/PlugIns/ExcelPrintPDE.plugin> (bundle, loaded)
and the update don't repair this...
(can't print page ranges, like 10 to 12)
How about some exchange 2003 support?
Arbitrary and capricious come to mind when I try to think of reasons not to support the large installed base of those users
Arbitrary and capricious come to mind when I try to think of reasons not to support the large installed base of those users
Installed the 14.0.1 update and other than the annoying "must close Safari" message, it seems ok.
Of course you have read the installation notes first "Note: You can install Office for Mac 2011 side by side with an earlier version of Office. However, if you want users to use only Office for Mac 2011, remove the earlier version."
No matter what OS one is using, it's always best to quit all running applications before installing software or software updates. People who fail to do that often later complain of various problems.
It's only recommended when 1) the application to be installed works together with some application already installed and open 2) the application to be installed is badly written and can cause problem even if it doesn't work together with some application already installed and open.
In this cause it's clear that it's 2), as Office has no association with Safari whatsoever and thus has no reason to demand quitting Safari.
And of course if it isn't a problem for you then it isn't a problem at all, right?
Anyone know if they might add support for Exchange 2003? Two Pharma companies I know of are still on Exchange 2003 and we cannot upgrade at this time.
Nope it only supports Exchange 2007 and later.
Question: Why aren't they upgrade at this time? Assuming they have some grey matter they should automatically get the latest version if they're signed up to 'Software Assurance'.
The company I work at and am the Exchange admin for has a license for 2007, but the upgrade path is not an in place, since 2007 is 64-bit and requires not only a server that is 64-bit but also a 64-bit OS, which may not have been included in a Software Assurance update.
Our license terms got us Exchange 2003/2007, but didn't include the OS upgrade. Which is why we are stuck at 2003 for now and may be the reasons others are stuck, too. That and time to migrate to a new server.
Our license terms got us Exchange 2003/2007, but didn't include the OS upgrade. Which is why we are stuck at 2003 for now and may be the reasons others are stuck, too. That and time to migrate to a new server.
I see: when Apple rolls-out a quick fix then it's praise all 'round. "Kudos to Apple for reacting so fast, thanks Steve". When Microsoft however does the same it's because of their crap software. Am I correct? Are you of the first school?
Apple and Microsoft making crappy software together made me lose several hours worth of work and miss a deadline. Office crashed, and it didn't autosave because OS X was having some random problems with writing to the ssd(again) so all hte work was lost. Yes, I know, I should learn to save manually, and I learned to do so back in 1995. Over the past few years, however, I became used to having a stable system with windows 7 and office 2007, and stopped constantly worrying about it.
As a relatively new mac user I have come to the conclusion that OS X kinda sucks, and the mac version of office is even suckier. It is pretty ridiculous that I have to use a virtual/bootcamp version of windows 7 and office 2010 when I want to get some work done without having to worry about constant crashes(nevermind the complete lack of onenote or anything even remotely as good on os x).
