Sharepoint Unknown Error

[mtdmitchell]

Just gone to configure a federated search on sharepoint 2007 via Central administration > Shared service administration >search administration . then click on federated locations and i get "Unkown error"

also if i try to add a web part for federated results on any web site the following error occurs:

unable to add seleted web parts(s)

deferated results: could not find stored procedure

'dbo.proc_MSS_Getlocationsconfigurations'


i don't really know where to start looking! im presuming somethin is missing or not activated.

[mtdmitchell]

Ive enabled callback so the error messages displays instead of the Unkown error:

Could not find stored procedure 'dbo.proc_MSS_GetLocationConfigurations'. at Microsoft.SharePoint.Portal.Search.Admin.Pages.Sea rchAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.SharePoint.Portal.Search.Admin.Pages.Sea rchSSPAdminPageBase.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_managefederatedlocations_aspx.Process Request(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionSte p.System.Web.HttpApplication.IExecutionStep.Execut e()
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean& completedSynchronously)

[mtdmitchell]

heres the fix

Error when trying to access "content sources under crawling

I did some searching on that error and found that it occurs when a 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.

, here's what I did to resolve it:

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 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.

This command will run the SharePoint Products and Technologies Configuration Wizard, but with specific conditions. The wizard will execute a “build-to-build” upgrade of the farm, forcing all files and databases to be upgraded to the latest patch version that has been installed for the farm