Reset Crawled Content on MOSS 2007 Shared Services

If you need to reset the Reset Crawled Content on MOSS 2007 Shared Services

• Open SharePoint Central Administration, select Application Management
• On the Application Management page, click Create or configure this farm’s shared services.
• On the Manage this Farms Shared Services page, click the SSP to reset.
• Select Search settings in the Search section.
• On the Configure Search Settings page, click Reset all crawled content in the Crawl Settings section
• By default, the Deactivate search alerts during reset check box is selected on the Reset Crawled Content page. This option prevents users who have search alerts configured from being sent unnecessary e-mail messages when the crawled content is reset. Click to clear this check box if you do not want to disable alerts during the reset operation.
• Click Reset Now.
• In the message box, click OK to confirm that you want to reset the search content index.

Key words
"Error The content index is corrupt. Unable to connect ..."

Resources
MOSS Search. Error The content index is corrupt. Unable to connect to the Search Service

MOSS: Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content.

When working with MOSS today: Running a farm setup on a single machine with Server 2008, Sql Server 2008, and MOSS 2007.

Trying to get the search service to complete a Crawl of the local SharePoint sites, I was receiving "Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content."

After validating that the account had access to the content (sites), and verifying that there were no crawl rules, I eventually expected to find the answer in the event log.

In the event log, there were no entries like the expected "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: ]", and according to the log everything was running correctly.

As an additional check, I set up the crawler service to run against another SharePoint server, using the same crawl account credentials. Worked fine without a problem.

After checking around, I ran across this post on Microsoft TechNet Forums: http://social.technet.microsoft.com/forums/en-US/sharepointsearch/thread/84f93fbe-f4a6-4683-b25b-b595b9006ad7/

Within the post, someone recommends re-entering the crawler account credentials. I re-entered the credentials, and initiated a full site crawl. The error still occurred, with the same message.

After reading further into others that had encountered this problem, it would appear that the Loopback check security feature is back in Server 2008. After running the work-around http://support.microsoft.com/kb/896861 (see Method 1: Disable the loopback check), and restarting the machine the site can now be crawled.

Resources:
http://social.technet.microsoft.com/forums/en-US/sharepointsearch/thread/84f93fbe-f4a6-4683-b25b-b595b9006ad7/
http://support.microsoft.com/kb/896861

Shared Service Providers (SSP) with MOSS 2007

What are Shared Service Providers (SSP) with MOSS 2007?

I've recently started digging into the Shared Service Providers (SSP) for MOSS 2007.

The idea behind the Shared Service Providers (SSP) within Microsoft Office SharePoint Server (MOSS) is to allow for centralized control of features that are common among different sites. This also allows for sharing of these features between sites.

The Shared Service Providers completes all of the work around it's various processes, and is used by your web applications to locate the information requested.

SSPs are separate web applications and surprising are not required when setting up a site, but some features (like Search) will not work correctly until the first SSP is set up and configured.

This is the list of shared services that are handled by the Shared Service Providers model:

Search
Index
Audience compilation and User profiles database
My Sites
Business Data Catalogue (BDC)
Excel Services

How to set up a Shared Service Providers (SSP) with MOSS 2007

1. Open SharePoint central administration site

2. Click on "Shared Service Administration" on the left naviation

3. Click on "New SSP" below "Manage this Farm's Shared Services"

Here are some articles that I was able to locate on the topic:
MOSS Architecture and Shared Services
What is a Shared Service Provider?

Windows SharePoint Services 3.0 Application Templates: All Templates

When installing the Windows SharePoint Services 3.0 Application Templates: All Templates package I found the directions to be a bit lacking.

There was a great blog post out there on the
Microsoft SharePoint Team Blog, but it was a little difficult to follow, and event harder to get the commands to complete the installation.

Basically, the installation that I am working with is a virtual machine running Windows 2008 server, and a beta version of SQL Server 2008. SharePoint is set up as a farm, using an SQL configuration database hosted on the same machine (with a few changes the steps below should work for a database on another box).

Here are the steps that I used:
Double click on AllTemplates
and extract to (C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN on my machine)

Open a command line prompt, and navigate to the directory from the previous step. Run these commands.

stsadm -o addsolution -filename ApplicationTemplateCore.wsp
stsadm -o deploysolution -name ApplicationTemplateCore.wsp -local -allowGacDeployment
stsadm -o copyappbincontent

