Application Template – Feature is not installed in this farm

You may see this type of error if you are creating a site using one of Microsoft’s application templates as the template for your new site. For example, trying to install the HelpDesk site, you would see this error: Feature ’75a0fea7-12fe-4cad-a1b2-525fa776c07e’ is not installed in this farm Oops!  First, check in Central Admin > Operations…


Failure trying to sync web application – A duplicate site ID

You may receive this type of error after detaching and reattaching content databases in SharePoint. In my specific case, I had renamed a database and then reattached it to a web application using the addcontentdb command.  Apparently synchronization information gets confused a long the way.   Error Example: Failure trying to synch web application d07de01b-1544-4058-ac17-8671865964d2,…


IIS 6.0 No Sites or ‘the path specified cannot be used at this time’

If your IIS Manager on a SharePoint server is failing to load the websites for the server, your SharePoint Timer Service may be trying to access IIS 6.0 at the same time (multiple threads). Microsoft released a hotfix back in January to resolve this issue. Unable to manage IIS: http://support.microsoft.com/?id=946517


Login Prompt When Opening documents in SharePoint

This is something that will happen to a lot of users when using MOSS and IE7.  You can search for the issue and find many possible causes and resolutions.  Typically, the problem can be resolved by adding the site to your Local Intranet sites in IE’s options.  Below are the directions to do so.  …


Attaching this database requires upgrade

Recently I was onsite with a client trying to recover their WSS 3.0 environment that they completely lost (post coming on that later).  During the recovery process I needed to add a content database back to their installation but received the following error in central administration:  Attaching this database requires upgrade, which could time out…


WSS 2.0 – Who deleted the site?

When I was recently onsite with a client, someone went and deleted an important site (WSS 2.0)… Oops! Found the individual responsible by looking through the IIS logs, and tracking down the user who visited the page:   deleteweb.aspx – Dan Lewis