Microsoft KB Archive/932619

= You cannot crawl case-sensitive Web content in SharePoint Server 2007 =

Article ID: 932619

Article Last Modified on 9/20/2007

-

APPLIES TO


 * Microsoft Office SharePoint Server 2007

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows XP and Windows Vista



SYMPTOMS
In Microsoft Office SharePoint Server 2007, you add a content source to crawl Web content that resides on a computer that is not running Microsoft Windows. Additionally, the computer supports case-sensitive file names and case-sensitive folder names. When you search for crawled content in a folder that has a name that contains uppercase letters, the search query returns no results. For example, this problem occurs when you search for crawled content in a folder that is named FOLDERNAME.

Additionally, the crawl log contains an error message for each URL that contains an uppercase folder name or an uppercase file name. However, the URLs in the crawl log are displayed in lowercase letters.



How to obtain the hotfix
This issue is fixed in the SharePoint Server 2007 Hotfix Package that is dated April 12, 2007. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

934793 Description of the SharePoint Server hotfix package: April 12, 2007

How to obtain the hotfix
This issue is fixed in the Microsoft Windows SharePoint Services 3.0 Hotfix Package that is dated April 12, 2007. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

934790 Description of the Windows SharePoint Services hotfix package: April 12, 2007

How to enable the hotfixes
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.  Exit any programs that are running. Click Start, click Run, type cmd, and then click OK. At the command prompt, type net stop sptimerv3, and then press ENTER. Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\ \Gather\Portal_Content

 Double-click CaseSensitiveUrls, type 1 in the Value Data box, and then click OK. Exit Registry Editor.</li> At the command prompt, type the following commands. Press ENTER after you type each command: <ul>  net stop osearch </li>  net start osearch </li>  net start sptimerv3 </li></ul> </li></ol>

Note After you apply the hotfix and then set CaseSensitiveUrls to 1, you must reset the indexes. Then, you must recrawl the content.

How to determine the correct Shared Services Provider (SSP)
<ol> Click Start, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.</li> Click Application Management.</li> Under Office SharePoint Server Shared Services, click Create or configure this farm's shared services.</li> Click the list next to the Shared Services Provider for which you want to enable case-sensitive crawling, and then click Edit Properties.</li> Next to the SSP Database section, note the Database Server value and the Database Name value, and then click Cancel.</li> Exit the Web browser.</li> Click Start, click Run, type regedit, and then click OK.</li> Locate and then click the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\12.0\Search\Applications

</li> Expand the first GUID that is listed, and then click the   subkey.</li> Compare the value of the  subkey with the Database Server value and the Database Name value that you noted in step 5.</li> If the Database Server value and the Database Name value are the same as the value of the  subkey, you have located the correct SSP.</li> <li>If the Database Server value and the Database Name value differ from the value of the  subkey, repeat steps 9 and 10 by using the next GUID that is listed under the   registry key.</li></ol>

<div class="status_section">

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

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB932619

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.