I am trying to get rid of this message:

I tired this as suggested but as you can see I am having no luck. any ideas?

PS C:\Users\administrator.DOMAIN1> psconfig.exe -cmd upgrade -inplace v2v -force

SharePoint Products Configuration Wizard version 14.0.4762.1000. Copyright (C) M
icrosoft Corporation 2010. All rights reserved.

The upgrade command is invalid or a failure has been encountered.
The passphrase parameter for the upgrade command is required.

Usage:
        PSCONFIG.EXE -cmd <Command> [Parameters]
        PSCONFIG.EXE -help [Command]
        PSCONFIG.EXE -?
Commands:
        setup
        standaloneconfig
        configdb
        helpcollections
        secureresources
        services
        installfeatures
        adminvs
        upgrade
        evalprovision
        applicationcontent
        quiet

These seem to be SP2010 databases yes? v2v would be used for SharePoint 2007 databases in a SharePoint 2010 environ.  For SharePoint 2010 databases in a newer patch level SharePoint 2010 environ you would use b2b. 

See the following reference on the difference between v2v and b2b:
http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d%2D183c%2D4fc2%2D8320%2Dba5369008acb&ID=306

Have you tried something like the following?

psconfig.exe -cmd upgrade -inplace b2b -force

Or if required:
psconfig.exe -cmd upgrade -inplace b2b -passphrase <insert-passphrase-here> -force

Hi

I have this same issue

psconfig.exe -cmd upgrade -inplace b2b -passphrase <insert-passphrase-here> -force

The command is looking for anything that has not been updated to the current build of the farm and tries to update it.

v2v will take you from 12 to 14 for example where as b2b will take you from 14.0.0.4762 to 14.0.0.5114 for example.

To know what build level you are going from and too you would need to review the DLL level active in the farm along with the Versions table in the databases of the farm.

For example you could review the StateServiceDatabase and see what Version it shows in its table entries cmpared to the Configuration database.

Fred

Thanks for that reply - I feel a bit more reassured. to break the farm on the day the pilot started would not be career enhancing. Incidently, I ran this command on Friday and it seem to stop the w3c service before tell me that there was an issue with passphrase. Startled one or two of my test users!  I am a bit used to this behaviour from SharePoint so easily spotted.

I don't have  direct access to the DB instances in our farm - even though I installed it (don' ask)! So it's a SQL query I guess run by the dba I guess. Unless, that is you know of a Powershell command I could run to see config database versions and or, the version per each of the "service app" dbs such as the StateServiceDatabase. No worries if not ... I can keep searching for the answer.

Firstly Check the Database is not running under the suspect mode in SQL or is not running as a single user.

 Make sure that you are able to navigate to the tables inside those databases.

Run the following command from the bin folder PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install

Hi

Thanks that was a useful command. 

Daniel

Hello,

If the upgrade command line "PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install" finish with success, maybe this search's databases are linked to search service application who have been uninstalled.

To list search service application you can use this command :

Get-SPEnterpriseSearchServiceApplication

To list database used by your search services, you can use this command :

Get-SPEnterpriseSearchServiceApplication | format-list "PropertyStores","CrawlStores","SearchAdminDatabase"

If the databases to upgrade aren't listed and if you are sure database are not used you can delete them :

get-spdatabase | where {$_.name -eq 'db_name'} | foreach {$_.Delete()}

Florent C.

I've been running the psconfig command a number of times but the warning about "compatibility range" hasn't gone away. And the SharePoint_AdminContent<GUID> DB was shown in red even if it showed "No action required" under Database Status.

But what made the trick for me was just to goto SP Central Administration / Backup and Restore /Perform a backup. When it completed the warning was gone