Office 2008 SP2 kills cross platform file compatibility
Various sources, including Microsoft, indicate that PC created Open XML formated files cannot be opened after applying last week’s Office 2008 Service Pack 2 (SP2). Redmond’s recommending that users roll back to an earlier version in order to restore compatibility.
MacWindows is reporting that Office 2007 (i.e. Windows) Open XML formated documents (.docx), presentations (.pptx) and spreadsheets (.xlsx) cannot be opened by Macs running Office 2008 after applying the SP 2 Update from last week.
Thereupon, Microsoft’s Mac Business Unit is recommending that users try the following in order to restore compatibility:
• Remove Office manually, reinstall Microsoft Office 2008 for Mac from the original installation media, and then upgrade to Office 2008 for Mac 12.1.9 Update. Do not upgrade to Microsoft Office 2008 for Mac Service Pack 2 (12.2.0) from Microsoft AutoUpdate.
• Use Time Machine to roll back to Office 2008 for Mac 12.1.9 Update or an earlier version.
• Convert your document to .doc, .xls, or .ppt, by using Open XML Converter.
Maddeningly, this issue appears to affect different Macs and their users inconsistently.
“I have not had any problems with .pptx files, however after installing Office 12.2.0 on my Powerbook G4 I found that I could no longer open Windows-created .xlsx files, in particular, our expense voucher format — this matters a lot!” states one MacWindows reader. “I had to revert to Excel 12.1.7 using my Time Machine backup. At that point the .xlsx files opened fine.”
Given that most users don’t mirror their applications and files, it’s likely that the greater majority of people affected will be forced to manually convert files and/or manually roll back their Office 2008 installations. Neither prospect sounds very appealing.
Asleep at the switch…
It’s kind of hard to image that Microsoft didn’t test Office 2008 SP2 for cross-platform compatibility ahead of time, especially given that the Open XML format is a marquis feature in the software giant’s latest versions of Office for both the Mac and PC.
That said, it bears remembering that that every software vendor produces a steaming pile every now and then—yes, even Apple—but this particular case is a real head scratcher…
What’s your take?
Related Posts:
July 31st, 2009
What a complete pile of horse manure. We have seven computers in the office, the upgrade did not effect the admin laptop that we try all software and upgrades on first. Rolled it out on to the rest only to find 4 went gaga. (2 Imacs (intel) 1 G5 1 MacbookPro) Had to do a complete re-install.
I think thats the final nail in MS Office for us, we have been running iWorks in tandem and will now plan to switch over completely.
You know if Apple did this, image the hyperbole that would have been raised.
Get a Mac, get a life.
July 31st, 2009
This gives us IT people again so much work.
I must say that no one of my upgrades to SP2 went wrong, but I feel that it will appear very soon.
If there is one software on the Mac that gives me headaches sometimes, it is something from Microsoft. Either it is Word, or Powerpoint, or Excel, Entourage…
It is sad to see that Microsoft can get away with it…for so many years now. People keep on buying this sh*t.
I know I’m not using M$ applications at home.
July 31st, 2009
“t’s kind hard to image that Microsoft didn’t test Office 2008 SP2 for cross-platform compatibility ahead of time”
Actually it is not believable. More likely, is that it is a deliberate action forced on the MBU by other parts of MS. Create the perception that Macs are unreliable for business. The patch is already written, waiting for Monkeyboy to order it released.
If it was any other company, the above would be paranoid, but with MS, it is how they work.
July 31st, 2009
This is dismaying! As a workmate of mine once said, “It’s more likely incompetence than a conspiracy!”
They wouldn’t dare risk this on purpose as the MBU is a good revenue source… plus, it just reinforces the move towards open office adoptions and away from Microsoft’s! They’re going to take it on the chin.
It is a nuisance, although, in the interim, one could simply install one of the other freebie office packages and read the .docx, .xlsx docs until *Micro-soft-in-the-head* fixes this!
July 31st, 2009
OpenOffice 3.1
http://www.openoffice.org/dev_docs/features/3.0/#Microsoft_Office_2007_Import_Filters
How do I love thee?
July 31st, 2009
I so love the smell of conspiracy theories in the morning.
This is, pure and simple, a bug. There’s no “deliberate action” forced on us here in MacBU by anybody.
MacWindows is incorrect in reporting that it is cross-platform issue. It’s an issue where some files using the new XML-based file format were written without one important piece of it. We’re working to track down all instances were it could occur. There are some cases where the file originated from Windows Office and, at some point, this issue was introduced. There are cases where the file originated from Office:Mac and the issue was introduced.
It is most emphatically not the case that Office:Mac 2008 SP2 is unable to open all files that were created by Office for Windows. The cases where this happen appear to be pretty isolated, and they don’t seem to have a lot in common. We introduced stronger checking of our XML-based files, and we got bitten by it all at once.
Further, uninstalling and reinstalling is the last-ditch effort to get you working with your files again. The page that you linked to lists several potential workarounds, all of which are far less invasive than uninstalling and reinstalling. In case none of the previous ones work for you or are available to you, then the last thing that you can do if you have affected files is to go back to using 12.1.9. It’s not optimal, but access to your files is of utmost importance.
August 3rd, 2009
Not to fret!
Just open the Office 2007 XML files with iWork09. You can then export as non-XML Office files.
But then again, you may like the iWork apps so much that you just won’t bother to export back to Office files.
August 6th, 2009
Microsoft has released update 12.2.1 to fix this problem.
I don’t have this problem though. I was able to open any XML from other windows office. But still, I wonder why some macs have it, some others don’t.