Compartilhar via


Announcing Service Pack 3 for Office 2007 and SharePoint 2007

Today we’re pleased to announce the 3rd (and likely final) Service Pack release for Office 2007 and SharePoint Server 2007. We are targeting a release date within Calendar Q4 2011. As we approach the date we will have more to share on exact timing.

We are offering this release in preparation for the April October 2012 end of mainstream support for the 2007 client and server products. The October 2011 release provides a 6-month window to test and deploy the release prior to exiting mainstream support. (note: the correction is due to an error in the support date that was fixed on the product support lifecycle web page. The correct date is October).

Upgrading to Office 2010 is also an option for those who are still using Office 2007. Office 2010 will remain in mainstream support until 2015, and this path provides a much better option for those looking to upgrade from Office 2003 prior to its end of life, scheduled for April 2014.

For those of you hoping to test SP3 prior to its deployment, we will continue or standard practice with Service Pack releases. Initially SP3 will be offered through the Microsoft Download Center as a manual download, through Microsoft Update as an Optional update. No earlier than 90 days after release, we will convert SP3 to an Automatic Update for our 2007 customers.

Service Pack 3 contains a roll-up of all 2007 Cumulative and Public Updates since Service Pack 2 for both Office client suites and applications as well as SharePoint Servers, in addition to some new fixes for issues discovered during the lifecycle of SP2.

For each of these products, if you are current with Automatic Updates for Office 2007, you have already installed most of the changes in the release. SP3 is much smaller than 2007 SP1, SP2 or the recently released 2010 SP1. We will provide documentation detailing the changes and the affected packages on TechNet.

The deployment experience should be straightforward. Unlike 2010 SP1, we will not be asking customers to deploy the accompanying Cumulative Update at the same time. Our deployment guidance for 2007 servers remains consistent with the guidance we have provided in the past. Office Client deployment for SP3 will also remain consistent with prior guidance.

SP3 will include changes in the following areas:

Office Client 2007 Suites
Office SharePoint 2007 Servers
Office SharePoint Search Server 2007
Office SharePoint Designer 2007
Office Project 2007
Office Visio 2007
Office Proofing tools 2007
Calendar Printing Assistant for Outlook 2007
Office InterConnect 2007
Office Compatibility Pack
PowerPoint Viewer
Visio Viewer
Office Servers Language Pack
Windows SharePoint Services 3.0
Office Access Runtime and Data Connectivity Components

Comments

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    @JairJy, we'll update on release contents in a future post. Nothing to announce at this time. @git98, you'll have to ask the Windows blog that question... @XPClient, we'll update on release contents in a future post.

  • Anonymous
    October 06, 2011
    Any improvements about OOXML and ODF?

  • Anonymous
    October 07, 2011
    I want to know when Microsoft will be releasing Windows Vista Service Pack 3.

  • Anonymous
    October 07, 2011
    The comment has been removed

  • Anonymous
    October 07, 2011
    Could you clarify what is meant by the the "October 2011" release that was mentioned in the 2nd paragraph?  Are you referring to some October 2011 cumulative update for Office 2007?

  • Anonymous
    October 10, 2011
    Office Client 2007 Suites I did not understand why it never did work I was lostAnnouncing Service Pack 3 for Office 2007 and SharePoint 2007 this should help.Thank's MUCH.  

  • Anonymous
    October 19, 2011
    In our enterprise, the post-offices were upgraded to 2010 Exchange, but everyone is still on Office 2007 32 bit Outlook, on our Windows 7 64-bit Enterprise workstations.  Some people have installed their own Office 2010 suite excluding Outlook 2010 and while also keeping Office 2007 suite installed (for Outlook?).  The understanding (is it false?) is that 32 bit 2007 outlook is less risky than 64 bit 2010 outlook, and Microsoft may never be able to get it fixed. I don't know why Microsoft can't get their software to agree.(?)

  • Anonymous
    October 19, 2011
    @git98 : Microsoft has already said before that there will be no Vista SP3. If released it would be before mainstream support ends [April 2012].

  • Anonymous
    October 21, 2011
    can ms office 2007 able to work with 2010 ms office file?

  • Anonymous
    October 22, 2011
    I'd like to see the MS Outlook, Outlook Connector fixed so that hotmail accounts will connect the way they'er supposed to connect without error.

  • Anonymous
    October 23, 2011
    Where to download it by the way? Its not provided as a single pack???

  • Anonymous
    October 25, 2011
    And that release date would be today as it just showed up on MU and WSUS.

  • Anonymous
    October 28, 2011
    I've been running Office 2010 on Win 7 since it came out. Why is Windows Update offerring the Office 2007 SP3 to me?

  • Anonymous
    November 01, 2011
    I have Office 2010.  Why is MS Update telling me that I need Office 2007 SP3?

  • Anonymous
    November 09, 2011
    After running the SP3 udates, all of my office apps are still showing SP2 in the About section.

  • Anonymous
    November 25, 2011
    After applying Microsoft Office Access Runtime and Data Connectivity 2007 Service Pack 3 (SP3), SSIS package fails.  Spent days recoding package to resolve issue and end results were no data was being loaded into dbase.  Only resolution was to uninstall update.  The following are error messages that were trapped when update was installed.   Source: ExtractMDS Connection manager "Excel Connection Manager"   Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.  Source: "Microsoft Office Access Database Engine"  Hresult: 0x80004005  Description: "Unexpected error from external database driver (????????).".   Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.

  • Anonymous
    August 27, 2014
    This is the new continued page about all recently published cumulative updates, service packs and related