Archive for February, 2009

Search Errors – Error Microsoft Windows SharePoint Services Protocol Handler

February 20, 2009

In order to clear this error that you may see in your error log in Central Administration, stop the Search Service.

This will detatch the indexer from the farm.

Start it up again and assign the correct server as the indexer.

Go to Shared Services and make sure you edit it so that you choose the indexer.

Go to your search settings, reset crawled content and re-crawl.

After I did that, got another horrible error: Element not found. (Exception from HRESULT: 0x8002802B (TYPE_E_ELEMENTNOTFOUND)) (ComInterop Exception).

Yes, nasty. I re-crawled content from the server directly and it is nicely crawling content again.

Documents locked when editing a document you opened

February 18, 2009

I’ve come across a problem that SharePoint has. When you check out and edit a document, when you get to the check in stage, an error prompts you that “the filename http://blahblahblah.com/document/yourdocument.docx” is locked for editing by another user.

According to KB8997089, the fix is to wait 10 minutes and to edit the file using the “Edit document”. This issue is either caused by the MSOCache folder or the client Office lock out. See Paul Liebrand’s blog for more details.

Displaying Fields in Content Query WebParts

February 10, 2009

Following my earlier post today, I explained how you can customise your CQWP.

I had a series of articles which I wanted to see the article date and who the publishing contact person was, not the author as the author could be an admin person. So how did I get this done, with patience and lots of Googling!

First, create the query and export to your desktop, open with notepad and amend the property CommonViewFields. For my own use, I needed the article date, not modified and the contact name. I had originally set the contact name as text, that is wrong, it should be a LookUp as contact names are entered using a people picker in the original article page.

<property name=”CommonViewFields” type=”string”>ArticleStartDate,DateTime;PublishingContact,Lookup</property>

Next step is to amend the itemstyle.xsl.

Add   xmlns:ddwrt=”http://schemas.microsoft.com/WebParts/v2/DataView/runtime” to the header so that the date is passed through.

I copied the first template and renamed the name (as per Microsoft blog).

First, define the variable for the PublishingContent element.

<xsl:variable name=”PublishingContact”>
       <xsl:call-template name=”OuterTemplate.GetGroupName”>
           <xsl:with-param name=”GroupName” select=”@PublishingContact”/>
           <xsl:with-param name=”GroupType” select=”‘PublishingContact'”/>
       </xsl:call-template>
</xsl:variable>

In the first   <div class=”description”>, you have to declare what you want the content web part to display. The script is:

<xsl:value-of select=”ddwrt:FormatDateTime(string(@ArticleStartDate) ,1033 ,’d/M/yyyy’)” />
Created by – <xsl:value-of select=”$PublishingContact”>
</xsl:value-of>

Make sure you check in the file as a minor and preview your changes on your web page. . all should be fine.

Hope this helps someone!!

Content Query Web Part Date Format

February 10, 2009

Firstly, follow Heather Solomon’s blog on a great how to customise the content query web part. Essentially, you need to allow the webpart to expose itself to whatever information you need it to display.

I had a roll up of information, which ideally I needed the article date to display on the page.

Links: http://www.heathersolomon.com/blog/articles/customitemstyle.aspx

Follow on to the MSDN blog which is found within the above link (http://blogs.msdn.com/ecm/archive/2006/10/25/configuring-and-customizing-the-content-query-web-part.aspx)

I managed to get what I wanted… but in an American date and time format, which was a big no no for me.

Fortunately, there was a post on the SharePoint User Group forum for UK members.

All you need to do is edit itemstyle.xsl to include xmlns:ddwrt=”http://schemas.microsoft.com/WebParts/v2/DataView/runtime  as a reference on the top header and amend the description tag to <xsl:value-of select=”ddwrt:FormatDateTime(string(@Modified) ,1033 ,’d/M/yyyy h:mm tt’) />

You can remove the time, amend the date as you wish.

If you do unfortuantly break your SharePoint site with any mistakes, not to worry, reset to the site definition using SharePoint Designer.

Any questions let me know!

‘An error occurred processing the data view. The XslText property is empty’

February 9, 2009

I had the above error in my beautifully styled out data view, the problem was that I had accidently inserted another empty data view, once removed, the page was completly fine.

Lesson learned: Don’t click too many times when inserting data views 🙂

Illegal Filenames in SharePoint

February 6, 2009

Whilst migrating documents from a network drive manually, I noticed that SharePoint was not happy with certain file names. Thought I’d add this in for future reference:

: \ / : * ? ” < > | # { } % ~ &

I use Bulk Rename Utility to rename files – Why do this manually? I like to do it this way so that I have control over what is migrated over – useless information certainly is not useful in a SharePoint system!

SharePoint User Group Meet Up – 11/12 March 2008

February 4, 2009

This is pretty exciting – there’s a SharePoint User Group meeting in March at the London Olympia.

http://www.communitiescollaborating.org/index.html

See you there!

How to save a site as a template in MOSS 2007

February 3, 2009

Ever wondered why you can’t save a publishing site as a template? Yup, I don’t either. You’ve probably designed a really great site using the publishing template, go to Site Actions, excitedly go to modify all site settings and you start… looking for save site as a template.

It’s a great feature in WSS 3.0… but it’s not readily available in MOSS 2007 AKA SharePoint 2007.

Never fear, help is here.

To save a publishing site as a template, go to the URL of your site, e.g http://www.acme.com/ and… add in _layouts/savetmpl.aspx

This will bring up a form which will ask for the name of the file you want to save, which incidently will create a .stp file, enter in name and description – I strongly suggest that you use this as it can be confusing to look for your site once you hit OK.

If you have created content in your site, tick “include content”, to be specific;

“Include content in your template if you want new Web sites created from this template to include the contents of all lists and document libraries in this Web site. Some customizations, such as custom workflows, are present in the template only if you choose to include content. Including content can increase the size of your template”.

Item security settings are not saved in a template, so make sure the publishing site you are creating doesn’t have anything specific to a document. General security settings are saved, e.g groups of people who have access to libraries etc.

Hit OK and your template has been saved.

When you create a new site, go to custom at the bottom of the page and you’ll see your site there.

Easy 🙂