Microsoft SharePoint Server 2010 encountered an error during setup. One or more required office components failed to complete successfully.

I encountered this error today after trying to reinstall SharePoint 2010 on my Windows 7 Enterprise 64 bit machine.  It failed near the end of the binary installation.  From the log file, I found that the “One or more required office components” failed during the setup was the installation of the SQL Server Express database for SharePoint.  And the root cause of the problem was in the Windows Registry, which is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations. 

SharePoint 2010 Certified!

Praise the Lord!

Last weekend I got some pleasant news from Microsoft Certification Program Team.  I passed two  Microsoft SharePoint 2010 beta exams taken on last May 25, which are Exam 70-667 TS: Microsoft SharePoint 2010, Configuring and Exam 70-668 PRO: Microsoft SharePoint 2010, Administrator.  This entitles me for both MCTS - SharePoint 2010, Configuration and MCITP - SharePoint Administrator 2010 credentials.

On top of that, I also passed Exam 70-576 PRO: Designing and Developing Microsoft SharePoint 2010 Applications beta exam on June 9, counted toward MCPD: SharePoint Developer 2010 credential. One more exam to go is Exam 70-573 TS: Microsoft SharePoint 2010, Application Development

I am very glad to be again among the very first group of people worldwide achieving this credential.  It's similiar to my SharePoint 2007 and .NET certification achievements many years back.

AvePoint Content Shield: A Superior Content Filtering Solution for SharePoint 2007

One of the requirements that we have to deliver for our client is to implement a content filtering solution for our SharePoint 2007 farm with the following core capabilities:

• The solution can perform real time scanning of all content prior to upload for instance(s) of forbidden keyword/phrases and file types, and can block or replace the violating content accordingly
• The solution can perform scheduled scanning of existing content which have been uploaded to the sites for instance(s) of forbidden keyword/phrases and file types, and can remove the violating content accordingly
• Each site collection can has its own filtering dictionary, containing the list of  forbidden keyword/phrases and file types, and its own filtering profile, containing the list of actions to be taken for violating content based on scanning type, such as block, delete, remove content with error message, send email to content creator or modifier, etc.  This is actually the main requirement since each site collection can be owned by different agencies and each agency has its own content policy.  For example, some agencies might allow .avi content in their sites, while other agencies might prohibit them
• The content filtering can be performed on lists, list attachments, and document libraries for items where their iFilters are installed, including zipped items
• The solution provides audit trails for all the actions taken, such as block, delete, etc.
• The solution user interface is integrated with SharePoint Central Administration

Replica is inconsistent error in Data Protection Manager 2007

I encountered this replica is inconsistent error for protection status of SharePoint Farm Configuration Database under Protection tab inside DPM 2007 Administrator Console.  The suggestion given by DPM admin console to solve the error is by performing consistency check on the farm configuration database.  However after running the consistency check for several times, it didn't fix the error and consequently all protection activities, like recovery point creation for the SharePoint farm also failed.

After some troubleshooting,  I found out that the root cause of this issue was due to the addition of a new content database to store a new site collection in the SharePoint farm. This made the replica of the data source (content databases) are inconsistent with the data source (content databases) on the protected farm.

Failed to create the configuration database - User cannot be found

I got the above error message when running the SharePoint 2010 Products Configuration Wizard after installing the binaries on my Windows 7 64-bit machine.  Then from the event log, it was Event ID 104 as below:

Failed to create the configuration database.

An exception of type Microsoft.SharePoint.SPException was thrown. Additional exception information: User cannot be found.

Running Windows Server 2008 R2 on Windows 7 with Boot to VHD

With the MSDN release of SharePoint 2010 RTM, I am very excited to start installing it on my notebook,  running on Windows 7 64 bit with 4GB RAM.  Then there were two options that I considered.  First option was to install SharePoint 2010 directly on my Windows 7 64 bit notebook and the second option was to install it on my Windows Server 2008 R2 VHD, and then use the boot to VHD feature of Windows 7.  Both options seems good.  However for portability reason I chose the second option.  With the second option it would be very easy and quick if I need to change my notebook and it has minimal performance impact.  Microsoft estimates that Windows Server 2008 bR2 take a performance hit of only about 2% when running from a VHD.  Furthermore I can also play around with all of the Windows Server 2008 features, such Active Directory.

Deploying Data Protection Manager 2007 (DPM) for SharePoint 2007 Protection and Recovery

In order to meet our Recovery Time Objective (RTO) and Recovery Point Objective (RPO) goals, we have decided to deploy and use Microsoft System Center Data Protection Manager 2007 (DPM) for our SharePoint farm, rather than using third party tools or manual content database restore approach which needs a longer restore time.  From that experiences, below is the summary of steps that we have performed in order to set it up for protecting our farm, which consists of web front-end, index, and database servers.

