</compilation>
  <pages enableSessionState="false" enableViewState="true" enableViewStateMac="true" validateRequest="false" pageParserFilterType="Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" asyncTimeout="7">
    <namespaces>
      <remove namespace="System.Web.UI.WebControls.WebParts" />
    </namespaces>
    <tagMapping>
      <add tagType="System.Web.UI.WebControls.SqlDataSource, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" mappedTagType="Microsoft.SharePoint.WebControls.SPSqlDataSource, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
    </tagMapping>
  </pages>
<siteMap defaultProvider="SPSiteMapProvider" enabled="true">

The error that we were getting in the trace logs is similar to below.

Exception Type: System.Web.HttpRequestValidationException  Exception Message: A potentially dangerous Request.Form value was detected from the client (ctl00$PlaceHolderDialogBodySection$ctl04$OriginalEntities="<Entities />").

via Solien Technology

Related posts

• SharePoint Alerts Not Working (5)
• WssRemoveFeatureFromSite + BAT File (0)
• WSS v3 & MOSS 2007 Features (0)
• Unable To Enable Office SharePoint Server Publishing (0)
• Unable To Activate Office SharePoint Server Publishing Infrastructure (0)

So, I am finally posting the solution:

stsadm -o activatefeature -name PublishingResources -url <site>

*Be sure to include the “http://” in the <site>

Hope this helps!

Related posts

• SharePoint Alerts Not Working (5)
• Faulty Feature Tool (0)
• WSS v3 & MOSS 2007 Features (0)
• Unable To Activate Office SharePoint Server Publishing Infrastructure (0)
• Find Checked Out Files (0)

Once I got it installed I ran the SharePoint Products & Technologies Configuration Wizard and received the following error:

Failed to register SharePoint services.

The log pointed to several different registry keys located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\Services.

I deleted everything under that location and it completed successfully.

Related posts

• WssRemoveFeatureFromSite + BAT File (0)
• WSS v3 & MOSS 2007 Features (0)
• Stop Windows SharePoint Services Web Application (0)
• SharePoint Search Services Error (0)
• SharePoint Alerts Not Working (5)

Event Type:      Warning
Event Source:      Windows SharePoint Services 3 Search
Event Category:      Gatherer
Event ID:      2436
Date:            4/11/2009
Time:            11:45:02 PM
User:            N/A
Computer:      <servername>
Description:
The start address <{somesite}> cannot be crawled.

Context: Application ‘Search index file on the search server’, Catalog ‘Search’

Details:
Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content.   (0×80041205)

Apparently, this error was caused by a recent Microsoft Windows Update that was installed that affected the "Loopback Check" in order to make the system more secure.

In order for the SharePoint Search Services to work we needed to add the following registry entry with a REG_DWORD value of 0×00000001 (1):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\DisableLoopbackCheck

Have you ran into this issue or one like it?

Related posts

• Stop Windows SharePoint Services Web Application (0)
• Error Running The Configuration Wizard (0)
• An update conflict has occurred, and you must re-try this action (0)
• WssRemoveFeatureFromSite + BAT File (0)
• WSS v3 & MOSS 2007 Features (0)

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Publishing Provisioning
Event ID:    4965
Date:        5/13/2009
Time:        10:16:31 AM
User:        N/A
Computer:    SERVERNAME
Description:
Event log message was: ‘Failed to provision the scheduling job definitions.  Page scheduling will not succeed.’. Exception was: ‘System.Security.SecurityException: Access denied.
…

To resolve the issue, we took the following steps:

1. Used stsadm to activate the feature:
   1. stsadm -o activatefeature -name PublishingResources -url http://www.example.com
2. Clicked the [Activate] button on the Site Collection Features page.

Related posts

• Unable To Enable Office SharePoint Server Publishing (0)
• SharePoint Alerts Not Working (5)
• Faulty Feature Tool (0)
• Change Central Admin Port (0)
• WssRemoveFeatureFromSite + BAT File (0)