On some of my SharePoint farms the Restore-SPEnterpriseSearchServiceApplication command fails with the following error:
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 15.0.26.0 of Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence failed. --->
System.Data.SqlClient.SqlException: 'DF__MSSCrawlS__IsDed__117F9D94' is not a constraint. Could not drop constraint. See previous errors.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.Office.Server.Data.SqlSession.ExecuteScript(TextReader textReader, Int32 commandTimeout)
at Microsoft.SharePoint.Upgrade.SPDatabaseAction.ExecuteSql(String sql, Int32 commandTimeout) at Microsoft.Office.Server.Search.Upgrade.UpgradeCrawlStoresAndComponentsTables.Upgrade()
at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.Upgrade()
at Microsoft.Office.Server.Search.Upgrade.SearchDatabaseSequence.Upgrade()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSession(Object lockObject, IUpgradable iup, SPUpgradeOperationFlags upgradeOperationFlags)
at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.RunPostRestore(SPRestoreInformation args)
at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Restore(String name, SearchQueryAndSiteSettingsService service, SPIisWebServiceApplicationPool applicationPool, SPDatabaseParameters adminDBParameters, SearchServiceInstance adminComponentInstance)
at Microsoft.Office.Server.Search.Administration.SearchService.<>c__DisplayClass9.<RestoreApplication>b__8()
at Microsoft.Office.Server.Search.Administration.SearchService.CreateApplication(String name, CreateSearchApplicationDelegate createSearchAppDelegate)
at Microsoft.Office.Server.Search.Administration.SearchService.RestoreApplication(String name, SPDatabaseParameters adminDBParameters, SearchServiceInstance adminComponentInstance, SPIisWebServiceApplicationPool applicationPool)
at Microsoft.Office.Server.Search.Cmdlet.RestoreSearchServiceApplication.CreateDataObject() at Microsoft.SharePoint.PowerShell.SPNewCmdletBase`1.InternalProcessRecord()
at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()
Error Category: InvalidData Target Object Microsoft.Office.Server.Search.Cmdlet.RestoreSearchServiceApplication Details NULL RecommendedAction NULL
This problem seems to occure when the MSSCrawlStoresTable contains a constraint named DF__MSSCrawlS__IsDed__1CF15040 instead of DF__MSSCrawlS__IsDed__117F9D94. I've compared this table with other SharePoint farms and found it to be correct in two of them using the following configuration:
SP2010 April 2012 CU (14.0.6126.5000), SQL Server 2008 R2 (10.500.4000)
SP2010 SP1 (14.0.6029.1000), SQL Server 2008 R2 (10.50.2500)
But it got the wrong name in my farms with the following configuration:
SP2010 December 2012 CU, SQL 2012 SP1 (11.0.2332)
SP2010 August 2012 CU (14.0.6126.5000), SQL 2012 SP1 (11.0.2332)
Renaming the constraint to DF__MSSCrawlS__IsDed__117F9D94 fixes the problem with the PowerShell command and the search service seems to be working.
Is this work around supported, or are there any other ways to fix the problem?
Best regards
Johan