Hi all,
After the December 2014 CU, all my farms have their BDC Service Database in compatibility range.
I found the solution from Markus’ Blog and I’ve executed this PowerShell command:
Add-PSSnapinMicrosoft.SharePoint.PowerShell
(Get-SPDatabase|?{$_.type -eq"Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase"}).Provision()
Also, I got an error (as mentionned in his post), and checked the access rights.
This is the error I had:
PS C:\Windows\system32> (Get-SPDatabase | ?{$_.type -eq "Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase"}).Provision()
Exception calling "Provision" with "0" argument(s): "Cannot find the object "dbo.Versions" because it does not exist or you do not have permissions."
At line:1 char:1
+ (Get-SPDatabase | ?{$_.type -eq "Microsoft.SharePoint.BusinessData.SharedService ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : SqlException
So, I’ve asked to the SQL Team to add the SPDataAccess for the service account:
Then, I ran again the PowerShell command, and my BDCS database is now in “No action required” status.
I’ve also 3 system database that are in “Database is too old and upgrade is required” status.
For those 3 DBs, I’ve tried the same way as for the BDCS database:
First, getting the correct Type Name for each DB:
Get-SPDatabase|ft -Auto
Second, preparing the PowerShell commands:
(Get-SPDatabase|?{$_.type -eq"Microsoft SharePoint Foundation Subscription Settings Database"}).Provision()
(Get-SPDatabase|?{$_.type -eq"Microsoft.Office.Server.Administration.ProfileDatabase"}).Provision()
(Get-SPDatabase|?{$_.type -eq"Microsoft.Office.Server.Administration.SocialDatabase"}).Provision()
Third, checking and adapting the SQL settings for SPDataAccess
Finally, executing my PowerShell commands.
Voilà,
That’s all Folks !!!