--ApplicationTemplateCore.wsp
stsadm -o addsolution -filename AbsenceVacationSchedule.wsp
stsadm -o addsolution -filename BudgetingTrackingMultipleProjects.wsp
stsadm -o addsolution -filename BugDatabase.wsp
stsadm -o addsolution -filename CallCenter.wsp
stsadm -o addsolution -filename ChangeRequest.wsp
stsadm -o addsolution -filename ComplianceProcessSupport.wsp
stsadm -o addsolution -filename ContactsManagement.wsp
stsadm -o addsolution -filename DocumentLibraryReview.wsp
stsadm -o addsolution -filename EventPlanning.wsp
stsadm -o addsolution -filename ExpenseReimbursementApproval.wsp
stsadm -o addsolution -filename HelpDesk.wsp
stsadm -o addsolution -filename InventoryTracking.wsp
stsadm -o addsolution -filename ITTeamWorkspace.wsp
stsadm -o addsolution -filename JobRequisition.wsp
stsadm -o addsolution -filename KnowledgeBase.wsp
stsadm -o addsolution -filename LendingLibrary.wsp
stsadm -o addsolution -filename PhysicalAssetTracking.wsp
stsadm -o addsolution -filename ProjectTrackingWorkspace.wsp
stsadm -o addsolution -filename RoomEquipmentReservations.wsp
stsadm -o addsolution -filename SalesLeadPipeline.wsp

stsadm -o deploysolution -name BudgetingTrackingMultipleProjects.wsp -local -allowGacDeployment
stsadm -o deploysolution -name BugDatabase.wsp -local -allowGacDeployment
stsadm -o deploysolution -name CallCenter.wsp -local -allowGacDeployment
stsadm -o deploysolution -name ChangeRequest.wsp -local -allowGacDeployment
stsadm -o deploysolution -name ComplianceProcessSupport.wsp -local -allowGacDeployment
stsadm -o deploysolution -name ContactsManagement.wsp -local -allowGacDeployment
stsadm -o deploysolution -name DocumentLibraryReview.wsp -local -allowGacDeployment
stsadm -o deploysolution -name EventPlanning.wsp -local -allowGacDeployment
stsadm -o deploysolution -name ExpenseReimbursementApproval.wsp -local -allowGacDeployment
stsadm -o deploysolution -name HelpDesk.wsp -local -allowGacDeployment
stsadm -o deploysolution -name InventoryTracking.wsp -local -allowGacDeployment
stsadm -o deploysolution -name ITTeamWorkspace.wsp -local -allowGacDeployment
stsadm -o deploysolution -name JobRequisition.wsp -local -allowGacDeployment
stsadm -o deploysolution -name KnowledgeBase.wsp -local -allowGacDeployment
stsadm -o deploysolution -name LendingLibrary.wsp -local -allowGacDeployment
stsadm -o deploysolution -name PhysicalAssetTracking.wsp -local -allowGacDeployment
stsadm -o deploysolution -name ProjectTrackingWorkspace.wsp -local -allowGacDeployment
stsadm -o deploysolution -name RoomEquipmentReservations.wsp -local -allowGacDeployment
stsadm -o deploysolution -name SalesLeadPipeline.wsp -local -allowGacDeployment

stsadm -o copyappbincontent
stsadm -o execadmsvcjobs

The directions for the application templates included in the package worked well for me. This is a direct copy of those directions:
1. Download the site template EXE file to your computer.
2. Run the EXE file to unpack the template file to a
location on your computer.
3. Select the template file, .stp, from
the extracted distribution for the application template
you wish to install.
4. Log into your SharePoint site as the site Administrator.
5. From the Site Actions drop-down menu in the top right,
select Site Settings.
6. Under the Galleries section, select Site templates.
7. Select Upload to load an application template into this
SharePoint site.
8. Browse to the .stp file from the distribution
and select Open. If you have several application templates
to load into your site, you can use the Upload Multiple
Files… option to load them all at once.
9. Click Ok to complete the upload of the application template
to your SharePoint site.


Here is some additional information on the stsadm utility:
Stsadm command-line tool (Office SharePoint Server)
http://technet.microsoft.com/en-us/library/cc261956.aspx

SharePoint Wiki

Lately I've been working with the Wiki from Windows SharePoint Services 3.0, and it's pretty limited.

One of the topics that I was (and still am) interested in is what Wiki commands will work in the SharePoint version.

If your reading this, and wondering what will work, you should be glad to know your search is over.

The total number of supported wiki commands: 1

Link to Wiki Article
Link to Page: [[Page Name]]
However, it does support adding a link with different text, following this syntax: [[Page NameDisplay Text]]

Example: [[MoneyFinancial Information]]