Unable to open .docx files after conducting March 2010 Microso
in [Windows Update]
|
Prev: Installation Failure Error Code: 0x80070641
Next: Unable to open .docx files after conducting March 2010 MicrosoftUpdate
From: infinite jest on 13 Mar 2010 13:52 On Fri, 12 Mar 2010 07:54:01 -0800, Sam Theivagt wrote: > We have the same issue. There is also an issue of being unable to open > (convert) .xlsm files. This only occurs on our Windows 2000 PCs with > Office 2003 & the Office 2007 Compatibility Pack. > > 977724 updates MSO.DLL in > > C:\Program Files\Common Files\Microsoft Shared\OFFICE12 > > 977724 does not show up in Add/Remove programs, but I was able to find > an older version of MSO.DLL in the Windows Installer patch cache: > > > C:\WINNT\Installer\$PatchCache$\Managed\00002109020090400000000000F01FEC \12.0.6425\ > > To verify that the problem is caused by the MSO.DLL from 977724, I > renamed the MSO.DLL in > > C:\Program Files\Common Files\Microsoft Shared\OFFICE12 > > & copied the MSO.DLL I found in the patch cache to the above location. I > was then able to open (convert) .docx files in Word 2003 & .xlsm files > in Excel 2003. > > The version of MSO.DLL installed by 977724 is 12.0.6521.5000 & is dated > 10/29/2009. The version from the patch cache is 12.0.6425.1000 & is > dated 04/03/2009. > <...> > Replacing the mso.dll, as you described, instantly fixes the broken computers on my network. Thanks for tracing this through.
From: Ottmar Freudenberger on 15 Mar 2010 01:23 "PA Bear [MS MVP]" <PABearMVP(a)gmail.com> schrieb: > Chris wrote: >> The update has been pulled: >> >> http://blogs.technet.com/wsus/archive/2010/03/11/expired-update-kb977724.aspx > KB977724 wasn't one of the March 2010 updates anyway. That may not be true for those having .NET Framework 4.0 *Beta*/CTP/RC installed. http://blogs.technet.com/office_sustained_engineering/archive/2010/03/11/issues-with-office-after-installing-kb977724.aspx | KB977724 is a non-security update that allows support of .NET 4.0 | components within the Office 2007 system. This was published in a | limited release through the Download Center in February, and more | broadly through MU in March. FWIW, Freudi
From: Liz on 15 Mar 2010 11:30 This fix helped me as well. Thank you. Liz > Replacing the mso.dll, as you described, instantly fixes the broken > computers on my network. > > Thanks for tracing this through. > . >
From: jake1453 on 26 Mar 2010 05:21 On Mar 12, 3:54 pm, Sam Theivagt <Sam Theiv...(a)discussions.microsoft.com> wrote: > We have the same issue. There is also an issue of being unable to open > (convert) .xlsm files. This only occurs on our Windows 2000 PCs with Office > 2003 & the Office 2007 Compatibility Pack. > > 977724 updates MSO.DLL in > > C:\Program Files\Common Files\Microsoft Shared\OFFICE12 > > 977724 does not show up in Add/Remove programs, but I was able to find an > older version of MSO.DLL in the Windows Installer patch cache: > > C:\WINNT\Installer\$PatchCache$\Managed\00002109020090400000000000F01FEC\12.0.6425\ > > To verify that the problem is caused by the MSO.DLL from 977724, I renamed > the MSO.DLL in > > C:\Program Files\Common Files\Microsoft Shared\OFFICE12 > > & copied the MSO.DLL I found in the patch cache to the above location. I was > then able to open (convert) .docx files in Word 2003 & .xlsm files in Excel > 2003. > > The version of MSO.DLL installed by 977724 is 12.0.6521.5000 & is dated > 10/29/2009. The version from the patch cache is 12.0.6425.1000 & is dated > 04/03/2009. > > I tired installing the hotfix from > > http://blogs.technet.com/office_sustained_engineering/archive/2010/03... > > It does NOT fix this issue. > > > > "Susan Bradley" wrote: > > Bruce wrote: > > > I did open a case: Support Request Number - 1127134209 > > > > As for your question on having 977724 installed, I don't know how to verify, other than going onto Microsoft Update, reviewing my update history, and it showing that I successfully installed 977724. > > > > --- > > > frmsrcurl:http://msgroups.net/microsoft.public.windowsupdate/Unable-to-open-doc... > > Office Sustained Engineering : Issues with Office after installing KB977724: > >http://blogs.technet.com/office_sustained_engineering/archive/2010/03... > > > Check that out > > .- Hide quoted text - > > - Show quoted text - I think this is also my problem. Of all the many thousands of users out there who might be suffering from this issue, apparently caused by a MS update, only a few will be sophisticated enough to mess around in the innards of the programs to extract the relevant file. Many won't know where to go to for help. I don't fancy doing it as if I mess it up I have no idea what the consequences might be. Why aren't Microsoft acknowledging this and removing the update? How can pressure be applied? It's a disgrace. Would an easier solution be to uninstall the updates which are supposed to have caused the problem? Any downside to this? thanks again
From: PA Bear [MS MVP] on 26 Mar 2010 09:50
See the Known Issues section ("This problem can occur if the file is saved to a network location and then configured as a shared workbook) of http://support.microsoft.com/kb/978474. For home users, no-charge support is available by calling 1-866-PCSAFETY (and/or 1-866-234-6020 and/or 1-800-936-5700) in the United States and in Canada or by contacting your local Microsoft subsidiary. There is no-charge for support calls that are associated with security updates. When you call, clearly state that your problem is related to a Security Update and cite the update's KB number (e.g., KB978474). Or you can... Start a free Windows Update support incident request: https://support.microsoft.com/oas/default.aspx?gprid=6527 Customers who experience issues installing Microsoft security updates also can visit the following pages for assistance: https://consumersecuritysupport.microsoft.com/ http://support.microsoft.com/ph/6527#tab3 For more information about how to contact your local Microsoft subsidiary for security update support issues, visit the International Support Web site: http://support.microsoft.com/common/international.aspx For enterprise customers, support for security updates is available through your usual support contacts. -- ~Robear Dyer (PA Bear) MS MVP-IE, Mail, Security, Windows Client - since 2002 jake1453 wrote: <snip> > I think this is also my problem. Of all the many thousands of users > out there who might be suffering from this issue, apparently caused by > a MS update, only a few will be sophisticated enough to mess around in > the innards of the programs to extract the relevant file. Many won't > know where to go to for help. I don't fancy doing it as if I mess it > up I have no idea what the consequences might be. Why aren't > Microsoft acknowledging this and removing the update? How can pressure > be applied? It's a disgrace. > > Would an easier solution be to uninstall the updates which are > supposed to have caused the problem? Any downside to this? > > thanks again |