MOSS 2007 Issue when Upgrading to SP3 : Ensure enough disk space for Search DB Transaction Log
You may experience the following behavior when upgrading your MOSS2007 environment to SP3:
If the Office Server Search functionality is configured within SSP, while Configuration Wizard is running after installing the WSS and MOSS2007 bits, the SQL Transaction Log assigned to the Search DB will tremendously increase its size (up to 100 GB in some cases).
So make sure you have enough space on the Drive on SQL Server where the Transaction Log is located.
Otherwise, the Wizard will fail at Step8 with a Timeout while trying to start the Office Sharepoint Server Search, Search will no longer work.
Entries in SQL Error Log are mentioning the Transaction Log for Search DB that is running out of space.
--PSCDiagnostics_<..>.log--
01/04/2012 11:09:15 7 ERR A exception was encountered when trying to stop service OSearch
01/04/2012 11:09:15 7 ERR An exception of Type 'System.ServiceProcess.TimeoutException' was thrown. Further Information: The action could not complete because the Timeout has expired.
System.ServiceProcess.TimeoutException: The action could not complete because the Timeout has expired. at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout) at Microsoft.SharePoint.PostSetupConfiguration.ServiceHelper.Stop(String serviceName)
--Upgrade.log--
[SPManager] [ERROR] [04.01.2012 15:05:49]: Action 12.2.508.0 of Microsoft.Office.Server.Search.Upgrade.SearchDatabaseSequence failed to rollback.
[SPManager] [ERROR] [04.01.2012 15:05:49]: at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)
[SPManager] [ERROR] [04.01.2012 15:05:49]: at System.Data.SqlClient.SqlTransaction.ZombieCheck() at System.Data.SqlClient.SqlTransaction.Rollback(String transactionName) at Microsoft.Office.Server.Data.TransactionalSqlSession.Rollback() at Microsoft.SharePoint.Upgrade.SPDatabaseAction.Rollback()
and the Event Viewer entry:
Level: Error
Source: OfficeServer Search
Category: Gatherer
Event ID: 10036
Date: 29.12.2011
Time: 21:10:48
User: None
Computer: Server_Name
Description: Database Error
Source: Microsoft OLE DB Provider for SQL Server
Code: 2812 was found 1-time
Description: The Stored Procedure 'dbo.proc_MSS_GetCrawls' was not found
Context: Application 'SharedServices_Name'
References:
Database maintenance (Office SharePoint Server 2007) https://technet.microsoft.com/en-us/library/cc825329(office.12).aspx
Deploy software updates for Office SharePoint Server 2007 https://technet.microsoft.com/en-us/library/cc263467(office.12).aspx
Shrinking the Transaction Log https://msdn.microsoft.com/en-us/library/ms178037.aspx
Comments
- Anonymous
November 14, 2012
Our problem was this, but with the content database log instead of search db. Thanks so much for the help and references. They're invaluable.