Unable to complete upgrate after installing Aug 2011 Cu for Sharepoint 2010 and getting error of Exception: localStoragePath
07/10/2011 3 Comments
Every upgrade attemp is one of challage for IT team. So this time we are working on a problem which is occured after Aug 2011 Cumulative Update.
the symptom is Sharepoint Configuration Wizard can not able to complete and finishing with failure.
First of all once we check the PSCDiagnostics logs we could not able to find something useful:
Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\PSCDiagnostics_10_7_2011_9_55_26_860_989474110.log, fix the problem, and run this configuration wizard again
Cool but it say nothing. So we peek that let check “upgrade” logs …
And see some error. LocalStoragePath. What is actually LocalStoragePath and why we are getting this error while upgrading. It is definitly something wrong with search db.
[OWSTIMER] [SPUpgradeSession] [ERROR] [10/7/2011 10:05:49 AM]: Exception: localStoragePath
[OWSTIMER] [SPUpgradeSession] [INFO] [10/7/2011 10:05:49 AM]: SearchAdminDatabase Name=Fast_Query_SSA_DB_3a64d349dc2249679a8be…
[OWSTIMER] [SPUpgradeSession] [ERROR] [10/7/2011 10:05:49 AM]: at Microsoft.Office.Server.Search.Administration.SearchApi.AssertParameter(String parameterName, Boolean condition)
at Microsoft.Office.Server.Search.Administration.SearchApi.UpdateAdminComponent(String serverName, Guid serverId, String localStoragePath, Boolean standalone, Nullable`1 settingsInRegistry)
at Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence.InitializeTopologyBasedOn2007Settings()
at Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence.PostUpgrade()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
The problem in our scenario is some how psconfig can not update the topology, possible cause for this may be service name changes may be an old conf. backup restored or even more the server name has changed.
Resolution
1. Checked the Upgrade error log and notice following information
[OWSTIMER] [SPUpgradeSession] [INFO] [10/7/2011 10:05:49 AM]: SearchAdminDatabase Name=Fast_Query_SSA_DB_3a64d349dc2249679a8be…
2.Use Get-SPEnterpriseSearchServiceApplication cmdlet and list all search service applications. we try to delete the Search Service Application. Unable to delete the service Application through GUI hence tried successfully with following Powershell command.
$ssa = Get-SPEnterpriseSearchServiceApplication -Identity 4e6d0c5c-f47b-425e-a637-e8a44aca12ae
$ssa.Delete()
We had 2 search application more so we deleted all of them .
3. Run the configuration wizard
4. created a new SSA to after configuration wizard has run.
About bpostaci
Pingback: CLSCompliant(true)
Merhaba Buğra Bey,
Bahsetmiş olduğunuz çözümden ötürü çok teşekkür ederim. Benimde işime yaradı. Benim sorunum localStoragePath hatası değildi ama yine aynı yöntemle devam ettim ve sorunum çözüldü. Verdiğiniz bilgilerden ötürü tekrar teşekkürler. Bu arada benim sorunum ise şu şekilde
Upgrade [SearchAdminDatabase Name=Search_Service_Application_DB_3fca005e7...] failed.
[OWSTIMER] [SPUpgradeSession] [ERROR] [3/17/2012 7:07:52 PM]: Exception: Index was outside the bounds of the array.
[OWSTIMER] [SPUpgradeSession] [ERROR] [3/17/2012 7:07:52 PM]: at Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence.InitializeTopologyBasedOn2007Settings()
at Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence.PostUpgrade()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
Yani sorun Index was outside the bounds of array. Bu sıkıntıda search application service için yaratılmış olan obje de bazı alanların null kalması ve GUID’lerinin olmamasından verdi. Bende sizin dediğiniz gibi ilk önce servisleri listeledim ardından bu durumu fark ettim iki tane servis var ama biri bozuk durumda. Ben de bozul olanı sildim ve yeniden konfigürasyonu başlattım işlem tamamlandı. Arama ve indeksleme yaptım her hangi bir sorun ile karşılaşmadım. Belki böyle bir sıkıntı ile yaşayan arkadaşlar da sizin çözümünüze ek olarak bu çözümle dertlerine deva bulurlar.
Saygılarımla,
Ersan DÖLEK
Thank you! Thank you! Thank you! Saved my A$$ tonight! :)