SharePoint Error: Property doesnt exist or is used in a manner inconsistent with schema settings.

29 02 2012

We were recently uncovered an error when we passed a URL with a number of parameters to the SharePoint search results page and the users IE browser returned the following error:

“Property doesn’t exist or is used in a manner inconsistent with schema settings.”

The error wasn’t returned by chrome.

The resolution we found was that the browser was set to US language so it couldn’t interpret the dates we had passed to the page.

A quick resolution to a strange error.



PDF iFilter SharePoint

21 06 2009

No doubt within about 5 minutes of using WSS or MOSS your users will want to be able to search the contents of a pdf, if its not a prequisite. This post will show you how.

How to add the PDF iFilter to SharePoint 2007.

Before we start, this post shows you how to add the PDF icon to SharePoint which might be of interest.

You will need:

Adobe PDF IFilter 6.0
Note: After this iFiliter is packaged with Adobe Reader
Admin rights on your indexing server.


  1. Copy the Adobe PDF iFilter 6.0 to your SharePoint indexing server.
  2. Run the PDF iFilter 6.0 on the server.
  3. Enable the pdf extension. Go to Central Administration > SharedServices > Search Settings > File Types >Add File Type.
  4. Enter ‘pdf’ as a file extension and save.
  5. Perform a full crawl to index you PDF documents.

For troubleshooting check the Microsoft KB for WSS issues.
Ive never had an issue with this on 32bit platforms, usually i forget to enable the the extension if anything doh.

For 64 bit you will have to choose between Adobe 9.0 (free bundled with Adobe reader) and Foxit (paying). Check out this blog post for more details:

For instructions on how to install Adobe 9.0 64 bit check here

Other iFilters to consider:

This post shows you how to add the PDF icon to SharePoint the same steps apply for other icons.

Trouble Shooting

Use Citeknet  iFilter explorer to help with debugging see which extensions are registered to the correct dlls.

Check your event viewer:

DCOM error  event id 10016
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1}

This error means one of your app pools doesnt have the correct permissions. Navigate to:
Start > Administration Tools > component Services > Computer > My Computer > DCOM Config.

Locate IIS WAMREGT Admin Service – Propertises > Customize > Edit.

Add/Edit the App Pool (User) account that caused the error – Allow Local Activation.

If this post helped you share it with others.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

SharePoint for Dummies

18 06 2009

SharePoint for Dummies from the for Dummies series offers some great tips on getting started with SharePoint covering all the topics you need.

From the Back Cover
Match SharePoint to your specific business needs.

The fun and easy way® to deploy SharePoint in your business today!

Are you stymied by SharePoint? This plain–English guide offers simple instructions and focused coverage of this powerful tool, giving you practical solutions to real–world SharePoint challenges. You′ll install SharePoint, create sites and grant access, manage data and business processes, use sites to improve employee relations and marketing, put interactive reports and forms on a portal, and much more!

  • Set up a SharePoint portal
  • Manage portal content and Office documents
  • Integrate Office 2007 with SharePoint
  • Use SharePoint to collaborate
  • Create personalized sites
  • Monitor and back up your portal

Table of Contents


Part I: Setting Up SharePoint.

Chapter 1: Getting to Know SharePoint.
Chapter 2: Installing SharePoint.
Chapter 3: Creating the Site Hierarchy.

Part II: Exploring SharePoint’s Building Blocks.

Chapter 4: Introducing Sites and Site Content.
Chapter 5: Navigating SharePoint.
Chapter 6: Granting Access to SharePoint.
Chapter 7: Managing Data with SharePoint.
Chapter 8: Managing Business Processes with SharePoint.

Part III: Improving Information Worker Collaboration and Productivity.

Chapter 9: Using SharePoint for Collaboration.
Chapter 10: Communicating with SharePoint.
Chapter 11: Using Portal Sites.
Chapter 12: Configuring Profiles and My Sites.
Chapter 13: Personalizing Sites.
Chapter 14: Searching the Enterprise.

Part IV: Enterprise Applications for SharePoint.

Chapter 15: Exploring Document and Records Management.
Chapter 16: Publishing Web Content.
Chapter 17: Providing Access to Business Intelligence.

Part V: Administering SharePoint.

Chapter 18: Administering and Monitoring SharePoint.
Chapter 19: Backing Up the Server.

Part VI: The Part of Tens.

Chapter 20: Ten SharePoint Resources Worth Checking Out.
Chapter 21: Ten Positive Outcomes from Implementing SharePoint.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

