Consider the following scenario:

•	You have a Word 2003 document that contains mail recipient information and attachments.
•	You have installed Microsoft Office Outlook 2007 and Office Word 2007 on your computer.
•	You open the Word 2003 document in Word 2007.

In this scenario, when you click Send to Mail Recipient, you receive the following error message:

Additionally, if you click Send to Mail Recipient again, the Send to Mail Recipient view appears. However, the attachments and mail recipient information are lost.

Back to the top

This issue is fixed in the Outlook 2007 post-Service Pack 1 hotfix package that was released on January 28, 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

Source: Microsoft Support

Back to the top

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

Microsoft Outlook AutoDiscover will not Configure Outlook for the Microsoft Online Environment. It will revert back to the on-premise Microsoft Exchange 2007 Server and email will not be able to be viewed through the Microsoft Outlook client.

Back to the top

If your company is an Exchange Online customer and your e-mail environment meets the following conditions, you may encounter Autodiscover issues.

1.       Your organization is using Microsoft Exchange Server 2007.

2.       Your users are using Microsoft Outlook 2007.

3.       Your users with Exchange Online mailboxes also have mailboxes on your on-premise Exchange Server, AND your Exchange Online user accounts have identical primary SMTP e-mail address in both systems.Description

Autodiscover is a feature of Exchange 2007 that automatically connects your Outlook 2007 clients with the correct Exchange e-mail server without requiring the users to enter any Outlook configuration information.

The Autodiscover feature keys off of the user’s primary SMTP address. For example, jim@contoso.com. If there is an SMTP address conflict, if the user’s computer is joined to an on-premise Active Directory domain, the connection to the on-premise Exchange Server will receive the highest priority.

This situation is most likely to occur during the trial period or during an e-mail coexistence period before the users mailbox is fully migrated to the Exchange Online environment, and the on-premise mailbox is deleted.Recommendations

1.       Do not allow users with mailboxes on both systems. Delete the on-premise Exchange mailbox as quickly as possible after migrating mailbox content to Exchange Online.

2.       Do not use the same primary SMTP address for Microsoft Online user accounts and on-premise Exchange mailboxes during the trial period.

Back to the top

If you must have both mailboxes in use at the same time, and if you must use the same primary SMTP address for both mailboxes, use the following work-around:

1. Install Outlook 2007 SP1.

2. Install the Outlook 2007 hotfix (/Feedback.aspx?kbNumber=948716) described in KB KB948716.

3. Modify the registry on each client computer:

To modify the registry:

1.       Click Start, click Run, and then type regedit.

2.       Navigate to the following registry key:
HKEY_CURRENT_USER Software Microsoft Office 12.0 Outlook AutoDiscover

3.       Set the following values for the Value Names listed below:
PreferLocalXML=dword:1
ExcludeHttpRedirect=dword:0
ExcludeHttpsAutodiscoverDomain=dword:1
ExcludeHttpsRootDomain=dword:1
ExcludeScpLookup=dword:1
ExcludeSrvLookup=dword:1
ExcludeSrvRecord=dword:1

