In Windows Vista and Windows Server 2008, the Content Indexer service cannot index the custom properties of a document

Assume that you have a document that contains custom properties. In Windows XP or in any pre-Windows XP operating system, the Content Indexer service can index these custom properties. However, in Windows Vista and in Windows Server 2008, the Content Indexer service cannot index these custom properties as expected.

A hotfix is available to resolve this issue. After you install this hotfix and deploy the registry key changes, the earlier version of the Content Indexer service is enabled to work in Windows Vista and in Windows Server 2008. Therefore, you can now index and search custom properties in Microsoft Office documents and in text files as expected.

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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, you must have Windows Vista Service Pack 1 (SP1) or Windows Server 2008 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To have us enable the hotfix for you, go to the “Fix it for me” section. If you would rather enable the hotfix yourself, go to the “Let me fix it myself” section.

Fix it for me

To enable the hotfix automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.



Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.

Now go to the "Did this fix the problem?" section.

Let me fix it myself

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 enable this hotfix, follow these steps:

1. Click Start, type regedit in the Start Search box, and then press ENTER
2. Locate the following registry subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer

3. On the Edit menu, point to New, click DWORD Value, and then type BindDirectlyToPropertySetStorage for the new DWORD value name.
4. Right-click the BindDirectlyToPropertySetStorage registry entry, and then click Modify .
5. In the Value data box, type 1 to enable this hotfix, and then click OK .
6. Exit Registry Editor.
7. Restart the computer.

Note If you do not require the Content Indexer service to search custom properties in Microsoft Office documents or in text files, we recommend that you set the value of the BindDirectlyToPropertySetStorage entry to zero (0).

Now go to the "Did this fix the problem?" section.

Did this fix the problem?

Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support (http://support.microsoft.com/contactus) .

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 SP1 and Windows Server 2008, x86-based versions

Windows Vista SP1 and Windows Server 2008, x64-based versions

Windows Server 2008, Itanium-based versions

This issue occurs because the Content Indexer service that runs in Windows Vista and in Windows Server 2008 cannot use the IPropertySetStorage interface to access custom properties or NTFS properties.

For more information about Microsoft Index Server, visit the following Microsoft Web site:For more information about the IPropertySetStorage interface, visit the following Microsoft Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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