Unexpected error in “content sources” when try to crawl in SSP

Errors:

Exception Details: System.IndexOutOfRangeException: DisplayInAdminUI

detailed:

Could not find stored procedure ‘dbo.proc_MSS_GetCrawlHistory’.   at Microsoft.SharePoint.Portal.Search.Admin.Pages.SearchAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.SharePoint.Portal.Search.Admin.Pages.SearchSSPAdminPageBase.OnError(EventArgs e)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP._layouts_listcontentsources_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Caused:

SharePoint database is not on the same version as the farm’s configuration database. If you open up SQL Server and looked at the rows on the dbo.Version tables in both the configuration database and the database associated with the failed SSP, and check that they are not in sync; the updates for the farm had been applied to the configuration database but not the SSP databases.

Solution:

1. On a SharePoint server in your farm (I’d suggest the one hosting the Central Admin site), open a command prompt and navigate to the directory containing the SharePoint Products and Technologies Configuration Wizard (psconfig.exe)
2. Execute the following command:
   psconfig -cmd upgrade -inplace b2b -wait -force
3. Review the PSconfig and Update logs to see if any errors were reported.
4. Check the versioning data in the dbo.Version table in both of the SSP’s databases to confirm that they now matched the config database’s version.
5. Open the SSP Admin site and tried to administer the farm’s Search configuration

Resources:

http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/69e664d9-c841-4c9e-8468-2e8b605d781a?prof=required