SharePoint 2010 DB Migration – database is up to date, but some sites are not completely upgraded

I was migration several content databases to SharePoint 2010 using Powershell (Mount-SPContentDatabase command) and after the migration I went to Central Admin to check the databases status.

There I could see this message on one of the databases:
Database is up to date, but some sites are not completely upgraded.

Searching on Google for the solution I found several articles on using STSADM instead of the Powershell command. The article “SharePoint 2010 Content Database Migration, Re-Deploy Results in Foreign Key Constraint Error” is one of the examples I found with the STSADM recommendation. With further research, I also found some articles recommending to run the Upgrade-SPContentDatabase cmdlet to upgrade the content DB. The article SharePoint Upgrade has a good example of it and explains how to get the content DB GUID using the Get-SPContentDatabase cmdlet. I also tried this and even though the cmdlet returned sucessfully the database continued with the same status.

Finally, checking the Mount-SPContentDatabase Errors on 2nd and subsequent attempts of same database article I found the awesome recommendation on closing the Powershell window and open it again. I did it and finally I could run the migration successfully. The article didn’t explain why it happens but it says it is a known issue and happens after you leave the Powershell window open for a long time. I hope Microsoft works on solving this kind of issues because they can easily take a couple of days from our migration schedules.

See you,



Useful Features for SharePoint 2010 Central Admin

I’ve found a few useful features for Central Admin:

Developer Dashboard configuration feature

It allows you to configure the developer dashboard using Central Admin instead of running Powershell or STSADM commands, which can be very helpful for administrator with no access to the servers console.

Central Admin Resource Links Generator

It create links on the Resource Links for all service applications and also allow you to create your own links if you
configure the feature.

If you want to customize your Central Admin and add links to its sections you will find this resource useful. It show you the location and group IDs you should use to add your own links to the Central Admin sections.

See you,


SharePoint 2007 Service Pack 3 Available

The SP 3 for Windows SharePoint Services (WSS) 3.0 and SharePoint Server (MOSS) 2007 is available at:

WSS Service 3.0 Pack 3

MOSS 2007 Service Pack 3

Remember: the installation order for SharePoint Server 2007 environments is first install the WSS SP 3 binaries, then install the MOSS SP 3 binaries and then run the SharePoint Configuration Wizard. If you run language pack you have to install the WSS Language packs and the the MOSS language packs.

More instructions on how to update SharePoint 2007 can be found in TechNet or on the SharePoint 2007 Updates Resource Center.

See you,



SharePoint Farm Solution Extractor

When you are migrating SharePoint 2007 to 2010 you might realize that you don’t have a copy of all the solution packages you installed on your farm. If that is your case, the SharePoint Farm Solution Extractor is an awesome tool to help you get the current deployed solution packages on your farm:

You can use it with the following parameters to save all deployed packages to the specified folder:

SharePointFarmSolutionExtractor.exe -extractAll e:\FarmSolutions

A few notes:
-the extractAll parameter is case sensitive.
-the folder must exist before you run the command.

It helped me to get all the solution packages from the 2007 environment to install on the 2010 environment.

Hope this helps you as well.


SharePoint 2010 Installation – Windows Pre-Requisites and Security Hardening

I was installing SharePoint 2010 on some new Windows 2008 R2 severs to create a new farm and I was having several problems installing the required Windows roles and features.

The error message was the same for several features:

<Feature>: Installation failed Error: Attempt to install <Feature> failed with error code 0x80070643. Fatal error during installation The following features were not installed: <Feature>.

I wasn’t finding an actual reason for this error message. After a while I tried to install one feature or role at a time to make sure I was understanding which features were failing. Checking the SharePoint 2010 pre reqs installer logs I was able to find the commands the installer executes:

“C:\Windows\system32\ServerManagerCmd.exe” -inputpath

I was also able to find the XML file with the roles/features list the installer uses.

Here are files if you want to install the Windows Pre Reqs manually:

XML file with required Windows roles and features

Batch file to install Windows roles and features

After a executing this command a few times I found out lots of features were failing every time I ran it but it didn’t help me.

Then I recalled all servers we have go through a security hardening process before they are available on the network. I went to talk to the security guys and we found out they ran the Security Configuration Wizard (SCW) on the servers and it wasn’t allowing new features or roles to be installed on the servers. After changing the SCW template and applying it I was able to finish installing the pre reqs.

Researching a little bit more about this issue I found out the SharePoint 2010 Administration Toolkit comes with several  SCW templates for Windows 2008 servers.

More details on security hardening for SharePoint 2010 and a visual guide on SCW configuration can be found at

See you around this world,


SharePoint Feature Administration and Clean Up Tool

The Feature Administration and Clean Up Tool ( helps you find all the installed features on your farm, web application, site collection and site. It also has the ability to find and remove faulty features from the farm. The author provides versions for SharePoint 2007 and 2010.

It is very useful tool when maintaining SharePoint farms and it was even more useful for me when I started migrating my farm from SharePoint 2007 to 2010. I used it to double check the features on the SharePoint farm and remove the faulty ones (yes, be sure you take a look at faulty features, you might not know but it can be there).

See you,


How to clear a FAST Collection

I’ve struggled a lot lots of times when I needed to clear a collection on FAST ESP + Impulse because the most common commands available on the documentation for this task do not always work.
I’ve used several of them:

  • collection-admin –m clearcollection –n <collection name>
  • indexeradmin –a cleancollection <collectionname>

They seemed to work but when I checked the collection detailed information I could yet see the documents there and I could also see the documents on the FAST Impulse Search page.

The only process to clear a collection which always worked is:

  • Generate a list of all documents internal ids on the target collection and save it to a file.
    •  indexerinfo reportcontents <collection name> > documents.txt
    • It will save the list internal ids on the documents.txt file.
  • Run a command to delete all documents list on the file you generated on the previous step.
    • indexeradmin rdocs file.txt <collection name> <execution number>
    • This command will get all internal ids from the documents.txt and send to the indexer admin to delete. The execution number normally will be 1 but if you need to send more than 4000 documents to be deleted you might need to run these commands more than one time, increasing the execution number. The indexeradmin rdocs command can only process 4000 documents at a time.
It might take a little bit to FAST to delete all the documents but it will work.
You can check the progress by going to the collection detailed information page on FAST Admin or running the command to show the doc count for a collection:
indexerinfo -a doccount <collectionname>
See you around this world,