MOSS Installation Pitfalls
The Office SharePoint Server 2007 administrators now have three years of experience in installing MOSS in various environments. I thought to gather here all the common errors faced in MOSS installation process. Most of these are now luckily documented in MS KB articles. This was not case a year or two ago.
- Our favourite: You cannot browse to an SSL-secured Office SharePoint Server 2007 site or to the Search Settings page for a Shared Services Provider (KB962928). This appears especially in larger farms if you have .NET 3.5 SP1 installed before MOSS installation. During September 2008 we were among the first to discover this in co-operation with Microsoft, and the KB article was published couple months later.
- This one happens every time: Event ID error messages 10016 and 10017 are logged in the System log after you install Windows SharePoint Services 3.0 (KB920783). Now also with the 2008 Server extra flavor.
- Event ID 8 is logged in the Application log (KB317541).
- Error when you try to edit the content source schedule in Microsoft Office SharePoint Server 2007: “Access is denied” (KB926959).
- You may be unable to manage IIS by using Server Manager if two threads access IIS at the same time (KB946517).
- Error message when you try to open a help window from a SharePoint Server 2007 site or from a Windows SharePoint Services 3.0 site: “Cannot display help” (KB939313).
- You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version (KB896861).
- Search service creates VSS errors in system log, similar to this DHCP issue. Happens only with Windows Server 2008 R2.
- Error 7888: Could not find stored procedure ‘proc_ar_BumpCacheInvalidationCounter’
- The nastiest installation bug must be the Service Pack 2 expiration date issue. Although the faulty SP2 version was only available for some weeks, it must have been used numerous times. The license type was converted into a trial license without notifying the administrator, so you could only become notified of the issue by accident. And if you have not followed SharePoint-related news and installed the fix, you will get some nasty errors 180 days after the service pack upgrade.
As SharePoint 2010 matures and we get more installation experiences, we will post in this blog the installation bugs faced with SP2010.
Popularity: 1% [?]