Adding Properties to MOSS Advanced Search
http://www.codeproject.com/spoint/MOSS_Advanced_Search.asp?print=true
How to: Change the Properties Returned in the Core Search Results
http://msdn2.microsoft.com/en-us/library/ms560074.aspx
How to: Display a Search Scope in the Search Box and Advanced Search Web Parts
http://msdn2.microsoft.com/en-us/library/ms498872.aspx
Walkthrough: Add a Tab and Custom Search Page with Enterprise Search Web Parts to the Search Center
http://msdn2.microsoft.com/en-us/library/ms584031.aspx
Sunday, July 22, 2007
Links: SharePoint V3: Search: Planning
Plan search (Office SharePoint Server)
http://technet2.microsoft.com/Office/en-us/library/e8c0fccd-8364-4352-8778-c9c46a668b701033.mspx
Plan for administrative and service accounts (Office SharePoint Server
http://technet2.microsoft.com/Office/en-us/library/f07768d4-ca37-447a-a056-1a67d93ef5401033.mspx?mfr=true
MOSS Search - Customer Proof of Concept Scoping and Typical Tasks
http://blogs.msdn.com/miketag/archive/2007/01/18/moss-search-customer-proof-of-concept-scoping-and-typical-tasks.aspx
SharePoint Deployment Capacity & Performance Planning 2003 & 2007
http://blogs.msdn.com/joelo/archive/2006/07/19/671789.aspx
Estimate performance and capacity requirements for search environments
http://technet2.microsoft.com/Office/en-us/library/5465aa2b-aec3-4b87-bce0-8601ff20615e1033.mspx?mfr=true
Estimate performance and capacity requirements for Internet environments (Office SharePoint Server)
http://technet2.microsoft.com/Office/en-us/library/45997bad-da15-4442-8727-78e0f2dc5a9c1033.mspx?mfr=true
Estimate MOSS Search Disk Space Requirements
http://blogs.msdn.com/miketag/archive/2007/07/05/estimate-moss-search-disk-space-requirements.aspx
http://technet2.microsoft.com/Office/en-us/library/e8c0fccd-8364-4352-8778-c9c46a668b701033.mspx
Plan for administrative and service accounts (Office SharePoint Server
http://technet2.microsoft.com/Office/en-us/library/f07768d4-ca37-447a-a056-1a67d93ef5401033.mspx?mfr=true
MOSS Search - Customer Proof of Concept Scoping and Typical Tasks
http://blogs.msdn.com/miketag/archive/2007/01/18/moss-search-customer-proof-of-concept-scoping-and-typical-tasks.aspx
SharePoint Deployment Capacity & Performance Planning 2003 & 2007
http://blogs.msdn.com/joelo/archive/2006/07/19/671789.aspx
Estimate performance and capacity requirements for search environments
http://technet2.microsoft.com/Office/en-us/library/5465aa2b-aec3-4b87-bce0-8601ff20615e1033.mspx?mfr=true
Estimate performance and capacity requirements for Internet environments (Office SharePoint Server)
http://technet2.microsoft.com/Office/en-us/library/45997bad-da15-4442-8727-78e0f2dc5a9c1033.mspx?mfr=true
Estimate MOSS Search Disk Space Requirements
http://blogs.msdn.com/miketag/archive/2007/07/05/estimate-moss-search-disk-space-requirements.aspx
Labels:
Links,
Search,
SharePoint,
SharePoint 3.0
Friday, July 13, 2007
SharePoint V1, V2, V3: SharePoint Web Site Prompts User For Windows Credentials
Description:
SharePoint web site prompts user for Windows credentials
Solution:
Open Internet Explorer
Tools
Internet Options
Security Tab
Highlight "Local Intranet"
Click Sites
Add SharePoint URLs
Click Close to close Local Intranet
Highlight "Local Intranet"
Click Custom Level
Scroll to the option User "Authentication: Logon"
Set this to "Automatic logon only in Intranet zone"
Click OK to close Security Settings
Click OK to close Internet Options
Navigate Internet Explorer to SharePoint URL
SharePoint web site prompts user for Windows credentials
Solution:
Open Internet Explorer
Tools
Internet Options
Security Tab
Highlight "Local Intranet"
Click Sites
Add SharePoint URLs
Click Close to close Local Intranet
Highlight "Local Intranet"
Click Custom Level
Scroll to the option User "Authentication: Logon"
Set this to "Automatic logon only in Intranet zone"
Click OK to close Security Settings
Click OK to close Internet Options
Navigate Internet Explorer to SharePoint URL
Labels:
Authentication,
Internet Explorer,
SharePoint
WhitePaper: Microsoft Office Programs and SharePoint Products and Technologies Integration Fair, Good, Better, Best
This document compares the user experiences of Office 2007 and Office 2003 as it relates to SharePoint 2007 integration. It summarizes the benefits of Office 2007. This information is helpful for anybody with SharePoint 2007 who might be considering an upgrade to Office 2007, or maybe somebody who already has upgraded to Office 2007 and wants to understand the SharePoint 2007 integration features available to them.
WhitePaper: Microsoft Office Programs and SharePoint Products and Technologies Integration Fair, Good, Better, Best
WhitePaper: Microsoft Office Programs and SharePoint Products and Technologies Integration Fair, Good, Better, Best
Thursday, July 12, 2007
SharePoint V3: Configuring the "I Need To..." Web Part
* Create a custom list (e.g. Site List) with the following columns:
Title (single line of text)
URL (hyperlink)
Visable (choice, checkbox, yes is only option, yes is default value)

* Add the "I Need To..." web part to a web page
* Modify Shared Web Part
* Click the Change button and set the following fields:
Select custom list (e.g. Site List)
Filter Field: Visible
Filter Value: Yes
Title (single line of text)
URL (hyperlink)
Visable (choice, checkbox, yes is only option, yes is default value)
* Add the "I Need To..." web part to a web page
* Modify Shared Web Part
* Click the Change button and set the following fields:
Select custom list (e.g. Site List)
Filter Field: Visible
Filter Value: Yes
Thursday, July 05, 2007
SharePoint V2, V3: Error: Service Unavailable
Description:
* This applies to: WSS 2.0, WSS 3.0, SPS2003, MOSS2007
* Service account password had changed.
* Site returns error: "Service Unavailable"

Solution:
IIS Manager > Application Pool Properties > Identity Tab
* Update the service account and password

Start > Run
* IISRESET /noforce
Start > Programs > Administrative Tools > Services
* Update user name and password for any other services registered with this user account
* Restart the updated services
* This applies to: WSS 2.0, WSS 3.0, SPS2003, MOSS2007
* Service account password had changed.
* Site returns error: "Service Unavailable"
Solution:
IIS Manager > Application Pool Properties > Identity Tab
* Update the service account and password
Start > Run
* IISRESET /noforce
Start > Programs > Administrative Tools > Services
* Update user name and password for any other services registered with this user account
* Restart the updated services
Thursday, June 28, 2007
SharePoint V3: Site Images Appear as Red X
Description:
After logging into a SharePoint Web Application, the site images show as red x.

Solution:
* IIS Manager > Application Pool Properties for Web Application > Identity
* Select "Configurable" radio button
* For user name and password, type the domain\username and password of a farm service account
* Run IIS Reset

After logging into a SharePoint Web Application, the site images show as red x.
Solution:
* IIS Manager > Application Pool Properties for Web Application > Identity
* Select "Configurable" radio button
* For user name and password, type the domain\username and password of a farm service account
* Run IIS Reset
SharePoint V3: Error: Access Denied When Clicking User Profiles and Properties in SSP
Description:
Shared Service Provider > User Profiles and Properties
Error: Access Denied


Solution:
Log into Shared Service Provider web application using an administrator account. In Actions > Site Settings > All Site Settings > Advanced Permissions, add the users to the access list for the site and assign permissions. In Actions > Site Settings > All Site Settings > Site Collection Owners, add the user account as a site collection owner if desired.
Shared Service Provider > User Profiles and Properties
Error: Access Denied
Solution:
Log into Shared Service Provider web application using an administrator account. In Actions > Site Settings > All Site Settings > Advanced Permissions, add the users to the access list for the site and assign permissions. In Actions > Site Settings > All Site Settings > Site Collection Owners, add the user account as a site collection owner if desired.
Wednesday, June 13, 2007
SharePoint V2: How to Configure and View Diagnostic Logs for Search in SharePoint Portal Server 2003
Configuring:
Central Admin > Component Configuration > Configure Diagnostic Settings

Under Logging Settings, highlight Search Service and click Edit

Modify the logging level (remember to go back afterwards and set it back to avoid using disk space unnecessarily)

Viewing:
Under View Diagnostic Logs, highlight the most recent search log and click View
Central Admin > Component Configuration > Configure Diagnostic Settings
Under Logging Settings, highlight Search Service and click Edit
Modify the logging level (remember to go back afterwards and set it back to avoid using disk space unnecessarily)
Viewing:
Under View Diagnostic Logs, highlight the most recent search log and click View
Monday, June 11, 2007
Links: SharePoint V3: What every SharePoint administrator needs to know about Alternate Access Mappings
Thursday, June 07, 2007
SharePoint V3: Error Importing User Profiles
Description:
In Microsoft Office SharePoint Server 2007, after initiating a full user profile import, the user profiles fail to import and the crawl log contains the following error:
"The specified domain either does not exist or could not be contacted. (Exception from HRESULT: 0x8007054B)"
Solution:
Adding WINS addresses to the LAN Connection properties corrected this issue.
1.
From the Index server: Control Panel > Network Connections > LAN Connection Properties > WINS tab
Add WINS server addresses
2.
SSP Admin > User Profile and Properties > Import
Perform user profile import
Verify import is successful
In Microsoft Office SharePoint Server 2007, after initiating a full user profile import, the user profiles fail to import and the crawl log contains the following error:
"The specified domain either does not exist or could not be contacted. (Exception from HRESULT: 0x8007054B)"
Solution:
Adding WINS addresses to the LAN Connection properties corrected this issue.
1.
From the Index server: Control Panel > Network Connections > LAN Connection Properties > WINS tab
Add WINS server addresses
2.
SSP Admin > User Profile and Properties > Import
Perform user profile import
Verify import is successful
Wednesday, June 06, 2007
SharePoint V2: Adding a New Portal to an SPS 2003 Server Farm
Description:
This blog post explains how to add a new portal to a SharePoint Portal Server 2003 farm having two front end web servers.
Solution:
Web Server #1
* From Windows Explorer: Create a directory on a non operating sytem drive to be used for the new IIS web site.
* From IIS Manager: Create a new web site, using the new directory as the home directory. Disable anonymous access.
* From SharePoint Portal Server 2003 Central Administration:
SharePoint Portal Server > Portal Site and Virtual Server Configuration > Create a Portal
Site Name: Give the portal a name, consider using host header or port number in name.
Virtual Server: Select the new IIS web site. Site URL: e.g. http://webserver1:port
Account Name, Email Address
Web Server #2
* From Windows Explorer: Create a directory on a non operating sytem drive to be used for the new IIS web site.
* From IIS Manager: Create a new web site, using the new directory as the home directory. Disable anonymous access.
* From SharePoint Portal Server 2003 Central Administration:
Windows SharePoint Services > Virtual Server Configuration > Extend or Upgrade Virtual Server Provisioning Options > Extend and map to another virtual server Current
Virtual Server: Verify this is set to the web site you want to extend
Server Mapping: Select the virtual server that was created on web server #1 Wait for refresh cache on the other serverse to succeed and click ok.
This blog post explains how to add a new portal to a SharePoint Portal Server 2003 farm having two front end web servers.
Solution:
Web Server #1
* From Windows Explorer: Create a directory on a non operating sytem drive to be used for the new IIS web site.
* From IIS Manager: Create a new web site, using the new directory as the home directory. Disable anonymous access.
* From SharePoint Portal Server 2003 Central Administration:
SharePoint Portal Server > Portal Site and Virtual Server Configuration > Create a Portal
Site Name: Give the portal a name, consider using host header or port number in name.
Virtual Server: Select the new IIS web site. Site URL: e.g. http://webserver1:port
Account Name, Email Address
Web Server #2
* From Windows Explorer: Create a directory on a non operating sytem drive to be used for the new IIS web site.
* From IIS Manager: Create a new web site, using the new directory as the home directory. Disable anonymous access.
* From SharePoint Portal Server 2003 Central Administration:
Windows SharePoint Services > Virtual Server Configuration > Extend or Upgrade Virtual Server Provisioning Options > Extend and map to another virtual server Current
Virtual Server: Verify this is set to the web site you want to extend
Server Mapping: Select the virtual server that was created on web server #1 Wait for refresh cache on the other serverse to succeed and click ok.
Tuesday, June 05, 2007
SharePoint V3: Configuring the Author Managed Property
Description:
This blog post explains how to configure the Author managed property so that it may be used effectively in Search within an Office SharePoint Server 2007 environment.
Solution:
SSP Admin > Search Settings > Metadata Property Mappings > Managed Properties > Author
Step 1
Set the "Mappings to crawled properties" radio button to "Include values from a single crawled property based on the order specified." It is common to expose the Author property in search results, so don't "include all values from crawled properties mapped" because your search results will end up with mulitple names listed beside the search result and it will be difficult to distinguish which is really the author.
Step 2
Map the most relevant crawled properties to the Author managed property, and position them in the best possible sequence. Obviously, if authors are truly dilligent about maintaining the Office document Author property within the document itself , then this is best candidate for first position. However, in many organizations, this property is not actively maintained. SharePoint's Created By property isn't always an accurate indicator of who actually created the document, so this one also tends to fail as being a reliable first position candidate. In many cases, the best thing to do is to create a custom Author site column, make it required, and add it to all document content types. Then, map the corresponding crawled property as first position. This ensures that the Author information will be maintained to some degree by people touching the documents.
Once the first position is set, then add and order the subsequent crawled properties.
This blog post explains how to configure the Author managed property so that it may be used effectively in Search within an Office SharePoint Server 2007 environment.
Solution:
SSP Admin > Search Settings > Metadata Property Mappings > Managed Properties > Author
Step 1
Set the "Mappings to crawled properties" radio button to "Include values from a single crawled property based on the order specified." It is common to expose the Author property in search results, so don't "include all values from crawled properties mapped" because your search results will end up with mulitple names listed beside the search result and it will be difficult to distinguish which is really the author.
Step 2
Map the most relevant crawled properties to the Author managed property, and position them in the best possible sequence. Obviously, if authors are truly dilligent about maintaining the Office document Author property within the document itself , then this is best candidate for first position. However, in many organizations, this property is not actively maintained. SharePoint's Created By property isn't always an accurate indicator of who actually created the document, so this one also tends to fail as being a reliable first position candidate. In many cases, the best thing to do is to create a custom Author site column, make it required, and add it to all document content types. Then, map the corresponding crawled property as first position. This ensures that the Author information will be maintained to some degree by people touching the documents.
Once the first position is set, then add and order the subsequent crawled properties.
SharePoint V2: Error: Upgrade Pre-Scan Error, Orphaned Site
Description:
During preparation for an upgrade to Microsoft Office SharePoint Server 2007, after running prescan.exe on a SharePoint Portal Server 2003 environment, the pre-upgrade report lists an error such as the one below.
06/04/2007 16:26:59 Error: Cannot get content database Id for SPSite: http://servername/sites/sitename
06/04/2007 16:26:59 Microsoft.SharePoint.SPException: There is no Web named "/sites/sitename". ---> System.Runtime.InteropServices.COMException (0x81070504): There is no Web named "/sites/sitename". at Microsoft.SharePoint.Library.SPRequestInternalClass.OpenSite(String bstrUrl, Boolean bGetUrlOnly, String& pbstrServerRelativeUrl, Guid& pgSiteId, Int32& pOwnerID, Int32& pSecondaryContactID, DateTime& pdtLastContentChange, DateTime& pdtLastSecurityChange) at Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7) --- End of inner exception stack trace --- at Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7) at Microsoft.SharePoint.SPSite.c() at Microsoft.SharePoint.SPSite.get_ID() at Microsoft.SharePoint.PreupgradeReport.Scan.GetContentDBBySite(SPSite site, SPVirtualServer vs)
Solution:
Windows SharePoint Services 2.0 and SharePoint Portal Server 2003 each have their own approach to cleaning up orphaned records. The KB articles below provide information on related hotfixes and explain how to use command line utilities to clean up corrupted databases.
Windows SharePoint Services 2.0
http://support.microsoft.com/kb/924881
http://support.microsoft.com/kb/918744
From: \program files\common files\microsoft shared\web server extensions\60\bin
To Detect: stsadm -o databaserepair -url http://ServerName -databasename DatabaseName
To Repair: stsadm -o databaserepair -url http://ServerName -databasename DatabaseName -deletecorruption
SharePoint Portal Server 2003
http://support.microsoft.com/kb/919175
http://support.microsoft.com/kb/918742
From: \programfiles\Sharepoint Portal Server\Bin
To Repair: spsadm repairorphans http://ServerName
During preparation for an upgrade to Microsoft Office SharePoint Server 2007, after running prescan.exe on a SharePoint Portal Server 2003 environment, the pre-upgrade report lists an error such as the one below.
06/04/2007 16:26:59 Error: Cannot get content database Id for SPSite: http://servername/sites/sitename
06/04/2007 16:26:59 Microsoft.SharePoint.SPException: There is no Web named "/sites/sitename". ---> System.Runtime.InteropServices.COMException (0x81070504): There is no Web named "/sites/sitename". at Microsoft.SharePoint.Library.SPRequestInternalClass.OpenSite(String bstrUrl, Boolean bGetUrlOnly, String& pbstrServerRelativeUrl, Guid& pgSiteId, Int32& pOwnerID, Int32& pSecondaryContactID, DateTime& pdtLastContentChange, DateTime& pdtLastSecurityChange) at Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7) --- End of inner exception stack trace --- at Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7) at Microsoft.SharePoint.SPSite.c() at Microsoft.SharePoint.SPSite.get_ID() at Microsoft.SharePoint.PreupgradeReport.Scan.GetContentDBBySite(SPSite site, SPVirtualServer vs)
Solution:
Windows SharePoint Services 2.0 and SharePoint Portal Server 2003 each have their own approach to cleaning up orphaned records. The KB articles below provide information on related hotfixes and explain how to use command line utilities to clean up corrupted databases.
Windows SharePoint Services 2.0
http://support.microsoft.com/kb/924881
http://support.microsoft.com/kb/918744
From: \program files\common files\microsoft shared\web server extensions\60\bin
To Detect: stsadm -o databaserepair -url http://ServerName -databasename DatabaseName
To Repair: stsadm -o databaserepair -url http://ServerName -databasename DatabaseName -deletecorruption
SharePoint Portal Server 2003
http://support.microsoft.com/kb/919175
http://support.microsoft.com/kb/918742
From: \programfiles\Sharepoint Portal Server\Bin
To Repair: spsadm repairorphans http://ServerName
Labels:
.0,
SharePoint,
SharePoint 2.0,
Support,
Upgrade
Friday, June 01, 2007
SharePoint V3: MOSS 2007 Search: How to Index Lotus Notes Content
I recently configured MOSS Search to index Lotus Notes. Here is an overview of the process.
Preparation:
* Lotus Notes server name
* Lotus Notes database file name
* List of fields you want to display in search results
* Notes user logon file (e.g. user.id)
* User credentials for installing Notes client
Steps:
* Install Lotus Notes Client 6.0 to the SharePoint Index Server
* From the index server, share the c:\program files\lotus\notes\data directory allowing WSS_WPG group access
* From an existing workstation, copy a valid user id file to index server c:\program files\lotus\notes\data
* Download the Lotus C++ API Toolkit 3.0I* Extract the files* Copy lcppn30i.dll to the index server, c:\program files\microsoft office servers\12.0\bin
* Rename 1cppn30i.dll to 1cppn30.dll
* From index server, c:\program files\microsoft office servers\12.0\bin, execute notessetup.exe
* Specify the server name, database file, view, etc.
* From index server, cmd prompt, net stop osearch, then net start osearch
* SSP Admin > Search Settings > Content Sources: Configure content source for Lotus Notes
* SSP Admin > Search Settings > Scopes: Configure scope for Lotus Notes content source
* SSP Admin > Search Settings > MetaData Property Mappings: Create managed properties for those Lotus Notes properties that you want to search or display in search results
* Search Center: Configure the search web parts and search results web parts (and related xml files) to display useful field when the search result item is coming from the Lotus content source
Lessons:
* The notessetup.exe won't work with the 1cppn30i.dll file name, need to rename it to 1cppn30.dll
* I used 6.0 Notes Client, because Notes Client 6.5 did not create a data directory
References:
* Configure Office SharePoint Server Search to crawl Lotus Notes (Office SharePoint Server 2007 for Search)
* Using SharePoint 2007 to Index Lotus
* Secure crawls of Lotus Notes with SharePoint
* How to Configure Search to Honor Lotus Notes Security Settings
* MOSS2007 Search and Index Lotus Notes
* IBM software downloads (for Lotus C++ API ToolKit)
Preparation:
* Lotus Notes server name
* Lotus Notes database file name
* List of fields you want to display in search results
* Notes user logon file (e.g. user.id)
* User credentials for installing Notes client
Steps:
* Install Lotus Notes Client 6.0 to the SharePoint Index Server
* From the index server, share the c:\program files\lotus\notes\data directory allowing WSS_WPG group access
* From an existing workstation, copy a valid user id file to index server c:\program files\lotus\notes\data
* Download the Lotus C++ API Toolkit 3.0I* Extract the files* Copy lcppn30i.dll to the index server, c:\program files\microsoft office servers\12.0\bin
* Rename 1cppn30i.dll to 1cppn30.dll
* From index server, c:\program files\microsoft office servers\12.0\bin, execute notessetup.exe
* Specify the server name, database file, view, etc.
* From index server, cmd prompt, net stop osearch, then net start osearch
* SSP Admin > Search Settings > Content Sources: Configure content source for Lotus Notes
* SSP Admin > Search Settings > Scopes: Configure scope for Lotus Notes content source
* SSP Admin > Search Settings > MetaData Property Mappings: Create managed properties for those Lotus Notes properties that you want to search or display in search results
* Search Center: Configure the search web parts and search results web parts (and related xml files) to display useful field when the search result item is coming from the Lotus content source
Lessons:
* The notessetup.exe won't work with the 1cppn30i.dll file name, need to rename it to 1cppn30.dll
* I used 6.0 Notes Client, because Notes Client 6.5 did not create a data directory
References:
* Configure Office SharePoint Server Search to crawl Lotus Notes (Office SharePoint Server 2007 for Search)
* Using SharePoint 2007 to Index Lotus
* Secure crawls of Lotus Notes with SharePoint
* How to Configure Search to Honor Lotus Notes Security Settings
* MOSS2007 Search and Index Lotus Notes
* IBM software downloads (for Lotus C++ API ToolKit)
Monday, May 21, 2007
SharePoint V3: Fresh MOSS 2007 Search Configuration for Medium Server Farm
Description
After configuring and starting MOSS Search, you wish to have a clean configuration. Maybe the indexing process doesn't seem to be working correctly. Or, perhaps there are issues with the propogated index share folder. Or, maybe the crawler doesn't seem to complete its process. Or, maybe the first time around you forgot about your database naming convention and you want to rename the search database to something more relevant. Whatever the issue or reason, the solution below offers a way to gain a fresh start with MOSS search configuration. This solution creates a new search database, it clears the index and propogated index file shares and creates new ones.
Solution
From each of the search servers
* Start > Run > CMD
* net stop osearch
From each of the query servers
* Central Admin > Services on Server
* Stop/Remove MOSS Search (query) from each of the query search servers
From the index server
* Central Admin > Services on Server
* Stop/Remove MOSS search (index)
From the index server
* Central Admin > Services on server
* Note the database name
* Stop/Remove WSS search
From the index server
* Central Admin > Services on server
* Start/Add the WSS Search (this requires creating a new db)
From the index server
* Central Admin > Services on server
* Start/Add the MOSS Search (select only the index checkbox)
From each of the query servers
* Central Admin > Services on server
* Start/Add MOSS Search (select only the query checkbox)
From the SSP
* SSP Admin > User Profiles
* Verify that user profiles have been imported
From the SSP
* SSP Admin > Search Settings
* Verify all content sources, crawl rules, schedules, scopes are configured properly
* Perform a full crawl of content
After configuring and starting MOSS Search, you wish to have a clean configuration. Maybe the indexing process doesn't seem to be working correctly. Or, perhaps there are issues with the propogated index share folder. Or, maybe the crawler doesn't seem to complete its process. Or, maybe the first time around you forgot about your database naming convention and you want to rename the search database to something more relevant. Whatever the issue or reason, the solution below offers a way to gain a fresh start with MOSS search configuration. This solution creates a new search database, it clears the index and propogated index file shares and creates new ones.
Solution
From each of the search servers
* Start > Run > CMD
* net stop osearch
From each of the query servers
* Central Admin > Services on Server
* Stop/Remove MOSS Search (query) from each of the query search servers
From the index server
* Central Admin > Services on Server
* Stop/Remove MOSS search (index)
From the index server
* Central Admin > Services on server
* Note the database name
* Stop/Remove WSS search
From the index server
* Central Admin > Services on server
* Start/Add the WSS Search (this requires creating a new db)
From the index server
* Central Admin > Services on server
* Start/Add the MOSS Search (select only the index checkbox)
From each of the query servers
* Central Admin > Services on server
* Start/Add MOSS Search (select only the query checkbox)
From the SSP
* SSP Admin > User Profiles
* Verify that user profiles have been imported
From the SSP
* SSP Admin > Search Settings
* Verify all content sources, crawl rules, schedules, scopes are configured properly
* Perform a full crawl of content
SharePoint Error: Service Unavailable
Description:
Users receive "Service Unavailable" error when they point their browsers at the SharePoint site
Solution:
* Administrative Tools > Services > SQL Server Service > Log On Tab
Set the identity to a domain user account
Restart the service
* IIS Manager > Application Pools > Application Pool Properties > Identity Tab
Set the identity to a domain user account (e.g. use same as sql server service account)
* Start > Run > IISReset
See Also:
Microsoft Support KB973917: Description of the update that implements Extended Protection for Authentication in Internet Information Services (IIS) http://support.microsoft.com/kb/973917
Users receive "Service Unavailable" error when they point their browsers at the SharePoint site
Solution:
* Administrative Tools > Services > SQL Server Service > Log On Tab
Set the identity to a domain user account
Restart the service
* IIS Manager > Application Pools > Application Pool Properties > Identity Tab
Set the identity to a domain user account (e.g. use same as sql server service account)
* Start > Run > IISReset
See Also:
Microsoft Support KB973917: Description of the update that implements Extended Protection for Authentication in Internet Information Services (IIS) http://support.microsoft.com/kb/973917
Subscribe to:
Posts (Atom)
Events / Conferences / User Groups
- AIIM Conference
- Boston Area SharePoint User Group
- Boston Azure User Group
- Collaborate
- DevConnections
- DevIntersection
- Enterprise Search Summit
- Microsoft Build
- Microsoft SharePoint Conference
- Microsoft TechEd
- New England ASP.NET Professionals User Group
- New England Oracle Applications User Group
- Oracle Applications User Group (OAUG)
- Oracle OpenWorld
- PeopleSoft Government Contractor Special Interest Group
- PeopleSoft Southern New England Users Group
- Quest International Users Group
- SharePoint Saturday
- SPTechCon
- SQL PASS
- SQL Saturday
- Startup Weekend
