I recently had to deal with a weird SP2010 error. The error message that the client received was as follows
“L’opération de montage de l’application rassembleur GUID a échoué, car la version du schéma de la base de données d’administration de recherche est inférieure à la version du schéma de compatibilité descendante minimale prise en charge pour cette application rassembleur. La base de données n’a peut-être pas été mise à niveau.”
(Yes the installation is in French). I must admit that sometimes the terms used in the error messages are very obscure .. (I naively thought that an error message would help …)
After conversation with the client, he tells me that the only operation that has been done on its SharePoint was the passage of a KB fix, no upgrade of server or anything else.
After some research, I found the English version of the error message (all french talking people know we have a lot more answers when looking for an error message in English)
This therefore gives
“The mount operation for the gatherer application GUID has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded”
And thanks to this English version I could find possible solution. One possibility is that this error message may appear if you install a service pack without restarting the SharePoint configuration wizard. Yes but how do you know if the wizard was done without launching it (and therefore without downtime of the server)? For this there is a powershell command which will ask nicely to our SharePoint if we need to run this wizard!.
The command is
A command that is executed quickly and returns “True” or “False”. If this is true, that means the wizard must be run (which was the case for me).
So change folder to get the PSConfig.exe found in “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN” and execute the command
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
And now, the server is updated and the error is gone!
Hope this helps!