Recommendations to Improve Crawl Performance Post SPS Service Pack 2

SharePoint Portal Server 2003 Service Pack 2, by default, will disable some features previously distributed in service pack 1; this article will key in on feaures specific to search and indexing recommendations to improve crawl performance post-service pack 2 and correct features disabled in service pack 2.

Prevent the indexer from enumerating local groups on WSS crawled content.

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

2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINESoftwareMicrosoftSPSSearchGathering Manager

3. On the Edit menu, point to New, and then click DWORD Value.

4. Type IgnoreWSSLocalGroups, and then press ENTER.

5. Right-click IgnoreWSSLocalGroups, and then click Modify.

6. In the Value data box, type 1, and then click OK.

7. On the File menu, click Exit to quit Registry Editor.

Enable single threaded filter extensions.

Add the WSSSingleThreadedFilterExtensions registry entry to the following registry subkey, and then specify the file name extensions that you want:

HKEY_LOCAL_MACHINESoftwareMicrosoftSPSSearchGathering Manager

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 subkey:

HKEY_LOCAL_MACHINESoftwareMicrosoftSPSSearchGathering Manager

3. On the Edit menu, point to New, and then click String Value.

4. Type WSSSingleThreadedFilterExtensions, and then press ENTER.

5. Right-click WSSSingleThreadedFilterExtensions, and then click Modify.

6. In the Value data box, type the file name extensions that you want. The following are two things to consider when you type file name extensions:

7. Do not use a period character (.) before each file name extension that you type.

8. Separate each file name extension with a semicolon character (;).

For example, if you want to use the single-threaded filter for .jpg files, for .pdf files, and for .gif files, type the following line in the Value data box:

jpg;pdf;gif

1. Click OK, and then click Exit on the File menu to quit Registry Editor.

2. Restart the Microsoft SharePointPS Search service. To do this, follow these steps:

3. Click Start, click Run, type cmd, and then click OK.

4. Stop the Microsoft SharePointPS Search service. To do this, type net stop sharepointpssearch at the command prompt, and then press ENTER.

5. Start the Microsoft SharePointPS Search service. To do this, type net start sharepointpssearch at the command prompt, and then press ENTER.

What happens when a users profile is deleted in SPS.

Typically there is no real impact in the event a user profile is removed from the SharePoint profiles database; the profile will be restored during a full or incremental import. Though the statement is true for the most part when only considering Windows SharePoint Services sites, the behavior varies considerable when including My Site sites in the scenario. Since Windows SharePoint Services content is stored as a table in the sites database, the content can be easily recovered and archived; however, though My Site/Personal site content is similar in this respect many of the end-user facing customization exists as a shared service within SharePoint Portal Server. This content can include, but is not limited to, ‘My Links, My Alerts, etc’. Recovery of the shared services content is more detailed and will require a backup of the profile, sites and services databases to successfully restore the end-users My Site/Personal site to the condition it existed in prior to their profile being removed. The solution includes scheduling an AD import to recreate the missing user profile, recreating the users My Site/Personal site and restoring the contents from the sites database to this site, this will include documents, lists, images, etc. The shared services content can be restored by first learning what content the user had prior to the deletion; this can be achieved from associating the deleted site and user profile in the profile, sites and services backup databases, once determined, the shared services content can be mapped to the new user profile and site.

Renaming a Resource Forest on SharePoint Servers

* I haven’t revisted this post in awhile and thought I would include some additional information on the topic; in response to dkbobe‘s questions surrounding updating the user information; you can use the SPUserUtility to update the tp_Login column to reflect the new domain – more information on this tool can be found at Keith Richie’s blog @ http://blogs.msdn.com/krichie.

I was pleased to see my mention in Joel Oleson’s SharePoint Blog on the Impacts of Renaming a Resource Forest on SharePoint Servers; I’m hoping to elaborate more here as there is little documentation on this topic; at least from the perspective of impacts to SharePoint services.  The good news is that SharePoint services can be recovered after renaming the resource forest without a great deal of configuration management and member server preperation.  One item to note, do NOT run rendom /clean on the SharePoint servers; otherwise, as opposed to only having to reboot the members twice to learn the domain name changes you will be required to disjoin the server from its current forest and rejoin the new forest.  Rebooting twice ensures that each member computer learns of the domain name changes (LSA policy changes) and propagates them to all applications and services running on the member computer. Note that each computer must be restarted by logging into the computer and using the Shutdown/Restart administrative option. Computers must not be restarted by turning off the machine power and then turning it back on, as a result of this you may experience the same behavior as have you run the rendom /clean tool.  As far as the recovery aspect is concerned; recover the servers in the order of (assuming a typical topology), active Microsoft SQL Server node, passive SQL Server node, primary SharePoint Portal Server Web/Search server, SharePoint Portal Server Index server, secondary SharePoint Portal Server Web/Search server.  This will ensure the most rapid restoration of services.  As a prerequisite it is recommended that you collect each member servers IP address and local Administrator credentials in the event the machine is renamed or their are issues impacting name resolution that may prevent access by name.  Assuming the machines have successfully learned of the domain name changes; you will need to reestablish the password used for the service, appication pool, and access accounts for the following service, appication pool, and access accounts  in this order:


  1. Active SQL Server Node:  Cluster Service, SQL Server Agent and MSSQLServer
  2. Passive SQL Server Node:  SQL Server Agent and MSSQLServer
  3. Primary Front-End Web Server:  MSSharePointPortalAppPool and CentralAdminAppPool (NOTE IISRESET when complete)
  4. Primary Front-End Web Server:  SharePoint Timer, SharePoint Portal Administration, Microsoft SharePointPS Search, and SharePoint Portal Alert services
  5. Primary Front-End Web Server:  Configuration Database Administration Account, Default Content Access Account, and SharePoint Central Administration Account (NOTE IISRESET when complete)
  6. Repeat steps 3-5 on the Index/Job Server
  7. Repeat steps 3-5 on the Secondary Front-End Web Server