1. Service account preparation
- DPM administrator service account, which has local administrator privilege on the DPM Server
- DPM agent service account, which has local administrator privilege on the machines to be protected, which are the web front-end, index, and database servers
- SQL server service account

SharePoint Foundation 2010 and SharePoint Designer 2010 are available as public download

SharePoint Foundation 2010 download
Supported Operating Systems: Windows 7 Enterprise; Windows 7 Professional; Windows 7 Ultimate; Windows Server 2008 R2; Windows Server 2008 Service Pack 2; Windows Vista Service Pack 2

SharePoint Designer 2010 64 bit download
Supported Operating Systems: Windows 7; Windows Server 2003 R2 x64 editions; Windows Server 2008; Windows Server 2008 R2; Windows Vista Service Pack 1

SharePoint Designer 2010 32 bit download
Supported Operating Systems: Windows 7; Windows Server 2003 R2 (32-Bit x86); Windows Server 2003 R2 x64 editions; Windows Server 2008; Windows Server 2008 R2; Windows Vista Service Pack 1; Windows XP Service Pack 3

Enabling Information Rights Management in SharePoint 2007 by Integrating with AD RMS

Recently we have been asked to enable Information Rights Management (IRM) capability in our SharePoint infrastructure, which consists of three web front-end servers, one excel calculation server, one index server, and two clustered database servers.  All servers are running on Windows Server 2008 64 bit environment.
The original plan is to prepare our SharePoint infrastructure to store IRM-protected documents, where the protection capabilities are embedded in the document.  However, it will make these protected documents unsearchable since they cannot be tagged or indexed while the document contents are encrypted.  This is no longer the case with AD RMS and SharePoint 2007 since the IRM policies are only applied when the documents are downloaded and they are stored unencrypted in the libraries, hence making them indexable and later searchable.

Configuring SQL Server 2005 Log Shipping for SharePoint 2007 Disaster Recovery Farm

As part of the architecture design to provide 99.5% availability for our SharePoint infrastructure, which is equivalent to 3.5 hours downtime per month, we plan for the redundancy and failover between two server farms.  The primary farm is located in a main data centre and the secondary farm is located in a Disaster Recovery centre in the same city.  Both farms have been setup separately with their own configuration database and Central Administration content database.  All customizations and patches have been deployed on both farms as well.  

To support the disaster recovery scenario, the primary farm's content databases are configured with log shipping to the failover farm in the disaster recovery centre.  Log shipping essentially involves copying the content database backup and subsequent transaction log backups from the primary farm's database server and restoring the content database and transaction log backups on the secondary farm's database server. The content database and transaction logs are restored on the secondary farm in standby or no-recovery mode, which allows subsequent transaction logs to be backed up on the primary and shipped or copied to the secondary server and applied there.

SharePoint 2007 Farm Migration

As part of the company acquisition and platform enhancement, recently we have been tasked to perform a migration from an old SharePoint 2007 farm (running on old company domain) to a new SharePoint 2007 farm (running on new company domain).  The old SharePoint farm has one root site collection with fourteen sites, stored in one big content database.  On the new SharePoint farm, these fourteen sites will be created as site collections with their own content databases in order to ensure enhanced operation procedures.  The new farm topology consists of one web front-end server, one index server and one database server.  There is also a recovery farm in a standalone server and a DPM 2007 server for backup and restore purpose.  The migration was performed by using the stsadm command line tool.

The steps taken during the preparation of the migration process are below:
1. Setup and configure the new SharePoint farm
2. Deploy non out of the box site templates if any (e.g. F40 application templates) in the new farm
3. Create staging web application in the new farm
4. Create destination web application in the new farm

Error in the Site Data Web Service - No results returned from Search

I found this error message in the Crawl Log of Search Administration settings in Central Administration site after getting a complaint from the user that they cannot find any results when performing a search on a particular site collection.  It happened after we performed a site migration from one SharePoint 2007 farm to another SharePoint 2007 farm running on two different domains with trust relationship.

The root cause of this error is corrupted SIDs in the UserInfo table of the site collection, which returns no search results.  And the steps to solve the issue are:

Welcome to My SharePoint Blog

I would like to dedicate this blog as a diary of the exciting and challenging things that I have experienced and encountered while implementing SharePoint projects for my clients. It has been more than four years since I delivered the first SharePoint 2007 project in 2006. A lot of challenging issues have been found and ironed out during this journey. With the release of SharePoint 2010, there will be much more exciting things ahead.

Welcome to this blog!