Guest breaker19 Posted March 16, 2010 Posted March 16, 2010 'PA Bear [MS MVP Wrote: > 1661167']KB977724 wasn't one of the March 2010 updates anyway. > > Chris wrote: > > The update has been pulled: > > > > 'WSUS Product Team Blog : Expired Update KB977724' > (http://tinyurl.com/ye6lsne) Here is the description for 977724 in Windows Update/WSUS: Name: Update for the 2007 Microsoft Office System Classification: Critical Updates Description: Microsoft has released an update for the 2007 Microsoft Office System. This update provides the latest fixes to the 2007 Microsoft Office System. Additionally, this update contains stability and performance improvements. So this is an "update" for March. It's not a security-related update, but it is an "update" that was released and recommended by Microsoft. -- breaker19 Posted via http://www.vistaheads.com
Guest atlcomputech Posted March 16, 2010 Posted March 16, 2010 Unable to open .docx files after conducting March 2010 Microsoft U Hey Folks, It looks like the ver 12.0.6500.5000 (SP2) of the office compatability pack might also be an issue... ****We fixed the problem with the FileFormatConverter.exe ver 12.0.6015.5000**** We are running: 1) Windows 2000 sp4 2) Office 2003 sp3 When we ran microsoft update we skipped SP2 and acknowledged the first 2 security updates... Workaround until this is resolved...
Guest Kim Kristensen Posted March 17, 2010 Posted March 17, 2010 Hey, I have the same issue, but on a Windows Server 2003 terminal server. Unfortunatly it doesn't help replacing MSO.DLL with the older version. --- frmsrcurl: http://msgroups.net/microsoft.public.windowsupdate/Unable-to-open-docx-files-after-conducting-March-2010-Microsoft-
Guest Kim Kristensen Posted March 17, 2010 Posted March 17, 2010 Windows 2003 Hi, I have the same issue on a Windows Server 2003 terminal server. But here it doesn't help to replace the mso.dll file. atlcomputech wrote: Hey Folks,It looks like the ver 12.0.6500. 16-Mar-10 Hey Folks, It looks like the ver 12.0.6500.5000 (SP2) of the office compatability pack might also be an issue... ****We fixed the problem with the FileFormatConverter.exe ver 12.0.6015.5000**** We are running: 1) Windows 2000 sp4 2) Office 2003 sp3 When we ran microsoft update we skipped SP2 and acknowledged the first 2 security updates... Workaround until this is resolved... Previous Posts In This Thread: Submitted via EggHeadCafe - Software Developer Portal of Choice File-Based Cache for Web and non-Web Apps plus Extend ASP.NET 4.0 OutputCacheProvider http://www.eggheadcafe.com/tutorials/aspnet/56161e9e-7fa3-48e8-9dfe-9f7a28f4d58e/filebased-cache-for-web.aspx
Guest Gudufl Posted March 18, 2010 Posted March 18, 2010 Sam, That is a great find. Your solution RESOLVED the file opening issue for .docx and .xlsm files using MSO2K7 Compatibility Pack on my systems with: 1) OS W2Kpro, W2KSVR 2) Running MS Office 2000SP3 3) Security update KB977724 installed (Which has been pulled) Thanks Susan, are you still wanting a sample of an impacted file? --- frmsrcurl: http://msgroups.net/microsoft.public.windowsupdate/Unable-to-open-docx-files-after-conducting-March-2010-Microsoft-
Guest Gudufl Posted March 18, 2010 Posted March 18, 2010 Adendum: The full OS description should read: 1)OS W2Kpro SP4 amd W2KSVR SP4 with all MS-Updates. As non of the W2K OS show the KB977724 update in ARP and also do not create an Uninstall DIR in the WinDIR use the WindowsUpdate.log in that DIR or Belarc to check if it was installed. --- frmsrcurl: http://msgroups.net/microsoft.public.windowsupdate/Unable-to-open-docx-files-after-conducting-March-2010-Microsoft-
Guest Susan Bradley Posted March 19, 2010 Posted March 19, 2010 Unable to open .docx files after conducting March 2010 MicrosoftUpdate Gudufl wrote: > Sam, > That is a great find. Your solution RESOLVED the file opening issue for .docx and .xlsm files using MSO2K7 Compatibility Pack on my systems with: > 1) OS W2Kpro, W2KSVR > 2) Running MS Office 2000SP3 > 3) Security update KB977724 installed (Which has been pulled) > Thanks > > Susan, > are you still wanting a sample of an impacted file? > > --- > frmsrcurl: http://msgroups.net/microsoft.public.windowsupdate/Unable-to-open-docx-files-after-conducting-March-2010-Microsoft- Yes please!
Guest Gudufl Posted March 19, 2010 Posted March 19, 2010 Susan, sent you an email in the hope that I got your address right. Let me know if you get it. --- frmsrcurl: http://msgroups.net/microsoft.public.windowsupdate/Unable-to-open-docx-files-after-conducting-March-2010-Microsoft-
Guest Susan Bradley Posted March 19, 2010 Posted March 19, 2010 Unable to open .docx files after conducting March 2010 MicrosoftUpdate Gudufl wrote: > Susan, > sent you an email in the hope that I got your address right. > Let me know if you get it. > > --- > frmsrcurl: http://msgroups.net/microsoft.public.windowsupdate/Unable-to-open-docx-files-after-conducting-March-2010-Microsoft- Got it!
Guest jake1453 Posted March 26, 2010 Posted March 26, 2010 Unable to open .docx files after conducting March 2010 Microso On Mar 12, 3:54Â pm, 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. > > 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
Guest Gudufl Posted March 26, 2010 Posted March 26, 2010 Jake, Please read this thread carefully and you will see that MS has pulled (removed) the update on 2010-03-10. http://blogs.technet.com/wsus/archive/2010/03/11/expired-update-kb977724.aspx Un-installation of the updates is also discussed in this thread and the procedure, one can use to do so, depends on the OS (Operating System). There are varied levels of sophistication required to understanding and dealing with this issue, which proves a point that learning the basics of how a PC works (Hardware - OS - Applications Software) can never be wasted time and the sophistication one is prepared to pursue in learning about PCs is up to the individual. For the rest there are friendly and helpful threads like this one. It is foolish to expect MS to hold your hand like babies. --- frmsrcurl: http://msgroups.net/microsoft.public.windowsupdate/Unable-to-open-docx-files-after-conducting-March-2010-Microsoft-
Guest PA Bear [MS-MVP] Posted March 26, 2010 Posted March 26, 2010 Unable to open .docx files after conducting March 2010 MicrosoftUpdate 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 -- ~PA Bear, posted via Google Groups On Mar 11, 8:26Â am, Bruce wrote: > Hello -- I'm running Windows 2000, MS Office 2003 Professional, and Office Compatibility Pack. My system has been running quite stable. Â In conducting the March Microsoft Updates, it updated with the following files: > > Security Update for the 2007 Microsoft Office System (KB978380) > Update for the 2007 Microsoft Office System (KB977724) > Update for Microsoft Office Outlook 2003 Junk Email Filter (KB979771) > Security Update for Microsoft Office Excel 2003 (KB978474) > Windows Malicious Software Removal Tool - March 2010 (KB890830) > > After conducting this update, I find that when I attempt to open a .docx file, I get "There was an error opening the file." error message. Â I wentinto Add/Remove Programs in Control Panel, but was unable to find KB977724listed. Â I tried removing the Office 2007 Compatibility Pack and downloading it/installing it fresh, but to no avail.
Guest PA Bear [MS MVP] Posted March 26, 2010 Posted March 26, 2010 Unable to open .docx files after conducting March 2010 Microso 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: > 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
Recommended Posts