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 SuitesOffice SharePoint 2007 Servers Office SharePoint Search Server 2007Office SharePoint Designer 2007Office Project 2007Office Visio 2007Office Proofing tools 2007Calendar Printing Assistant for Outlook 2007Office InterConnect 2007Office Compatibility Pack PowerPoint ViewerVisio ViewerOffice Servers Language PackWindows SharePoint Services 3.0Office Access Runtime and Data Connectivity Components
@ Bryan and @ Andrew : If the version of the Office Suite installed on your system was delivered with a component updated with SP3, the system will be offered updates for it whether the component is installed or not. The detection logic used to scan for affected systems is designed to check for updates for all components that shipped with the particular Office Suite and offer the updates to a system. Users who choose not to apply an update for a component that is not installed, but is included in their version of the Office Suite, will not increase the security risk of that system. On the other hand, users who do choose to install the update will not have a negative impact on the security or performance of a system.
@ George D. : After the full installation of the SP3 updates, the About section should indicate SP3.
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.