Use the following SQL to find the sites that have missing assemblies that are found in the Review Problems and Solutions Central Admin page:

SELECT w.FullURL, w.Author, w.Title,w.[Description]
  FROM [dbo].[EventReceivers] with (nolock)
  inner join dbo.Webs w with (nolock) on WebId = w.Id
  where [Assembly] like '%<MISSING ASSEMBLY NAME>%'

Below is the SQL to find missing web parts so that you can navigate to the web part page and delete them:

USE <CONTENT DATABASE>
SELECT DISTINCT W.FullURL as WebURL, D.DirName,
     D.LeafName, tp_ID As WebPartSK ,WP.tp_WebPartTypeId
FROM dbo.Docs D WITH (nolock)
INNER JOIN dbo.Webs W WITH (nolock) ON D.WebID = W.Id
INNER JOIN dbo.WebParts WP WITH (nolock) ON D.Id = WP.tp_PageUrlID
WHERE WP.tp_WebPartTypeId in (
     '<MISSING WEB PART GUID>',
     '<MISSING WEB PART GUID>'
)
ORDER BY DirName, LeafName

Below is the SQL to find where the missing installation file is used:

select * from AllDocs with (nolock)
    where SetupPath like 'themesCardinal%'
    order by LeafName

.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

After you find out where the file is used, you can access the site using Sharepoint Designer and delete the reference.

We were having trouble adding a user to a site collection.  Every time we hit the search button or clicked the check userid button the system would just sit there and spin. I added the following section of the web.config to resolve the issue.

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="").

via Solien Technology

Whenever I create a new MOSS site this is going to use the Office SharePoint Server Publishing feature I get an “Access Denied” error when I try enable it.

So, I am finally posting the solution:
[code lang="dos"]stsadm -o activatefeature -name PublishingResources -url [/code]
*Be sure to include the “http://” in the <site>

Hope this helps!

I installed a Windows SharePoint Services (WSS) Web Front End (WFE) onto an external server to be used for the External Collaboration Tool-Kit.

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_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions12.0WSSServices.

I deleted everything under that location and it completed successfully.

One day, we noticed that our search was not working.   Well really, one of the applications managers noticed that it wasn’t working.  Anyway, we found the following errors in the event viewer on our SharePoint 2007 Server:

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_MACHINESYSTEMCurrentControlSetControlLsaDisableLoopbackCheck

Have you ran into this issue or one like it?

When trying to enable the Office SharePoint Server Publishing Infrastructure feature we were getting an “Access Denied” error.  The error in the application event log was:

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. [code lang="dos"]stsadm -o activatefeature -name PublishingResources -url http://www.example.com[/code]
2. Clicked the [Activate] button on the Site Collection Features page.