Web Services, XSL and Windows SharePoint Services Content Management *UPDATED

I recently posted an article detailing how the Content Editor Web Part can be leveraged to display a menu based on the SELECT element, using hypertext markup and javascript to render hyperlinks in a manner that maximizes Windows SharePoint Services real-estate and promotes a positive user experience. Several requests and questions I received as a result of this post were whether or not the hyperlinks in the Content Editor Web Part could be harvested from a List. As a result I’ve put together this, albeit, brief tutorial. In this article you will create a Windows SharePoint Services List, create a new XSL transform Data View Web Part, connect to the Lists Web Service, and specify Exensible Style Language (XSL) and JavaScript (JS) to both render, populate and handle to form content.

Create a Windows SharePoint Services ‘Custom’ List

1. Open a Windows SharePoint Services site in your browser, this site will host the List providing the Web Part its content.

2. Select Documents and Lists from the top navigation bar.

3. Click Create, and then select Custom List under Custom Lists.

4. Enter a name and optional description for the list in the Name: and Description: text boxes and click OK.

5. Select Modify settings and columns on the left navigation bar.

6. Select Add a new column under Columns.

7. Enter URL for the new column name in the Column name: text box and click OK.  Accept the default values when creating the new column.

8. Go back to the list and add at least two new items.  The Title should be the textual representation for your link.

Connect to the Windows SharePoint Services Lists Web Service

1. Open the List in Microsoft Office FrontPage 2003 or a Windows SharePoint Services compatible Web page editor.

2. Select an open area of the page to insert the Data View.

NOTE The following instructions are specific to Microsoft Office FrontPage 2003, consult your Web page editor for instructions corresponding to the remaining instructions.

3. Select Data, and then select Insert Data View.

4. Select Add to catalog… under XML Web Services from the Data Source Catalog dialog.

5. In the Data Source Properties window enter the location for the Lists Web Service in the Service description location box and click Connect Now.  The Lists Web Service is typically located at http://<portal>/<site>/_vti_bin/Lists.asmx?WSDL.

6. Select ListsSoap and GetListItems in the Port: and Operation: menus.

7. Double-click the listName Name in the Parameters(*required) dialog.

8. Enter the name of the List that contains the content for the Web Part in the Value: box and click OK.

9. Click OK on the Data Source Properties window.

10. Click the Web Service from the Data Source Catalog dialog and then select Insert Data View from the menu.

11. Remove the ows_Attachements, ows_Title, and ows_ID columns from the Data View.

12. Select Data from the Microsoft Office FrontPage 2003 taskbar, and then select Style…. from the menu.

13. Select the dropdown HTML view from the list of available views in the View Styles window and click OK.  Click Yes if presented with a formatting warning dialog.

Edit the XSL Transform Data View Web Part Source Code

1. Click Code on the Microsoft Office FrontPage 2003 page view options menu.

2. Locate the line <select name=”ID” size=”1″> and replace with <select name=”spjump” onchange=”window.open(this.options[this.selectedIndex].value)”>.

3. Enter the JavaScript below above the line <select name=”spjump” onchange=”window.open(this.options[this.selectedIndex].value)”>.


<!–

–>function menu_spjump(path) {

window.open = path.options[path.selectedIndex].value;

}

//–>


NOTE You can optionally replace the text Choose One… in the line <option selected=”true” value=”0″>Choose One…</option> to suit your needs, this is the default dropmenu option visible in the Web Part.

4. Locate the line <option style=”display:{$GroupStyle}”> and replace with <option>.

5. Enter the following XSL attributes below the line <option>.

<xsl:attribute name=”value”>

<xsl:value-of select=”@ows_URL”/>

</xsl:attribute>

6. Save the page.

Refresh the Windows SharePoint Services List


  1. Open the Windows SharePoint Services list in your browser.  Your XSL Data View will be visible below the standard List view.

Additional Options

If you would like to use the dropdown menu on another area of your site or install the menu as a Web Part elsewhere in your SharePoint environment, repeat the steps in the section Connect to the Windows SharePoint Services Lists Web Service; however, prior to step 3, select Data, and the select Web Part Zone from the menu in Microsoft Office FrontPage 2003, then proceed to with the remaining steps.  This option will create a Web Part in which the dropdown menu will be hosted.  You can export the Web Part from the Lists page in Windows SharePoint Services and uploaded the Web Part to other sites in your SharePoint environment on elsewhere on your site. The dropdown menu will show content added to your list.  If you would like to leverage the OPTGROUP element, simply create an additional column in your List labeled OPTGROUP and call the values in the XSL stylesheet for the List.

If you have any questions on how to implement steps in this tutorial or require troubleshooting assistance, please comment below.