Jan 11

Two very good articles on best practices for MOSS 2007 / WSS 3.0 installation:

MOSS 2007 Installation
http://www.sharepointforum.se/en-US/Wiki/Installation%20MOSS%202007.aspx

WSS 3.0 Installation
http://www.sharepointforum.se/en-US/Wiki/Installation%20WSS%203.0.aspx

Tagged with:
Jan 10

A known issue exists with SharePoint / MOSS 2007 that produces the following error when attempting to delete a master page form the master page gallery:

This item cannot be deleted because it is still referenced by other pages.

 

 

This error might be expected if the master page was still in use, but the error is shown regardless if other pages still reference the master page or not.

A Microsoft Knowledge Base article exists (http://support.microsoft.com/?kbid=926812) which suggests setting the master page to a hidden state, but sometimes that isn’t enough. There are times when it is more than just a clean up issue, often it really is necessary to completely remove the file.

To completely delete the master page, perform the following steps:

  1. Navigate to the Master Page Gallery page from the Site Settings page.
  2. Select ‘New’ | ‘Folder’ from the menu bar.
  3. Create the folder with a temporary name such as DeleteMe.
  4. Open the site with SharePoint Designer and navigate to the ‘_catalogs\masterpage’ folder.
  5. Drag and drop the master page to delete into the temporary folder created in the above steps.
  6. Close SharePoint Designer.
  7. Return to the Master Page Gallery and delete the temporary folder.
Tagged with:
Jan 10

Attempting to open a SharePoint document library in Windows Explorer view by choosing  ‘Actions’ | ‘Open with Windows Explorer’ on a Windows Server 2008 machine generates the following error:

Your client does not support opening this list with Windows Explorer.

 

This is because the ‘Web Client’ service is required, but not installed on Windows Server 2008 by default. The service can be installed as a part of the ‘Desktop Experience’ Windows feature. To install the ‘Desktop Experience’ Windows feature perform the following steps:

  1. Open ‘Server Manager’ from Administrator Tools.
  2. Highlight the ‘Features’ node under Server Manager.
  3. Click the ‘Add Features’ link on the right-hand side of the screen.
  4. Check ‘Desktop Experience’.
  5. Click ‘Next’.
  6. Click ‘Install’.
  7. You will be prompted to restart the server.

 

Thank you to Tihomir Ignatov for his post on this error.

Tagged with:
Dec 04

While working with Visual Studio 2008 / VseWSS projects I occasionally see the following COM exception preventing the VS project from packaging or deploying to SharePoint:

Error: System.Runtime.InteropServices.COMException
System.Runtime.InteropServices.COMException (0×80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.

It turns out, at least in my experience, that this is caused by an error within the manifest.xml file which typically is due to a renamed file or a change in the project’s directory structure.

To resolve:

  1. Manually edit the manifest.xml correcting any errors and save.
  2. Close Visual Studio 2008 and then re-open the project.

The VseWSS project should now package/ deploy without error.

Tagged with:
Nov 30

On a fresh install of Windows Server 2008, MOSS 2007, Visual Studio 2008, and the Visual Studio Extensions for Windows SharePoint Services I received the following error when trying to deploy or package a solution with VseWSS:

The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: ‘<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

Apparently the VseWSS CTP 1.3 uses the WCF in the deployment process and requires the Windows Server 2008 WCF HTTP Activation feature to be activated. To activate the WCF feature in Windows Server 2008 use the following steps:

  1. Open ‘Server Manager’ from Administrator Tools.
  2. Highlight the ‘Features’ node under Server Manager.
  3. Click the ‘Add Features link on the right-hand side of the screen.
  4. Expand the ‘.NET Framework 3.0 Features’ node.
  5. Expand the ‘WCF Activation’ node.
  6. Check ‘HTTP Activation’ (required). Optionally you mat wish to check the ‘Non-HTTP Activation’ feature if you will be using WCF projects that utilize this, but it is not required for the VseWSS to work.
  7. Click Next to install.
Tagged with:
Nov 29

I have noticed the following error a few times when activating the MOSS Publishing Infrastructure feature on a newly created site collection:

Failed to activate feature ‘PublishingPrerequisites’ (ID: a392da98-270b-4e85-9769-04c0fde267aa) at scope ‘http://[url]‘.

Typically opening a command prompt (as administrator) and running an ‘iisreset /noforce’ will resolve this error.

Tagged with:
preload preload preload