Every once in a while a WSS installation won't search. When searching in WSS we get the standard nothing was found. In the Application Event Viewer we see the following

Level: Warning
Source: Windows SharePoint Services 3 Search
Event ID: 2436
Task Category: Gatherer

Event Data:
The start address <sts3://dhq/contentdbid={20ef7238-e02f-4938-94cb-791b0581042c}> 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. (0x80041205)

So after a lot of searching and searching online, I came across article http://support.microsoft.com/kb/896861. I have found that the second method fixes it, the first doesn't do much for me.

Enjoy!

When using the XML web part in SharePoint, I received the error:

The XSL specified by the XSL property or XSL Link property is not valid, or the XSL file cannot be accessed. Make sure you have specified a valid XSL style sheet for this Web Part, or if the XSL file is linked that it can be accessed by the server. For assistance, contact your site administrator. More about making XSL files accessible.

I received this error after using SharePoint Designer to update the default.aspx page by adding a dataview. The obvious is that there is invalid informtion in my XSL, but it was working fine before I made the updates to the page.

After further examination, it appears that the XSL editor has extra spaces at the top of the page. The <?xml version="1.0" encoding="utf-8"?> should be the very first item in the page, first line first column. It wasn't It was on line two and column 20 or so. So I deleted the extra line and spaces and it worked again.

For some reason SharePoint Designer thought it necessary to mess with my already existing and functioning code. 

Hope this helps!

So, I've been using WSPBuilder to create my solutions, such a great add on for Visual Studio. I created a WSPBuilder Project and loaded up some app pages and web parts. I then realized I needed a workflow. So I right clicked on the project, selected Add then New Item. I selected Sequential Workflow Feature and clicked Add.

It added all of the wonder files and references itself. I did have to combine the new feature.xml file with my existing so this would install under a single feature.

When I went to open the workflow, the page errored:

The service 'System.Workflow.ComponentModel.Compiler.ITypeProvider' must be installed for this operation to succeed.  Please ensure that this service is available.

The reference to the DLL is in the project and is a good link. After searching the web for about 2 minutes I came across the following link:

http://www.codeplex.com/wspbuilder/Thread/View.aspx?ThreadId=27794

The GUIDs they were referencing didn't work, it broke my project. But I followed their lead. I created a new temporary WSPBuilder Project with Workflow project. I edited the .csproj file for the new project and copied the contents of the following tag, and then updated my original project csproj file.

<project>
  <PropertyGroup>
    <ProjectTypeGuids>{14822709-B5A1-4724-98CA-57A101D1B079};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>

It works like a charm! I can edit and update my workflow with ease.