If you contact Microsoft Online Support (http://technet.microsoft.com/en-us/library/cc268319(TechNet.10).aspx), they can provide a .REG file to simplify this operation.How to Access Your E-Mail

After on-premise Exchange Server mailboxes have been migrated to Exchange Online, the Outlook 2007 client will always connect to Exchange Online. If your on-premise mailboxes have not been deleted, you can use Microsoft Outlook Web Access to connect to your on-premise mailbox.How to Reverse the Work Around

After deleting the on-premise Exchange Server mailbox, or if the user no longer has an Exchange Online mailbox, you should return the registry key to its original settings.

To modify the registry:

1.       Click Start, click Run, and then type regedit.

2.       Navigate to the following registry key: HKEY_CURRENT_USER Software Microsoft Office 12.0 Outlook AutoDiscover

3.       Set the following values on the Value Names listed below:
PreferLocalXML=dword:0
ExcludeHttpRedirect=dword:0
ExcludeHttpsAutodiscoverDomain=dword:0
ExcludeHttpsRootDomain=dword:0
ExcludeScpLookup=dword:0
ExcludeSrvLookup=dword:0
ExcludeSrvRecord=dword:0

If you contact Microsoft Online Support (http://technet.microsoft.com/en-us/library/cc268319(TechNet.10).aspx), they can provide a .REG file to simplify this operation.

Back to the top

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

•	The issues that the hotfix package fixes.
•	The prerequisites for installing the hotfix package.
•	Whether you must restart the computer after you install the hotfix package.
•	Whether the hotfix package is replaced by any other hotfix package.
•	Whether you must make any registry changes.
•	The files that the hotfix package contains.

Back to the top

Issues that the hotfix package fixes

List of issues that are fixed

This hotfix fixes the following issues:

•	954540 (/Feedback.aspx?kbNumber=954540/) The changes in the TOC and PageRef fields do not appear when you compare Word 2007 documents
•	954541 (/Feedback.aspx?kbNumber=954541/) The Ref field is updated incorrectly when you print a Word 2007 document

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	When you compare and merge documents that are written in Chinese characters or in Japanese characters in Word 2007, the text that is marked as deleted and inserted is much larger than the text that is actually changed. For example, if you delete only one character or one word, a large chunk of text around this character or word is marked as deleted. Additionally, the chunk of text is marked as reinserted, except for the character or for the word that is actually deleted. Note The issue occurs for both character-level comparison and word-level comparison. However, this issue does not occur if you delete the word or the character at the end of the sentence.
•	Consider the following scenario. You create and then save a new document from a template on a trusted network share. This template contains Microsoft Visual Basic for Application (VBA) code. Then, you open the document again. In this scenario, you cannot save the document again. Additionally, you receive the following error message: The save failed due to out of memory or disk space.
•	Consider the following scenario. You create and then save a document that contains a table. You delete one row, and you modify the content in the following row. Then, you save the document as a different name. In this scenario, if you compare the revised document to the original document, the result is incorrect.
•	Consider the following scenario. You create a Microsoft Office Word 2003 document, and you apply a new style such as Style1 to some paragraphs that have outline numbering enabled. Then, you change the number format of Style1. To change this number format, you add text before the number in that document. In this scenario, when you use the Compare Documents functionality to compare the revised document to the original document, the comparison document shows the formatting as the formatting in the original document. However, the comparison document should show the formatting as the formatting in the revised document.
•	You create a document that is based on a template that has customized Ribbons. When you open the document, Word 2007 may not display the Ribbon customizations. This issue can occur if the following conditions are true: • The template uses the editing restriction, Filling in forms. Note This issue does not occur if the template is unprotected or if the template uses one of the following editing restrictions: • Comments • No changes (Read only) • Tracked changes • The document is saved in one of the following file formats: • Word 2003 XML Document (*.xml) • Word XML Document (*.xml) • Word Document (*.docx) • Word Macro-Enabled Document (*.docm) Note This issue does not occur if the document is saved in a rich text format (RTF) or in a binary document file format. However, the template is still correctly loaded as a base template.
•	When you add one or more letters at the beginning or at the end of a word, a word-level comparison only marks the inserted letters as an insertion, as if the inserted characters are a separate word. The expected behavior is that the original word should be marked as deleted, and the new word should be marked as an insertion.
•	If you click to clear the White space check box in the Compare Documents dialog box, the closing paragraph mark of an insertion is ignored. The expected behavior is that the closing paragraph mark should be displayed as part of the insertion, and the closing paragraph mark should not be ignored.
•	When you insert or delete a text box in the revised document, and then you compare this document to the original document, there is a revision bar next to the border of the text box. However, there is no revision markup in the text box.
•	If two plain text content controls are grouped, you may experience the following issues when you run the Spelling and Grammar check: • The last word in the first content control is selected together with part of the first word of the second content control. This behavior occurs when the following conditions are true: • There is no space after the last word in the first content control. • The last word of the first content control is proofed in the Spelling and Grammar dialog box. This issue occurs whether the last word of the first content control is spelled correctly. • After the last word of the first content control is proofed, the Spelling and Grammar check is complete. However, misspelled words are not checked in the second content control.

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix package does not replace any other hotfix packages.

Registry information

You do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The Global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb954576-fullfile-x86-glb.exe	12.0.6320.5000	15,929,040	19-Jun-2008	14:28	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,252,608	19-Jun-2008	18:33	Not Applicable
Wordconv.msp	Not Applicable	6,301,696	19-Jun-2008	18:33	Not Applicable

Word.msp file information

File name	File version	File size	Date	Time	Platform
Msword.olb	12.0.6300.5000	768,024	06-Dec-2007	17:05	Not Applicable
Winword.exe	12.0.6320.5000	349,720	19-Jun-2008	15:00	x86
Wwlib.dll	12.0.6320.5000	17,491,480	19-Jun-2008	15:00	x86

Wordconv.msp file information

File name	File version	File size	Date	Time	Platform
Wordcnv.dll	12.0.6320.5000	4,281,368	19-Jun-2008	22:42	x86
Wordconv.exe	12.0.6300.5000	24,584	13-Dec-2007	01:08	x86

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

After you apply hotfix 955572, you may receive an error message when you open an appointment in a shared calendar:

This issue may occur if the following conditions are true:

• You are the delegate in a delegate and manager scenario.
• You enable caching of shared folders.

  For more information about how to enable caching of shared folders, click the following article number to view the article in the Microsoft Knowledge Base:

  955572  (/Feedback.aspx?kbNumber=955572/ ) You cannot cache shared mail folders in Outlook 2007

To resolve this issue, apply hotfix 957692. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

In Microsoft Office Outlook 2007, when you disable the permission controls for mailbox folders by setting the following registry data, mailbox folders are disabled as expected. However, the permission controls for public folders are also disabled unexpectedly.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To disable the permission controls for mailbox folders only, follow these steps:

1. Install the Outlook 2007 hotfix package that is dated May 06, 2008.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
   952291  (/Feedback.aspx?kbNumber=952291/ ) Description of the Outlook 2007 hotfix package (Outlook.msp): May 06, 2008
2. Set the DisableEditPermissions registry entry DWORD value to 1. To do this, follow these steps:
   1. Start Registry Editor.
      • In Windows Vista, click Start
        Collapse this imageExpand this image

        

        , type regedit in the Start Search box, and then press ENTER.

        Collapse this imageExpand this image

        

        If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

      • In Windows XP, click Start, click Run, type regedit, and then click OK.
   2. Locate and then click the following registry subkey:
      HKEY_CURRENT_USER Software Microsoft Office 12.0 Outlook Options Folders
   3. Right-click DisableEditPermissions, and then click Modify.
   4. In the Value data box, type 1, and then click OK.
   5. On the File menu, click Exit to exit Registry Editor.

To disable permission controls for public folders only, follow these steps:

1. Install the Outlook 2007 hotfix package that is dated May 06, 2008.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
   952291  (/Feedback.aspx?kbNumber=952291/ ) Description of the Outlook 2007 hotfix package (Outlook.msp): May 06, 2008
2. Set the DisableEditPermissionsPublicFolders registry entry DWORD value to 1. To do this, follow these steps:
   1. Start Registry Editor.
      • In Windows Vista, click Start
        Collapse this imageExpand this image

        

        , type regedit in the Start Search box, and then press ENTER.

        Collapse this imageExpand this image

        

        If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

      • In Windows XP, click Start, click Run, type regedit, and then click OK.
   2. Locate and then click the following registry subkey:
      HKEY_CURRENT_USER Software Microsoft Office 12.0 Outlook Options Folders
   3. On the Edit menu, point to New, and then click DWORD Value.
   4. Type DisableEditPermissionsPublicFolders, and then press ENTER:
   5. Right-click DisableEditPermissionsPublicFolders, and then click Modify.
   6. In the Value data box, type 1, and then click OK.
   7. On the File menu, click Exit to exit Registry Editor.

After you install the hotfix package from KB952291, the DisableEditPermissions registry entry DWORD value indicates different functionality than it does before you install the hotfix package.

Before you install the hotfix package from KB952291, the DisableEditPermissions registry entry DWORD value indicates the following functionality:

• When the value is set to 1, the permission controls are disabled for both mailbox folders and public folders.
• When the value is set to 0, the permission controls are enabled for both mailbox folders and public folders.

After you install the hotfix package from KB952291, the DisableEditPermissions registry entry DWORD value indicates the following functionality:

• When the value is set to 1, the permission controls are disabled for mailbox folders only. In this case, the permission controls are not disabled for public folders.
• When the value is set to 0, the permission controls are enabled for both mailbox folders and public folders.

On a Windows Vista-based client computer, you try to open a Microsoft Office document from a Web site hyperlink in a 2007 Microsoft Office application. When you do this, you may experience the following symptoms:

•	Performance is slow, or the 2007 Office application may stop responding for several minutes.
•	You are prompted for authentication even though you previously entered your credentials.
•	You lose session state. Then, you are redirected to a logon page or to an error page on the Web site.
•	The document is downloaded two times. When the files are large, the download process consumes more network bandwidth.

Note These problems do not occur when you try to open the document on a Windows XP-based computer or on a Windows Server 2003-based computer.

Back to the top

This problem occurs because, on a Windows Vista-based client computer, 2007 Office applications use the Windows WebDAV Mini-Redirector Client component to open URL-based files. This component provides read/write permissions to DAV-based Web servers that support Web authoring.

When you try to open a document from a hyperlink, 2007 Office applications may request that the Windows WebDAV Client try to author the document at the URL location. However, if the authoring attempt is not expected on certain Web servers or in certain situations, the symptoms that are mentioned in the Symptoms section may occur.

Back to the top

To resolve this problem, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

1.

Apply hotfix 954573. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base: 954573 (/Feedback.aspx?kbNumber=954573/) Description of the 2007 Office system hotfix package: June 26, 2008

2.

Enable the hotfix by configuring the UseWinINETCopy registry entry. To do this, follow these steps: a. Click Start, click Run, type regedit, and then click OK. b. Locate and then click the following registry subkey: HKEY_CURRENT_USER SOFTWARE Microsoft Office 12.0 Common Internet c. On the Edit menu, point to New, and then click DWORD Value. d. Type UseWinINETCopy, and then press ENTER. e. Right-click UseWinINETCopy, and then click Modify. f. In the Value data box, type 1, and then click OK. g. Exit Registry Editor.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

This article describes an update that is available for Microsoft Office Outlook 2007. This update improves Internet Calendar functionality, and it improves compatibility with Internet Message Access Protocol (IMAP) servers.

Back to the top

This update for Outlook 2007 adds support for the following Internet Calendar features:

•	Users can now respond to a meeting invitation that is received in iCalendar format with a proposal for a new meeting time.
•	Extended yearly recurrence patterns are now supported for appointments or meetings that recur every year or every several years.

This update also improves the compatibility between Outlook 2007 and some IMAP e-mail servers.

Back to the top

Update information

How to obtain and to install the update

This update is available from the Microsoft Download Center. To download this update and to obtain installation instructions and deployment strategies, visit the following Microsoft Web site:

Previously released security updates and hotfixes that are contained in this update

Back to the top

How to determine whether the update is installed

This update contains files that have the versions that are listed in the following table.

File name	File version	File size	Date	Time
Contab32.dll	12.0.6300.5000	136,232	13-Dec-2007	06:56
Dlgsetp.dll	12.0.6308.5000	90,656	23-Mar-2008	02:14
Emsmdb32.dll	12.0.6307.5000	1,477,224	16-Mar-2008	08:29
Exsec32.dll	12.0.6300.5000	394,752	13-Dec-2007	06:56
Mimedir.dll	12.0.6309.5000	343,568	28-Mar-2008	03:24
Mspst32.dll	12.0.6308.5000	1,107,040	23-Mar-2008	02:14
Olmapi32.dll	12.0.6309.5000	2,953,776	28-Mar-2008	03:24
Omsmain.dll	12.0.6300.5000	663,088	13-Dec-2007	08:40
Omsxp32.dll	12.0.6300.5000	195,136	13-Dec-2007	08:40
Outlmime.dll	12.0.6309.5000	601,160	28-Mar-2008	03:24
Outlook.exe	12.0.6309.5000	12,840,480	28-Mar-2008	03:25
Outlph.dll	12.0.6300.5000	180,800	13-Dec-2007	06:56
Outlrpc.dll	12.0.6302.5000	47,624	07-Feb-2008	03:57
Outlvbs.dll	12.0.6300.5000	60,448	07-Dec-2007	07:05
Pstprx32.dll	12.0.6309.5000	416,280	28-Mar-2008	03:25
Scanpst.exe	12.0.6300.5000	40,520	07-Dec-2007	07:05
Scnpst32.dll	12.0.6308.5000	265,816	23-Mar-2008	02:14
Scnpst64.dll	12.0.6308.5000	275,552	23-Mar-2008	02:14

For information about how to distribute product updates for the 2007 Microsoft Office system, visit the following Microsoft Web site:

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office. For more information about the Office System TechCenter, visit the following Microsoft Web site:

Back to the top

When you start Microsoft Office Outlook 2007 in Windows Vista, you receive the following error message:

Back to the top

This problem occurs when all following conditions are true:

•	You used the Backup Status and Configuration program to back up the mail file.
•	You recently used the Backup Status and Configuration program to restore the mail file from backup.
•	The mail file is in an encrypted folder.

Back to the top

To work around this problem, use the Inbox Repair Tool (Scanpst.exe) to repair your personal mail file. To do this, follow these steps:

1.	Exit Outlook 2007.
2.	Click Start, and then click Control Panel.
3.	Click User Accounts and Family Safety or User Accounts. Note If you do not see User Accounts and Family Safety or User Accounts, go to the next step.
4.	Click Mail.
5.	Click Data Files, click Personal Folders, and then click Settings.
6.	Note the text in the Filename box. Note If you cannot view all the text, click in the Filename box, and then press the RIGHT ARROW key repeatedly.
7.	Click OK, and then click Close two times.
8.	Click Start, type %ProgramFiles% Microsoft Office Office12 in the Start Search box, and then press ENTER.
9.	Double-click Scanpst.
10.	In the Enter the name of the file you want to scan box, type the path and file name of the Outlook .pst file that you noted in step 6.
11.	Click Start.
12.	When the Inbox Repair Tool finishes, click OK.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about errors that occur when you start Outlook, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

This article describes the Web folders issues that are fixed in the Software Update for Web Folders that is dated May 18, 2007.

•	The issues that the update fixes.
•	The prerequisites for installing the update.
•	Whether you must restart the computer after you install the update.
•	Whether the update is replaced by any other update.
•	Whether you must make any registry changes.
•	The files that the update contains.

Back to the top

List of issues fixed

This update fixes various issues that may occur when you use Web folders from the client computer to connect to a server that supports Web Distributed Authoring and Versioning (WebDAV).

This update fixes the following issues:

•	A document that is opened from a Microsoft Office SharePoint Server 2007site may be downloaded two times when you click Edit in Microsoft Office program.
•	The download progress indicator does not work for some documents on the SharePoint site.
•	You cannot rename or copy files that have a display name in a non-Internet Information Services (IIS) Web folder.

Additionally, this update includes security enhancements to Web folders.

Back to the top

Update information

The following file is available for download from the Microsoft Download Center:
Download the Software Update for Web Folders package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=17C36612-632E-4C04-9382-987622ED1D64)

Release Date: May 18, 2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Restart information

You may have to restart the computer after you apply this update.

Update replacement information

This update replaces the Software Update for Web Folders that is dated January 25, 2005.

For more information about the Software Update for Web Folders that is dated January 25, 2005, click the following article number to view the article in the Microsoft Knowledge Base:

File information

After the update is installed, the English version of this update has the file attributes, or a later version of the file attributes, that are listed in the following table:

File name	File version	File size	Date	Time
Fp4autl.dll	4.0.2.3216	589,880	17-Nov-2004	22:33
Fp4awec.dll	4.0.2.2611	450,669	17-Nov-2004	22:33
Fpext_fp4.msg	Not Applicable	78,706	17-Nov-2004	22:33
Msdaipp.dll	12.0.4518.1014	1,011,488	27-Oct-2006	00:49
Msdapml.dll	12.0.4518.1014	163,104	27-Oct-2006	00:49
Msonsext.dll	12.0.4518.1014	970,528	27-Oct-2006	00:49
Nsextint.dll	12.0.4518.1014	75,552	27-Oct-2006	00:49

Additional notes

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Consider the following scenario:

•	You are running Microsoft Office Outlook on a Windows Vista-based computer.
•	You are using a Personal Folders File (.pst file) that is stored in a folder.
•	The folder is redirected to a server.
•	The .pst file is cached locally by Client-Side Caching (CSC).

In this scenario, when the client computer synchronizes the cached .pst file with the server, you cannot access the .pst file.

Note The client computer may access the .pst file when an Outlook rule runs or when the AutoArchive feature runs. Also, the client computer accesses the .pst file when you click the messages in the .pst file.

When this issue occurs, you have to remove and then re-add the .pst file. Or, you have to close and then reopen Outlook.

Back to the top

This problem occurs because CSC prevents file handles from being opened on files while a synchronization operation is in progress between the client and the server.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb944386~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,791	20-Feb-2008	21:51	Not Applicable
Package_2_for_kb944386~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,958	20-Feb-2008	21:51	Not Applicable
Package_3_for_kb944386~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,612	20-Feb-2008	21:51	Not Applicable
Package_4_for_kb944386~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,796	20-Feb-2008	21:51	Not Applicable
Package_5_for_kb944386~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,451	20-Feb-2008	21:51	Not Applicable
Package_6_for_kb944386~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,797	20-Feb-2008	21:51	Not Applicable
Package_7_for_kb944386~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,463	20-Feb-2008	21:51	Not Applicable
Package_8_for_kb944386~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,682	20-Feb-2008	21:51	Not Applicable
Package_9_for_kb944386~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,458	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,901	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,803	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,713	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_sc~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,423	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,901	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,430	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpe_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,420	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpe~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,424	20-Feb-2008	21:51	Not Applicable
Update.mum	Not Applicable	4,133	20-Feb-2008	21:51	Not Applicable
X86_417dbdd66e7f85de71f38020fa587622_31bf3856ad364e35_6.0.6000.20775_none_62944916ab319740.manifest	Not Applicable	1,064	20-Feb-2008	21:51	Not Applicable
X86_6162eb3681785f8502e361896adf5a75_31bf3856ad364e35_6.0.6000.20775_none_a380b5e6dbf71f9c.manifest	Not Applicable	705	20-Feb-2008	21:51	Not Applicable
X86_aff88adeeb6eead201eea5f7e627e287_31bf3856ad364e35_6.0.6000.20775_none_29a43dd6a505f991.manifest	Not Applicable	693	20-Feb-2008	21:51	Not Applicable
X86_cb421b5286fbe95ef0ac5d709590b23c_31bf3856ad364e35_6.0.6001.22118_none_98310cbb25f06b0a.manifest	Not Applicable	708	20-Feb-2008	21:51	Not Applicable
X86_d09befdeef4decc35f34ffc26d73485b_31bf3856ad364e35_6.0.6000.20775_none_31296f503c2afc5c.manifest	Not Applicable	711	20-Feb-2008	21:51	Not Applicable
X86_e0b3cef376459d8d3e29a4eae68da052_31bf3856ad364e35_6.0.6001.22118_none_825cee10ba32b98d.manifest	Not Applicable	711	20-Feb-2008	21:51	Not Applicable
X86_f73485f213aa5434975160036646b6b3_31bf3856ad364e35_6.0.6001.22118_none_daec13ff671f2811.manifest	Not Applicable	705	20-Feb-2008	21:51	Not Applicable
X86_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.0.6000.20775_none_a9c7a9f415508b13.manifest	Not Applicable	4,908	19-Feb-2008	05:13	Not Applicable
X86_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.0.6001.22118_none_abf1c9001243c063.manifest	Not Applicable	4,906	20-Feb-2008	04:45	Not Applicable
X86_microsoft-windows-o..nefiles-extend-apis_31bf3856ad364e35_6.0.6000.20775_none_8b4f6d5a50770694.manifest	Not Applicable	87,260	19-Feb-2008	05:17	Not Applicable
X86_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.0.6000.20775_none_9ca4f90a78129b39.manifest	Not Applicable	14,337	19-Feb-2008	05:12	Not Applicable
X86_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.0.6001.22118_none_9ecf18167505d089.manifest	Not Applicable	16,070	20-Feb-2008	04:44	Not Applicable
X86_microsoft-windows-offlinefiles-service_31bf3856ad364e35_6.0.6000.20775_none_0830422d7d8b959d.manifest	Not Applicable	39,170	19-Feb-2008	05:16	Not Applicable
X86_microsoft-windows-offlinefiles-service_31bf3856ad364e35_6.0.6001.22118_none_0a5a61397a7ecaed.manifest	Not Applicable	39,168	20-Feb-2008	04:49	Not Applicable
X86_microsoft-windows-rdbss_31bf3856ad364e35_6.0.6000.20775_none_583187ef7d94c0b7.manifest	Not Applicable	6,856	19-Feb-2008	05:18	Not Applicable
Cscapi.dll	6.0.6000.20775	31,232	19-Feb-2008	04:47	x86
Cscdll.dll	6.0.6000.20775	22,016	19-Feb-2008	04:47	x86
Cscapi.dll	6.0.6001.22118	31,744	20-Feb-2008	04:21	x86
Cscdll.dll	6.0.6001.22118	22,016	20-Feb-2008	04:21	x86
Cscobj.dll	6.0.6000.20775	131,584	19-Feb-2008	04:47	x86
Offlinefileswmiprovider.mof	Not Applicable	42,877	13-Dec-2007	20:11	Not Applicable
Offlinefileswmiprovider_uninstall.mof	Not Applicable	42,877	13-Dec-2007	20:11	Not Applicable
Csc.sys	6.0.6000.20775	348,160	19-Feb-2008	02:17	x86
Cscmig.dll	6.0.6000.20775	105,984	19-Feb-2008	04:47	x86
Microsoft-windows-offlinefiles-core-ppdlic.xrm-ms	Not Applicable	3,021	19-Feb-2008	04:24	Not Applicable
Csc.sys	6.0.6001.22118	351,232	20-Feb-2008	01:55	x86
Cscmig.dll	6.0.6001.22118	106,496	20-Feb-2008	04:21	x86
Microsoft-windows-offlinefiles-core-ppdlic.xrm-ms	Not Applicable	3,050	20-Feb-2008	04:00	Not Applicable
Cscsvc.dll	6.0.6000.20775	489,472	19-Feb-2008	04:47	x86
Microsoft-windows-offlinefiles.mof	Not Applicable	1,931	13-Dec-2007	20:11	Not Applicable
Cscsvc.dll	6.0.6001.22118	487,936	20-Feb-2008	04:21	x86
Microsoft-windows-offlinefiles.mof	Not Applicable	1,931	18-Dec-2007	21:26	Not Applicable
Rdbss.sys	6.0.6000.20775	222,720	19-Feb-2008	02:17	x86

Windows Vista, x64-based versions

File name	File version	File size	Date	Time	Platform
Amd64_09cac7b8b42ef38b72cc9847a8eeac05_31bf3856ad364e35_6.0.6000.20775_none_53b396be48b4aea0.manifest	Not Applicable	715	20-Feb-2008	21:51	Not Applicable
Amd64_23a0e446a781a5f08026f7fb6a5d74be_31bf3856ad364e35_6.0.6000.20775_none_29c3bd153576858b.manifest	Not Applicable	709	20-Feb-2008	21:51	Not Applicable
Amd64_4abcb7d434a97fff2a3d92d177bee3a7_31bf3856ad364e35_6.0.6000.20775_none_b6264a23215b00d8.manifest	Not Applicable	1,070	20-Feb-2008	21:51	Not Applicable
Amd64_634ead215e09242c940a07dc0cabd78a_31bf3856ad364e35_6.0.6001.22118_none_7f0c2ecbbfcccee4.manifest	Not Applicable	715	20-Feb-2008	21:51	Not Applicable
Amd64_87c632bc786bbcc10a836f55771b3dcd_31bf3856ad364e35_6.0.6001.22118_none_6ae356af0c8fe1c1.manifest	Not Applicable	712	20-Feb-2008	21:51	Not Applicable
Amd64_87f03d28b47994b5ec47dcca53d4f9a8_31bf3856ad364e35_6.0.6001.22118_none_96a9251b4156884c.manifest	Not Applicable	1,070	20-Feb-2008	21:51	Not Applicable
Amd64_adb71eded3b057007bf43aa4bde56a4f_31bf3856ad364e35_6.0.6001.22118_none_04d20d10e4ae4a01.manifest	Not Applicable	709	20-Feb-2008	21:51	Not Applicable
Amd64_e740362f06d12098e910b049bea4c04d_31bf3856ad364e35_6.0.6000.20775_none_760074672dc920e6.manifest	Not Applicable	697	20-Feb-2008	21:51	Not Applicable
Amd64_f4bd7c420fe5a76bff047b911bf45cd8_31bf3856ad364e35_6.0.6000.20775_none_83ae842867c51524.manifest	Not Applicable	1,428	20-Feb-2008	21:51	Not Applicable
Amd64_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.0.6000.20775_none_05e64577cdadfc49.manifest	Not Applicable	4,924	19-Feb-2008	05:19	Not Applicable
Amd64_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.0.6001.22118_none_08106483caa13199.manifest	Not Applicable	4,922	20-Feb-2008	05:31	Not Applicable
Amd64_microsoft-windows-o..nefiles-extend-apis_31bf3856ad364e35_6.0.6000.20775_none_e76e08de08d477ca.manifest	Not Applicable	87,286	19-Feb-2008	05:22	Not Applicable
Amd64_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.0.6000.20775_none_f8c3948e30700c6f.manifest	Not Applicable	14,365	19-Feb-2008	05:20	Not Applicable
Amd64_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.0.6001.22118_none_faedb39a2d6341bf.manifest	Not Applicable	16,098	20-Feb-2008	05:30	Not Applicable
Amd64_microsoft-windows-offlinefiles-service_31bf3856ad364e35_6.0.6000.20775_none_644eddb135e906d3.manifest	Not Applicable	39,206	19-Feb-2008	05:21	Not Applicable
Amd64_microsoft-windows-offlinefiles-service_31bf3856ad364e35_6.0.6001.22118_none_6678fcbd32dc3c23.manifest	Not Applicable	39,204	20-Feb-2008	05:35	Not Applicable
Amd64_microsoft-windows-rdbss_31bf3856ad364e35_6.0.6000.20775_none_b450237335f231ed.manifest	Not Applicable	7,113	19-Feb-2008	05:23	Not Applicable
Package_1_for_kb944386~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,801	20-Feb-2008	21:51	Not Applicable
Package_2_for_kb944386~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,199	20-Feb-2008	21:51	Not Applicable
Package_3_for_kb944386~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,628	20-Feb-2008	21:51	Not Applicable
Package_4_for_kb944386~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,035	20-Feb-2008	21:51	Not Applicable
Package_5_for_kb944386~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,465	20-Feb-2008	21:51	Not Applicable
Package_6_for_kb944386~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,036	20-Feb-2008	21:51	Not Applicable
Package_7_for_kb944386~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,706	20-Feb-2008	21:51	Not Applicable
Package_8_for_kb944386~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,930	20-Feb-2008	21:51	Not Applicable
Package_9_for_kb944386~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,472	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_client_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,913	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,815	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,723	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,431	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,913	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,438	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpe_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,428	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpe~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,432	20-Feb-2008	21:51	Not Applicable
Update.mum	Not Applicable	4,165	20-Feb-2008	21:51	Not Applicable
Wow64_microsoft-windows-o..nefiles-extend-apis_31bf3856ad364e35_6.0.6000.20775_none_f1c2b3303d3539c5.manifest	Not Applicable	83,800	19-Feb-2008	05:06	Not Applicable
X86_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.0.6000.20775_none_a9c7a9f415508b13.manifest	Not Applicable	4,908	19-Feb-2008	05:13	Not Applicable
X86_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.0.6001.22118_none_abf1c9001243c063.manifest	Not Applicable	4,906	20-Feb-2008	04:45	Not Applicable
Cscapi.dll	6.0.6000.20775	38,400	19-Feb-2008	04:56	x64
Cscdll.dll	6.0.6000.20775	29,184	19-Feb-2008	04:56	x64
Cscapi.dll	6.0.6001.22118	38,912	20-Feb-2008	04:54	x64
Cscdll.dll	6.0.6001.22118	28,672	20-Feb-2008	04:54	x64
Cscobj.dll	6.0.6000.20775	216,576	19-Feb-2008	04:56	x64
Offlinefileswmiprovider.mof	Not Applicable	42,877	14-Dec-2007	21:49	Not Applicable
Offlinefileswmiprovider_uninstall.mof	Not Applicable	42,877	14-Dec-2007	21:49	Not Applicable
Csc.sys	6.0.6000.20775	456,704	19-Feb-2008	02:32	x64
Cscmig.dll	6.0.6000.20775	134,144	19-Feb-2008	04:56	x64
Microsoft-windows-offlinefiles-core-ppdlic.xrm-ms	Not Applicable	3,021	19-Feb-2008	04:35	Not Applicable
Csc.sys	6.0.6001.22118	460,800	20-Feb-2008	02:28	x64
Cscmig.dll	6.0.6001.22118	134,656	20-Feb-2008	04:54	x64
Microsoft-windows-offlinefiles-core-ppdlic.xrm-ms	Not Applicable	3,050	20-Feb-2008	04:33	Not Applicable
Cscsvc.dll	6.0.6000.20775	603,136	19-Feb-2008	04:56	x64
Microsoft-windows-offlinefiles.mof	Not Applicable	1,931	14-Dec-2007	21:48	Not Applicable
Cscsvc.dll	6.0.6001.22118	603,648	20-Feb-2008	04:54	x64
Microsoft-windows-offlinefiles.mof	Not Applicable	1,931	18-Dec-2007	21:26	Not Applicable
Rdbss.sys	6.0.6000.20775	288,768	19-Feb-2008	02:31	x64
Cscobj.dll	6.0.6000.20775	131,584	19-Feb-2008	04:47	x86
Offlinefileswmiprovider.mof	Not Applicable	42,877	13-Dec-2007	20:11	Not Applicable
Offlinefileswmiprovider_uninstall.mof	Not Applicable	42,877	13-Dec-2007	20:11	Not Applicable
Cscapi.dll	6.0.6000.20775	31,232	19-Feb-2008	04:47	x86
Cscdll.dll	6.0.6000.20775	22,016	19-Feb-2008	04:47	x86
Cscapi.dll	6.0.6001.22118	31,744	20-Feb-2008	04:21	x86
Cscdll.dll	6.0.6001.22118	22,016	20-Feb-2008	04:21	x86

Windows Vista, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Ia64_202c4ac8b899fe2dfd373e2986191472_31bf3856ad364e35_6.0.6001.22118_none_a379fc374c7665df.manifest	Not Applicable	707	20-Feb-2008	21:51	Not Applicable
Ia64_4f9fa4aabe610272b86da18ff405ba8f_31bf3856ad364e35_6.0.6001.22118_none_4492f36a793dedf9.manifest	Not Applicable	1,068	20-Feb-2008	21:51	Not Applicable
Ia64_89b5072c3a16bfea9f7b701116257264_31bf3856ad364e35_6.0.6001.22118_none_415327bc0051fe05.manifest	Not Applicable	713	20-Feb-2008	21:51	Not Applicable
Ia64_da5bf744d562890b92f7833489bacd2e_31bf3856ad364e35_6.0.6001.22118_none_02c8715c3f9742ed.manifest	Not Applicable	710	20-Feb-2008	21:51	Not Applicable
Ia64_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.0.6001.22118_none_abf36cf61241c95f.manifest	Not Applicable	4,913	20-Feb-2008	05:04	Not Applicable
Ia64_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.0.6001.22118_none_9ed0bc0c7503d985.manifest	Not Applicable	16,084	20-Feb-2008	05:03	Not Applicable
Ia64_microsoft-windows-offlinefiles-service_31bf3856ad364e35_6.0.6001.22118_none_0a5c052f7a7cd3e9.manifest	Not Applicable	39,185	20-Feb-2008	05:08	Not Applicable
Package_1_for_kb944386~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,796	20-Feb-2008	21:51	Not Applicable
Package_2_for_kb944386~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,030	20-Feb-2008	21:51	Not Applicable
Package_3_for_kb944386~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,457	20-Feb-2008	21:51	Not Applicable
Package_4_for_kb944386~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,030	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,425	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_sc~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,427	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,905	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_server~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,435	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,426	20-Feb-2008	21:51	Not Applicable
Package_for_kb944386_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,434	20-Feb-2008	21:51	Not Applicable
Update.mum	Not Applicable	2,624	20-Feb-2008	21:51	Not Applicable
X86_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.0.6001.22118_none_abf1c9001243c063.manifest	Not Applicable	4,906	20-Feb-2008	04:45	Not Applicable
Cscapi.dll	6.0.6001.22118	83,968	20-Feb-2008	04:37	IA-64
Cscdll.dll	6.0.6001.22118	66,048	20-Feb-2008	04:37	IA-64
Csc.sys	6.0.6001.22118	1,016,832	20-Feb-2008	02:06	IA-64
Cscmig.dll	6.0.6001.22118	285,184	20-Feb-2008	04:37	IA-64
Microsoft-windows-offlinefiles-core-ppdlic.xrm-ms	Not Applicable	3,050	20-Feb-2008	04:17	Not Applicable
Cscsvc.dll	6.0.6001.22118	1,226,752	20-Feb-2008	04:37	IA-64
Microsoft-windows-offlinefiles.mof	Not Applicable	1,931	18-Dec-2007	21:26	Not Applicable
Cscapi.dll	6.0.6001.22118	31,744	20-Feb-2008	04:21	x86
Cscdll.dll	6.0.6001.22118	22,016	20-Feb-2008	04:21	x86

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

This update provides the Junk E-mail Filter in Microsoft Office Outlook 2007 with a more current definition of which e-mail messages should be considered junk e-mail. This update was released in September 2008.

Back to the top

Update details

This update replaces the following previously released update:

Back to the top

Installation details

How to obtain and install the update

This update is available from the Microsoft Download Center. To download this update and to obtain installation instructions and deployment strategies, visit the following Microsoft Web site:

How to determine whether the update is installed

This update contains files that have the versions that are listed in the following table.

File name	File version	File size	Date	Time	Platform
Outlfltr.dat	12.0.6804.1075	3,686,384	13-Aug-08	6:06	Not applicable

To determine the version of the files that are installed on the computer, follow these steps, as appropriate for the operating system that you are running.

Windows Vista

1.	Click Start , and then click Search.
2.	Click Advanced Search.
3.	In the Location box, click Local Hard Drives.
4.	In the Name box, type Outlfltr.dat, and then click Search.
5.	In the list of files, right-click Outlfltr.dat, and then click Properties.
6.	On the General tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Windows XP

1.	Start Search Companion. To do this, click Start, and then click Search. Note If Windows Desktop Search starts, click Click here to use Search Companion.
2.	In the Search Results window, click All files and folders in the Search Companion pane.
3.	In the All or part of the file name box, type Outlfltr.dat, and then click Search.
4.	In the list of files, right-click Outlfltr.dat, and then click Properties.
5.	On the General tab and on the Version tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Information for administrators about .msp files

This update consists of a full-file Microsoft Windows Installer (.msp) file. The .msp file is packaged in a self-extracting, executable file. The following .msp file is distributed in this update:

Information for administrators about how to reinstall specific components

If you update your administrative installation point and if you then recache and reinstall Outlook 2007 on client computers, you can run a command-line command that includes the REINSTALL=[ list of features ] property. This property specifies whether you want to reinstall specific components of Outlook 2007 from the administrative image.

For this update, the value for REINSTALL=[ list of features ] is as follows:

Or, you can substitute the REINSTALL=ALL parameter to reinstall all Microsoft Office components on the client computer.

For more information about how to distribute product updates for the 2007 Microsoft Office system, visit the following Microsoft Web site:

For more information about the policy for how e-mail is filtered by the junk e-mail filters in Outlook or in Exchange Server, click the following article number to view the article in the Microsoft Knowledge Base:

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office. For more information about the Office System TechCenter, visit the following Microsoft Web site:

Back to the top

This update provides the Junk E-mail Filter in Microsoft Office Outlook 2007 with a more current definition of which e-mail messages should be considered junk e-mail. This update was released in August 2008.

Back to the top

Update details

This update replaces the following update:

Back to the top

Installation details

How to obtain and to install the update

This update is available from the Microsoft Download Center. To download this update and to obtain installation instructions and deployment strategies, visit the following Microsoft Web site:

How to determine whether the update is installed

This update contains files that have the versions that are listed in the following table.

File name	File version	File size	Date	Time	Platform
Outlfltr.dat	12.0000.6629.1069	3,687,920	29-Jul-2008	23:31	Not applicable

To determine the version of the files that are installed on the computer, follow these steps, as appropriate for the operating system that you are running.

Windows Vista

1.	Click Start , and then click Search.
2.	Click Advanced Search.
3.	In the Location box, click Local Hard Drives.
4.	In the Name box, type Outlfltr.dat, and then click Search.
5.	In the list of files, right-click Outlfltr.dat, and then click Properties.
6.	On the General tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Windows XP

1.	Start Search Companion. To do this, click Start, and then click Search. Note If Windows Desktop Search starts, click Click here to use Search Companion.
2.	In the Search Results window, click All files and folders in the Search Companion pane.
3.	In the All or part of the file name box, type Outlfltr.dat, and then click Search.
4.	In the list of files, right-click Outlfltr.dat, and then click Properties.
5.	On the General tab and on the Version tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Information for administrators about .msp files

This update consists of a full-file Microsoft Windows Installer (.msp) file. The .msp file is packaged in a self-extracting, executable file. The following .msp file is distributed in this update:

Information for administrators about how to reinstall specific components

If you update your administrative installation point and if you then recache and reinstall Outlook 2007 on client computers, you can run a command-line command that includes the REINSTALL=[ list of features ] property. This property specifies whether you want to reinstall specific components of Outlook 2007 from the administrative image.

For this update, the value for REINSTALL=[ list of features ] is as follows:

Or, you can substitute the REINSTALL=ALL parameter to reinstall all Microsoft Office components on the client computer.

For information about how to distribute product updates for the 2007 Microsoft Office system, visit the following Microsoft Web site:

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office. For more information about the Office System TechCenter, visit the following Microsoft Web site:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

You may experience one or more of the following symptoms after you install a package that contains the Microsoft .NET Framework 3.5 with Service Pack 1 (SP1) and the .NET Framework 2.0 with Service Pack 2 (SP2) on a Microsoft Exchange 2007 Client Access server:

• When you click Out of Office Assistant on the Tools menu in Microsoft Office Outlook 2007, you receive the following error message:
  Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later.
• Outlook 2007 crashes when you try to view a user’s free/busy information.
• When you open the Scheduling Assistant tab in a meeting request form in Outlook 2007, you cannot view free/busy information. Instead, you see hash marks in the free/busy grid.
• When you run the Test-OutlookWebServices cmdlet in the Exchange Management Shell on the Client Access server, you receive the following error message:
  Object reference not set to an instance of an object.

Note Currently, there is no separate package for the .NET Framework 2.0 with SP2. The .NET Framework 2.0 with SP2 is included in the .NET Framework 3.5 SP1 package.

This issue is caused by a problem in the package. This problem only occurs when the package that contains the .NET Framework 3.5 with SP1 and the .NET Framework 2.0 with SP2 is installed on an Exchange Client Access server.

To resolve this problem, install the hotfix that is described in the following Microsoft Knowledge Base article on the Exchange Client Access server:

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this issue, follow these steps:

• Use Outlook Web Access to configure Out of Office (OOF) messages.
• If you have public folders in the Exchange 2007 environment, force Outlook to use public folder free/busy information instead of the Availability Service. To do this, follow these steps to add registry data to the Outlook 2007 clients:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
     HKEY_CURRENT_USER Software Microsoft Office 12.0 Outlook Options Calendar
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type UseLegacyFB, and then press ENTER.
  5. Right-click UseLegacyFB, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.

You update some page values in a Microsoft Office Word 2007 document. When you compare the revised document to the original document, the changes in the TOC and PageRef fields do not appear.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To resolve this issue, follow these steps:

1.

Install hotfix 954576.For more information, click the following article number to view the article in the Microsoft Knowledge Base: 954576 (/Feedback.aspx?kbNumber=954576/) Description of the Word 2007 hotfix package: June 20, 2008

2.

Set the CompDiffSupressPageRefOnlyInHdr registry entry. To do this, follow these steps: a. Click Start, click Run, type regedit, and then click OK. b. Locate and then click the following registry subkey: HKEY_CURRENT_USER Software Microsoft Office 12.0 Word Options c. On the Edit menu, point to New, and then click DWORD Value. d. Type CompDiffSupressPageRefOnlyInHdr, and then press ENTER. e. Right-click CompDiffSupressPageRefOnlyInHdr, and then click Modify. f. In the Value data box, type 1, and then click OK. g. Exit Registry Editor.

In a Microsoft Exchange Server 2007 environment, you grant a user the Full Access permission and the Send As permission on a shared mailbox or Exchange Management Shell. Then, the user logs on to Outlook and performs a Send As operation. If the logging level is set to Medium or Higher, the following event is logged in the Application log on the mailbox server:

Event Type: Information
Event Source: MSExchangeIS Mailbox Store
Event Category: Send As
Event ID: 1032
Description:
/o=<Organization name>/ou=<Administrative Group name>/cn=Recipients/cn=userA sent a message as /o=<Organization name>/ou=<Administrative Group name>/cn=Recipients/cn=share.

However, if the user performs the same operation by using Outlook Web Access (OWA), no event is logged for the Send As operation.

This problem occurs when users send e-mail from a shared mailbox using Outlook Web Access (OWA).

Notes

1. To perform a Send Asoperation in Office Outlook Web Access (OWA), log on as a user who has the appropriate permissions, and then click the name in the right top of the screen to open the Open Other Mailbox dialog box. Then,select the shared mailbox.
2. To set the logging level of MSExchangeIS 9000 Private Send As to Medium or Higher, you must use the Set-EventLogLevel cmdlet in Exchange Management Shell.

Download and install Update Rollup 5 for Exchange 2007 Service Pack 1.

For more information about Update Rollup 5 for Exchange 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the Set-EventLogLevel cmdlet, visit the following Web site:

For more information about how to grant the Send As permission for a mailbox, visit the following Web site:

For more information about how to enable explicit logons in Outlook Web Access, visit the following Web site:

This update provides the Junk E-mail Filter in Microsoft Office Outlook 2007 with a more current definition of which e-mail messages should be considered junk e-mail. This update was released in November 2008.

Update details

This update replaces the following previously released update:

Installation details

How to obtain and install the update

This update is available from the Microsoft Download Center. To download this update and to obtain installation instructions and deployment strategies, visit the following Microsoft Web site:

How to determine whether the update is installed

This update contains files that have the versions that are listed in the following table.

To determine the version of the files that are installed on the computer, follow these steps, as appropriate for the operating system that you are running.

Windows Vista

1. Click Start
   Collapse this imageExpand this image

   

   , and then click Search.

2. Click Advanced Search.
3. In the Location box, click Local Hard Drives.
4. In the Name box, type Outlfltr.dat, and then click Search.
5. In the list of files, right-click Outlfltr.dat, and then click Properties.
6. On the General tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Windows XP

1. Start Search Companion. To do this, click Start, and then click Search.

   Note If Windows Desktop Search starts, click Click here to use Search Companion.

2. In the Search Results window, click All files and folders in the Search Companion pane.
3. In the All or part of the file name box, type Outlfltr.dat, and then click Search.
4. In the list of files, right-click Outlfltr.dat, and then click Properties.
5. On the General tab and on the Version tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Information for administrators about .msp files

This update consists of a full-file Microsoft Windows Installer (.msp) file. The .msp file is packaged in a self-extracting, executable file. The following .msp file is distributed in this update:

Information for administrators about how to reinstall specific components

If you update your administrative installation point and if you then recache and reinstall Outlook 2007 on client computers, you can run a command-line command that includes the REINSTALL=[ list of features ] property. This property specifies whether you want to reinstall specific components of Outlook 2007 from the administrative image.

For this update, the value for REINSTALL=[ list of features ] is as follows:

Or, you can substitute the REINSTALL=ALL parameter to reinstall all Microsoft Office components on the client computer.

For information about how to distribute product updates for the 2007 Microsoft Office system, visit the following Microsoft Web site:

For more information about the policy for how e-mail is filtered by the junk e-mail filters in Outlook or in Exchange Server, click the following article number to view the article in the Microsoft Knowledge Base:

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office. For more information about the Office System TechCenter, visit the following Microsoft Web site:

Microsoft has released security bulletin MS08-069. To view the complete security bulletin, visit one of the following Microsoft Web sites:

• Home users:
  http://www.microsoft.com/protect/computer/updates/bulletins/200811.mspx (http://www.microsoft.com/protect/computer/updates/bulletins/200811.mspx)

  Skip the details: Download the updates for your home computer or laptop from the Microsoft Update Web site now:

  http://update.microsoft.com/microsoftupdate/ (http://update.microsoft.com/microsoftupdate/)
• IT professionals:
  http://www.microsoft.com/technet/security/bulletin/ms08-069.mspx (http://www.microsoft.com/technet/security/bulletin/ms08-069.mspx)

How to obtain help and support for this security update

For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for support issues with security updates, visit the Microsoft International Support Web site:

North American customers can also obtain instant access to unlimited no-charge e-mail support or to unlimited individual chat support by visiting the following Microsoft Web site:

For enterprise customers, support for security updates is available through your usual support contacts.

Additional information about this security update

Security update replacement information

This security update replaces the following security update:

File Information

The global version of this security update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

32-bit editions

64-bit editions

A Name Service Provider Interface (NSPI) connection from Microsoft Outlook to a Windows Server 2008-based domain controller may fail with the following error code that is returned from the server:

In some instances, a credential dialog box may appear in the Outlook user interface when you encounter this issue.

Back to the top

This behavior occurs because Windows Server 2008 only allows for a default maximum of 50 concurrent NSPI connections per user to any domain controller. Additional NSPI connections are rejected with a MAPI_E_LOGON_FAILED error code.

Note Windows Server 2003 and earlier versions of Microsoft Windows operating systems do not exhibit this behavior. The change of behavior in Windows Server 2008 is intended to protect domain controllers against clients that open too many NSPI connections without then closing the connections. Too many connections such as these can result in resource depletion.

Back to the top

To resolve this issue, check all NSPI connections that processes on the client create for connection leaks. For example, a call to the NspiBind function must have a corresponding call to the NspiUnbind function when an NSPI connection is no longer required. This operation may require that you debug any custom scripts or applications that are using NSPI. If this issue affects external applications, contact the software vendors for updates.

Note The Outlook NSPI MAPI provider that is installed with Microsoft Outlook is only intended for use with Microsoft Outlook. External scripts and applications that rely on the Outlook NSPI MAPI provider are not supported.

How to modify the registry to allow for additional NSPI connections

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

If more concurrent NSPI connections per user are legitimately required, you can change the default limit. To do this, follow these steps:

1.	Click Start, click Run, type regedit, and then click OK.
2.	Locate and then click the following registry key: HKEY_LOCAL_MACHINE System CurrentControlSet Services NTDS
3.	On the Edit menu, point to New, and then click Key.
4.	Type Parameters, and then press ENTER.
5.	Click the Parameters key.
6.	On the Edit menu, point to New, and then click DWORD Value.
7.	Type NSPI max sessions per user, and then press ENTER.
8.	Double-click NSPI max sessions per user, type the maximum number of the NSPI connections that you want to have, and then click OK.
9.	Exit Registry Editor.

Back to the top

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To confirm that you encountered the issue that is described in the Symptoms section, follow these steps:

1.

Enable event logging for NSPI connections. To do this, follow these steps: a. On the domain controller that is targeted for the NspiBind connection, click Start, click Run, type regedit, and then click OK. b. Locate and then double-click the following registry entry: HKEY_LOCAL_MACHINE System CurrentControlSet Services NTDS Diagnostics 4 MAPI Interface Events c. In the Value data box, type 5, and then click OK. Note The default value of this registry entry is 0. d. On the File menu, click Exit. Note This is a verbose level of event logging and may generate many events. This verbose level of event logging includes events that are unrelated to the diagnosis of this issue. We recommend that you restore this setting to the default value after you finish troubleshooting.

2.

After you enable event logging, an event that resembles the following is logged in the Directory Services event log when this issue occurs: Event ID: 2820NSPI max connection limit for the user has reached.You need to do NSPI unbind on old connections before making new connections.Additional DataMax NSPI connections per user: %1User: %2

A network capture of the failure may contain packets that resemble the following:

Source	Destination	Protocol	Information
ClientIP	ServerIP	NSPI	NspiBind request
ServerIP	ClientIP	NSPI	NspiBind response, Status: MAPI_E_LOGON_FAILED

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

This article describes an update that is available for Microsoft Office Outlook 2007. This update improves Internet Calendar functionality, and it improves compatibility with Internet Message Access Protocol (IMAP) servers.

Back to the top

This update for Outlook 2007 adds support for the following Internet Calendar features:

•	Users can now respond to a meeting invitation that is received in iCalendar format with a proposal for a new meeting time.
•	Extended yearly recurrence patterns are now supported for appointments or meetings that recur every year or every several years.

This update also improves the compatibility between Outlook 2007 and some IMAP e-mail servers.

Back to the top

Update information

How to obtain and to install the update

This update is available from the Microsoft Download Center. To download this update and to obtain installation instructions and deployment strategies, visit the following Microsoft Web site:

Previously released security updates and hotfixes that are contained in this update

Back to the top

How to determine whether the update is installed

This update contains files that have the versions that are listed in the following table.

File name	File version	File size	Date	Time
Contab32.dll	12.0.6300.5000	136,232	13-Dec-2007	06:56
Dlgsetp.dll	12.0.6308.5000	90,656	23-Mar-2008	02:14
Emsmdb32.dll	12.0.6307.5000	1,477,224	16-Mar-2008	08:29
Exsec32.dll	12.0.6300.5000	394,752	13-Dec-2007	06:56
Mimedir.dll	12.0.6309.5000	343,568	28-Mar-2008	03:24
Mspst32.dll	12.0.6308.5000	1,107,040	23-Mar-2008	02:14
Olmapi32.dll	12.0.6309.5000	2,953,776	28-Mar-2008	03:24
Omsmain.dll	12.0.6300.5000	663,088	13-Dec-2007	08:40
Omsxp32.dll	12.0.6300.5000	195,136	13-Dec-2007	08:40
Outlmime.dll	12.0.6309.5000	601,160	28-Mar-2008	03:24
Outlook.exe	12.0.6309.5000	12,840,480	28-Mar-2008	03:25
Outlph.dll	12.0.6300.5000	180,800	13-Dec-2007	06:56
Outlrpc.dll	12.0.6302.5000	47,624	07-Feb-2008	03:57
Outlvbs.dll	12.0.6300.5000	60,448	07-Dec-2007	07:05
Pstprx32.dll	12.0.6309.5000	416,280	28-Mar-2008	03:25
Scanpst.exe	12.0.6300.5000	40,520	07-Dec-2007	07:05
Scnpst32.dll	12.0.6308.5000	265,816	23-Mar-2008	02:14
Scnpst64.dll	12.0.6308.5000	275,552	23-Mar-2008	02:14

For information about how to distribute product updates for the 2007 Microsoft Office system, visit the following Microsoft Web site:

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office. For more information about the Office System TechCenter, visit the following Microsoft Web site:

Back to the top

Currently, the 2007 Microsoft Office system supports only forms-based authentication (FBA) through persistent cookies, such as the authentication cookies that are written to disk. Office does not support the acquisition of session cookies from a process in Internet Explorer 7.

However, in Windows Server 2008 Service Pack 2 (SP2) and in Windows Vista Service Pack 2 (SP2), the 2007 Microsoft Office system supports authenticating against FBA sites. Specifically, when you receive a particular response from the Web site, the 2007 Microsoft Office system now creates a Trident window that you can use to sign in to the Web site. The 2007 Microsoft Office system obtains cookies from that session, and you can access the content in the Web site.

To resolve this issue, obtain Windows Server 2008 SP2 or Windows Vista SP2 Release Candidate (RC). To obtain these programs, visit the following Microsoft Web site:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about FBA, visit the following Microsoft Web site:

Back to the top

List of issues that this hotfix package fixes

This hotfix package fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	You install 2007 Microsoft Office servers Service Pack 1 (SP1) on a computer that is running the release version of Microsoft Office SharePoint Server 2007. However, all DCOM permissions for the WSS_ADMIN_WPG security group and for the WSS_WPG security group are removed from the OSearch DCOM application. Additionally, if the Office SharePoint Server service is running under an account that is not in the Administrators group, the search function will not work. Note To work around this issue, manually add DCOM permissions for the WSS_ADMIN_WPG security group and for the WSS_WPG security group. To do this, follow these steps: 1. Click Start, click Run, type dcomcnfg, and then press ENTER. 2. Expand Component Services, expand Computers, expand My Computer, and then click DCOM Config. 3. In the details pane, right-click OSearch, and then click Properties. 4. Click the Security tab. 5. Under Launch and Activation Permissions, click Customize, and then click Edit. 6. Click Add to add the local WSS_ADMIN_WPG security group and the local WSS_WPG security group, grant them Local Launch and Local Activation permissions, and then click OK. 7. Under Access Permissions, click Customize, and then click Edit. 8. Click Add to add the local WSS_ADMIN_WPG security group and the local WSS_WPG security group, grant them Local Access Activation permission, and then click OK two times. 9. Restart the computer.
•	After you perform a crawl on a computer that is running Microsoft Office SharePoint Server 2007, you may receive an error message that resembles the following in the crawl log: Filtering of this file ended because the file reached the maximum filter output limit. Check that the filter does not generate a large amount of data relative to the size of the document. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 (/Feedback.aspx?kbNumber=322756/) How to back up and restore the registry in Windows Note To work around this issue, follow these steps: 1. Click Start, click Run, type regedit, and then press ENTER. 2. Locate the following registry subkey: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Office Server 12.0 Search Global Gathering Manager MaxGrowFactor 3. Double-click MaxGrowFactor, type 4096, click to select Decimal, and then click OK. 4. Exit Registry Editor.
•	You perform an incremental crawl on a computer that is running Microsoft Office SharePoint Server 2007. However, any documents in a meeting workplace template document library are not crawled. Note To work around this issue, perform a full crawl.
•	Consider the following scenario: • You create a Calendar list on a computer that is running Microsoft Office SharePoint Server 2007. • You use Microsoft Office SharePoint Designer 2007 to use a Display item form to display items in the Calendar list in a custom .aspx page. • You create a series of repeating calendar items. When you try to edit one of the repeating calendar items on the custom .aspx page, the first calendar item in the series opens instead of the calendar item that you selected. Note To work around this issue, edit the calendar item in the All Events view of the Calendar list.

Back to the top

Known issue of the hotfix package

•

Symptoms Consider the following scenario. You add a custom list as a Web Part on the home page of a SharePoint site. When you try to edit the current view of the custom list by clicking Edit the current view, the Create View page opens. However, you expect the Edit View page for this custom list to open. Workaround To work around this issue, edit the list view before you add the custom list as a Web Part on the home page of the SharePoint site. To do this, follow these steps: 1. Remove the Web Part that contains the custom list from the home page. 2. Open the custom list, click Modify this View. 3. On the Edit View page, make any changes that you want, and then click OK. 4. Add the custom list back as a Web Part on the home page.

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix package.

Restart information

You do not have to restart the computer after you apply this hotfix package.

Hotfix replacement information

This hotfix package is not replaced by any later hotfix package.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to correct the issues that are listed in this article.

32-bit hotfix package

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Download information

File name	File version	File size	Date	Time	Platform
Wss-kb953137-fullfile-x86-glb.exe	12.0.6300.5000	23,351,296	21-May-2008	16:31	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Sts.msp	Not Applicable	23,581,184	21-May-2008	22:18	Not Applicable

After the hotfix package is installed, the global version of this hotfix package has the file attributes, or a later version of the file attributes, that are listed in the following table:

File name	File version	Flie size	Date	Time	Platform
Atl80.dll	8.0.50727.762	96,256	6-Dec-2007	09:22	Not applicable
Atl80.dll	8.0.50727.762	114,688	6-Dec-2007	09:22	Not applicable
Dbghelp.dll	6.6.7.5	1,030,144	20-Feb-2007	20:14	x86
Dwdcw20.dll	12.0.6300.5000	441,864	6-Dec-2007	17:41	x86
Mfc80.dll	8.0.50727.762	1,101,824	6-Dec-2007	09:22	Not applicable
Mfc80chs.dll	8.0.50727.762	40,960	6-Dec-2007	09:22	Not applicable
Mfc80cht.dll	8.0.50727.762	45,056	6-Dec-2007	09:22	Not applicable
Mfc80deu.dll	8.0.50727.762	65,536	6-Dec-2007	09:22	Not applicable
Mfc80enu.dll	8.0.50727.762	57,344	6-Dec-2007	09:22	Not applicable
Mfc80esp.dll	8.0.50727.762	61,440	6-Dec-2007	09:22	Not applicable
Mfc80fra.dll	8.0.50727.762	61,440	6-Dec-2007	09:22	Not applicable
Mfc80ita.dll	8.0.50727.762	61,440	6-Dec-2007	09:22	Not applicable
Mfc80jpn.dll	8.0.50727.762	49,152	6-Dec-2007	09:22	Not applicable
Mfc80kor.dll	8.0.50727.762	49,152	6-Dec-2007	09:22	Not applicable
Mfc80u.dll	8.0.50727.762	1,093,120	6-Dec-2007	09:22	Not applicable
Mfcm80.dll	8.0.50727.762	69,632	6-Dec-2007	09:22	Not applicable
Mfcm80u.dll	8.0.50727.762	57,856	6-Dec-2007	09:22	Not applicable
Microsoft.sharepoint.administrationoperation.dll	12.0.6313.5000	472,104	23-Apr-2008	14:26	Not applicable
Microsoft.sharepoint.applicationpages.administration.dll	12.0.6300.5000	271,400	13-Dec-2007	20:55	x86
Microsoft.sharepoint.applicationpages.dll	12.0.6315.5000	627,784	8-May-2008	12:24	x86
Microsoft.sharepoint.dll	12.0.6316.5000	9,339,944	15-May-2008	15:39	Not applicable
Microsoft.sharepoint.dll	12.0.6316.5000	9,339,944	15-May-2008	15:39	x86
Microsoft.sharepoint.intl.dll	12.0.6300.5000	463,912	13-Dec-2007	20:55	x86
Microsoft.sharepoint.library.dll	12.0.6300.5000	132,136	13-Dec-2007	20:55	Not applicable
Microsoft.sharepoint.search.dll	12.0.6315.5000	1,433,648	6-May-2008	15:51	Not applicable
Microsoft.sharepoint.search.intl.dll	12.0.6309.5000	193,632	25-Mar-2008	14:07	Not applicable
Microsoft.sharepoint.setupconfiguration.intl.dll	12.0.6300.5000	2,081,832	13-Dec-2007	20:55	x86
Microsoft.sharepoint.workflowactions.dll	12.0.6300.5000	197,704	13-Dec-2007	20:55	x86
Msscntrs.dll	12.0.6300.5000	91,656	13-Dec-2007	20:56	Not applicable
Mssdmn.exe	12.0.6309.5000	282,144	25-Mar-2008	14:07	Not applicable
Mssearch.exe	12.0.6309.5000	159,304	25-Mar-2008	14:07	Not applicable
Mssph.dll	12.0.6316.5000	695,808	20-May-2008	15:57	Not applicable
Mssrch.dll	12.0.6309.5000	2,059,776	25-Mar-2008	14:07	Not applicable
Msvcm80.dll	8.0.50727.762	479,232	6-Dec-2007	09:22	Not applicable
Msvcp80.dll	8.0.50727.762	548,864	6-Dec-2007	09:22	Not applicable
Msvcr80.dll	8.0.50727.762	626,688	6-Dec-2007	09:22	Not applicable
Nlhtml.dll	2006.1206.6300.5000	126,488	12-Dec-2007	17:26	Not applicable
Offfilt.dll	2006.1206.6300.5000	202,784	12-Dec-2007	17:26	Not applicable
Offparser.dll	12.0.6314.5000	1,078,856	29-Apr-2008	14:05	x86
Oisimg.dll	12.0.6300.5000	26,152	13-Dec-2007	20:55	x86
Onetnative.dll	12.0.6300.5000	356,920	6-Dec-2007	13:43	x86
Onetutil.dll	12.0.6316.5000	1,983,528	20-May-2008	16:19	x86
Owssvr.dll	12.0.6316.5000	3,014,696	15-May-2008	15:39	Not applicable
Owstimer.exe	12.0.6315.5000	57,888	8-May-2008	12:24	Not applicable
Prescan.exe	12.0.6300.5000	103,424	13-Dec-2007	20:55	x86
Psconfig.exe	12.0.6300.5000	578,664	13-Dec-2007	20:55	x86
Psconfigui.exe	12.0.6300.5000	824,424	13-Dec-2007	20:55	x86
Query.dll	12.0.6300.5000	84,480	13-Dec-2007	20:56	Not applicable
Setup.exe	12.0.6309.5000	442,408	27-Mar-2008	12:21	x86
Sigconfigdb.dll	Not Applicable	11,280	13-Mar-2008	09:16	x86
Sigsearchdb.dll	Not Applicable	11,280	6-May-2008	15:51	Not applicable
Sigstore.dll	Not Applicable	11,272	8-May-2008	12:24	x86
Spwriter.exe	12.0.6300.5000	37,928	13-Dec-2007	20:55	Not applicable
Stsadm.exe	12.0.6300.5000	525,392	13-Dec-2007	20:55	x86
Stsmmc.dll	12.0.6300.5000	99,896	13-Dec-2007	20:55	x86
Stssoap.dll	12.0.6316.5000	312,360	15-May-2008	15:39	x86
Stswel.dll	12.0.6316.5000	1,930,792	15-May-2008	15:39	x86
Tquery.dll	12.0.6315.5000	2,336,768	6-May-2008	15:51	Not applicable
Wrapinst.exe	12.0.6300.5000	54,312	13-Dec-2007	20:55	x86
Wsssetup.dll	12.0.6309.5000	6,786,584	27-Mar-2008	12:21	x86
Wsstracing.exe	12.0.6300.5000	48,680	13-Dec-2007	20:55	x86
Xmlfilter.dll	2006.1206.6300.5000	105,496	12-Dec-2007	17:26	Not applicable

64-bit hotfix package

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Download information

File name	File version	File size	Date	Time	Platform
Wss-kb953137-fullfile-x64-glb.exe	12.0.6300.5000	26,564,392	21-May-2008	16:31	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Sts.msp	Not Applicable	26,820,608	21-May-2008	22:18	Not Applicable

After the hotfix package is installed, the global version of this hotfix package has the file attributes, or a later version of the file attributes, that are listed in the following table:

File name	File version	Flie size	Date	Time	Platform
Atl80.dll	8.0.50727.762	113,152	6-Dec-2007	09:22	Not applicable
Dbghelp.dll	6.6.7.5	1,319,936	20-Feb-2007	20:14	x64
Dwdcw20.dll	12.0.6300.5000	1,092,616	6-Dec-2007	13:48	x64
Mfc80.dll	8.0.50727.762	1,656,320	6-Dec-2007	09:22	Not applicable
Mfc80chs.dll	8.0.50727.762	33,280	6-Dec-2007	09:22	Not applicable
Mfc80cht.dll	8.0.50727.762	33,792	6-Dec-2007	09:22	Not applicable
Mfc80deu.dll	8.0.50727.762	54,272	6-Dec-2007	09:22	Not applicable
Mfc80enu.dll	8.0.50727.762	47,104	6-Dec-2007	09:22	Not applicable
Mfc80esp.dll	8.0.50727.762	51,712	6-Dec-2007	09:22	Not applicable
Mfc80fra.dll	8.0.50727.762	52,736	6-Dec-2007	09:22	Not applicable
Mfc80ita.dll	8.0.50727.762	52,224	6-Dec-2007	09:22	Not applicable
Mfc80jpn.dll	8.0.50727.762	38,912	6-Dec-2007	09:22	Not applicable
Mfc80kor.dll	8.0.50727.762	38,400	6-Dec-2007	09:22	Not applicable
Mfc80u.dll	8.0.50727.762	1,652,736	6-Dec-2007	09:22	Not applicable
Mfcm80.dll	8.0.50727.762	65,536	6-Dec-2007	09:22	Not applicable
Mfcm80u.dll	8.0.50727.762	64,000	6-Dec-2007	09:22	Not applicable
Microsoft.sharepoint.administrationoperation.dll	12.0.6313.5000	472,104	23-Apr-2008	14:18	Not applicable
Microsoft.sharepoint.applicationpages.administration.dll	12.0.6300.5000	271,400	13-Dec-2007	20:30	x86
Microsoft.sharepoint.applicationpages.dll	12.0.6315.5000	627,784	8-May-2008	12:10	x86
Microsoft.sharepoint.dll	12.0.6316.5000	9,339,944	15-May-2008	15:19	Not applicable
Microsoft.sharepoint.dll	12.0.6316.5000	9,339,944	15-May-2008	15:19	x86
Microsoft.sharepoint.intl.dll	12.0.6300.5000	463,912	13-Dec-2007	20:30	x86
Microsoft.sharepoint.library.dll	12.0.6300.5000	132,136	13-Dec-2007	20:30	Not applicable
Microsoft.sharepoint.search.dll	12.0.6315.5000	1,534,512	6-May-2008	15:57	Not applicable
Microsoft.sharepoint.search.intl.dll	12.0.6309.5000	193,632	25-Mar-2008	13:59	Not applicable
Microsoft.sharepoint.setupconfiguration.intl.dll	12.0.6300.5000	2,081,832	13-Dec-2007	20:30	x86
Microsoft.sharepoint.workflowactions.dll	12.0.6300.5000	197,704	13-Dec-2007	20:30	x86
Msscntrs.dll	12.0.6300.5000	438,280	13-Dec-2007	20:48	Not applicable
Mssdmn.exe	12.0.6309.5000	797,216	25-Mar-2008	13:59	Not applicable
Mssearch.exe	12.0.6309.5000	574,024	25-Mar-2008	13:59	Not applicable
Mssph.dll	12.0.6316.5000	1,938,944	15-May-2008	15:52	Not applicable
Mssrch.dll	12.0.6309.5000	4,743,680	25-Mar-2008	13:59	Not applicable
Msvcm80.dll	8.0.50727.762	516,096	6-Dec-2007	09:22	Not applicable
Msvcp80.dll	8.0.50727.762	1,061,376	6-Dec-2007	09:22	Not applicable
Msvcr80.dll	8.0.50727.762	796,672	6-Dec-2007	09:22	Not applicable
Nlhtml.dll	2006.1206.6300.5000	231,448	6-Dec-2007	10:35	Not applicable
Offfilt.dll	2006.1206.6300.5000	392,224	6-Dec-2007	10:35	Not applicable
Offparser.dll	12.0.6314.5000	1,670,728	29-Apr-2008	13:49	x64
Oisimg.dll	12.0.6300.5000	37,928	13-Dec-2007	20:30	x64
Onetnative.dll	12.0.6300.5000	954,936	6-Dec-2007	13:41	x64
Onetutil.dll	12.0.6316.5000	3,388,456	15-May-2008	14:42	x64
Owssvr.dll	12.0.6316.5000	5,138,984	15-May-2008	15:19	Not applicable
Owstimer.exe	12.0.6315.5000	92,704	8-May-2008	12:10	Not applicable
Prescan.exe	12.0.6300.5000	103,424	13-Dec-2007	20:30	x86
Psconfig.exe	12.0.6300.5000	578,664	13-Dec-2007	20:30	x86
Psconfigui.exe	12.0.6300.5000	824,424	13-Dec-2007	20:30	x86
Query.dll	12.0.6300.5000	223,232	13-Dec-2007	20:48	Not applicable
Setup.exe	12.0.6309.5000	442,408	27-Mar-2008	12:21	x86
Sigconfigdb.dll	Not Applicable	11,280	13-Mar-2008	09:16	x86
Sigsearchdb.dll	Not Applicable	11,280	6-May-2008	15:51	Not applicable
Sigstore.dll	Not Applicable	11,272	8-May-2008	12:24	x86
Spwriter.exe	12.0.6300.5000	59,432	13-Dec-2007	20:30	Not applicable
Stsadm.exe	12.0.6300.5000	525,392	13-Dec-2007	20:30	x86
Stsmmc.dll	12.0.6300.5000	163,896	13-Dec-2007	20:30	x64
Stssoap.dll	12.0.6316.5000	312,360	15-May-2008	15:19	x86
Stswel.dll	12.0.6316.5000	3,317,288	15-May-2008	15:19	x64
Tquery.dll	12.0.6315.5000	4,746,752	6-May-2008	15:57	Not applicable
Wrapinst.exe	12.0.6300.5000	54,312	13-Dec-2007	20:30	x86
Wsssetup.dll	12.0.6309.5000	6,786,584	27-Mar-2008	12:21	x86
Wsstracing.exe	12.0.6300.5000	87,592	13-Dec-2007	20:30	x64
Xmlfilter.dll	2006.1206.6300.5000	207,384	6-Dec-2007	10:35	Not applicable

Back to the top

Back to the top

List of issues that the hotfix package fixes

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	You paste a range of cells from Excel into a text box in Word 2007 and then click Keep Source Formatting and Link to Excel. You right-click in a cell of the pasted table, point to Linked Worksheet Object, and then click Links. You click Preserve formatting after update and then click Manual update. When you right-click in a cell of the pasted table, click Update Link, and then click the Undo button, duplicate tables may appear in the text box.
•	You set the default font and style in Outlook 2007. To do this, you click All caps or Bold in the Font style list. After you restart Outlook 2007, the default font and style settings are lost.
•	You add the Header Position from Top command, the Footer Position from Bottom command, or both to the Quick Access Toolbar (QAT) in Word 2007. When you add a table to a new document, and you type text in a cell of the table, the whole table row flashes between white and the text highlight color. Note You can see the typed text clearly when you click other cells.

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Download information

File name	File version	File size	Date	Time	Platform
Office-kb953924-fullfile-x86-glb.exe	12.0.6300.5000	15,860,320	05-Jun-2008	09:25	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,234,176	05-Jun-2008	14:01	Not Applicable
Wordconv.msp	Not Applicable	6,219,776	05-Jun-2008	14:01	Not Applicable

Contents of Word.msp

File name	File version	File size	Date	Time	Platform
Msword.olb	12.0.6300.5000	768,024	07-Dec-2007	01:05	x86
Winword.exe	12.0.6318.5000	349,720	05-Jun-2008	17:04	x86
Wwlib.dll	12.0.6318.5000	17,494,552	05-Jun-2008	17:04	x86

Contents of Wordconv.msp

File name	File version	File size	Date	Time	Platform
Wordcnv.dll	12.0.6318.5000	4,280,856	05-Jun-2008	17:02	x86
Wordconv.exe	12.0.6300.5000	24,584	13-Dec-2007	01:08	x86

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

This article describes the Microsoft Office Project 2007 issue that is fixed in the hotfix package that is dated May 8, 2008.

•	The issues that the hotfix package fixes.
•	The prerequisites for installing the hotfix package.
•	Whether you must restart the computer after you install the hotfix package.
•	Whether the hotfix package is replaced by any other hotfix packages.
•	Whether you must make any registry changes.
•	The files that the hotfix package contains.

Back to the top

Issue that this hotfix package fixes

This hotfix fixes the following issue that is not previously documented in a Microsoft Knowledge Base article:
In Office Project Professional 2007, when you create a report by using a Visual Reports template, the week number that is displayed in the report differs from the week number that is displayed in Office Project Professional 2007. Therefore, the incorrect week number is displayed in the report.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

To apply this hotfix package, you must have Project 2007 installed on the client computer.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb952293-fullfile-x86-glb.exe	12.0.6300.5000	10,438,496	02-May-2008	09:04	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Project.msp	Not Applicable	9,967,616	01-May-2008	17:53	Not Applicable

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

File name	File version	File size	Date	Time	Platform
P12migrationtool.exe	12.0.6312.5000	7,886,072	18-Apr-2008	08:49	x86
Pj11od11.dll	12.0.6308.5000	1,332,312	22-Mar-2008	11:05	x86
Pjresc.dll	12.0.6300.5000	328,768	08-Dec-2007	12:30	x86
Prjres.dll	12.0.6300.5000	3,650,624	12-Dec-2007	16:18	x86
Serconv.dll	12.0.6308.5000	738,344	22-Mar-2008	11:06	x86
Winproj.exe	12.0.6314.5000	17,339,424	01-May-2008	14:29	x86

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top