How to add SharePoint PDF Icon

18 06 2009

How to add the Adobe PDF icon to SharePoint MOSS or WSS.

After implementation someone will ask if you can add the Adobe PDF Icon to SharePoint MOSS or WSS to display next to pdf documents. To achieve this follow the instructions below.

Once you have setup the pdf icon try adding the PDF iFilter to Sharepoint.



  1. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images
  2. Copy in the Adobe PDF Icon PDF icon. “pdficon.gif“.
  3. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\xml
  4. Locate the Docicon.xml file open with an xml editor.
  5. Within the ByExtension tag add a new Mapping tag in alphabetical order with the following properties.
    <Mapping Key="pdf" Value="pdficon.gif" />
  6. Save the file. The Value needs to be the same as the icon you saved in images. Your file should look something like this.

    Extract from Docicon.xml showing pdf icon properties

    Extract from Docicon.xml showing pdf icon properties

  7. Restart IIS.
  8. Check a document library you should now see a pdf icon next to a pdf document.
    No icon check the steps again and look out for spelling mistakes…

Once you have setup the pdf icon try adding the PDF iFilter to Sharepoint.

If this post helped you share it with others.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

Become a SharePoint Guru overnight*

29 01 2009

* Ok maybe not overnight, but the below will give you access to the best content the web has to offer! The rest is up to you!

A lot of people are aware of all the web2.0 sites, most of you are users, but aren’t  aware of how you can harness the power of their content.

RSS Social Aggregators

RSS Social Feeds

Just a few well placed searches grab the RSS and you have cornered the web. Why stop there? Share this with your co-workers in an RSS viewer within your SharePoint Teams Site!

Check below for sites by category you might be already a user sitting on a goldmine of information and not know it!

Web2.0 sites categorised

Web2.0 sites categorised

See Getting ahead in your niche with RSS and social media for more indepth description.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

High Level Sharepoint Deployment

19 12 2008

Brief Summary

This article is High Level in nature and is work in progress. It aims to cover some key strategic areas when assessing the customisations an enterprise implementation of the SharePoint Framework needs to support. This solution has been tailored to our requirements and the majority of areas have been taken into consideration. Code in the 32-bit staging environment will be recompiled to 64-bit for live. any feedback would be appreciated.

Deployment Context

Highlights the differing areas of customisation within the SharePoint framework we must support and identify clear policies for deployment.

Deployment Context Structured

Highlights the core island workspaces required to manage structured development through to live deployment.


As SharePoint is so diverse and will eventually be far reaching as a dependent tool within the business supporting live business activities, we are all too aware any configuration or customisation of the framework can have the potential to affect business continuity.

We are faced with difficult issues when assessing the best way to apply customisation and configuration. To handle this difficulty we have broken the core issues down and captured our strategy in the following diagrams.

Deployment Context

As deployment is so flexible and wide spread, we have devised a deployment context method of separating out the differing areas of deployment that require supporting.

sharepoint deployment context

Click for larger image. Highlights the separation of concerns with regards to deployment within the SharePoint framework. Blue stripes represent structured and controlled deployment management resolving around software development. Orange represents a semi-structured and semi-controlled deployment scenario. Red represents the live changes that can occur without formally being subjected to a strict testing / UAT stage.

Deployment Context: Structured

This deployment context is all about structuring and managing the customisation of SharePoint through source code and low level configuration changes. Below is a diagram depicting the current structured deployment strategy.

sharepoint deployment strategy

Click for larger image. Depicts the stages of structured deployment process and stages involved. Also depicts the people and skills required at each stage during the deployment cycle.

Deployment Context: Semi-Structured

This deployment context is about releasing power to the people within the business to create, manage and deploy high level customisations and electronic forms. Semi-Structured represents a requirement for the SharePoint technical architect to be factored into the work to gain an appreciation of what is been done and highlight any reliance or problems. The extent of the technical input will differ depending on the solution in question.

For instance, a simple form will just require an acknowledgment by the technical architect and maybe an ITIL configuration record. A complex form may require help and significant input from the architect as it may require some low level functional support or reliance on some SharePoint framework functionality.

Either way, the technical architect assumes responsibility for supporting the solution.

Deployment Context: Un-Structured

This deployment context is concerned with high level live changes to SharePoint. Although the technical architect should be aware of any changes, the onus is on a trained user to manage the solution.

Content Management is a sound example of acceptable live configuration changes through delegated responsibility.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine