On the SSP Admin page, many pages I get unknown error such as Search Settings, Search usage reports Under Search Administration, I get unkown error for Content Sources, Crawl Rules, etc. Application error when access /_layouts/searchsspsettings.aspx, Error=Cannot find ContentPlaceHolder 'PlaceHolderGlobalNavigationSiteMap' in the master page '/_layouts/application.master', verify content control's ContentPlaceHolderID attribute in the content page. 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.Proces...

It looks like either the application.master or searchsspsettings.aspx is corrupt or some one edited it accidently can you quickly do a diff with another SharePoint server with the same service pack and CU's in place.Aravind http://aravindrises.blogspot.com

It looks like either the application.master or searchsspsettings.aspx is corrupt or some one edited it accidently can you quickly do a diff with another SharePoint server with the same service pack and CU's in place.Aravind http://aravindrises.blogspot.com

I will build a test box and check. Will recreating a new SSP fix this ?

I will build a test box and check. Will recreating a new SSP fix this ?

I will build a test box and check. Will recreating a new SSP fix this ? (looks like it won't) Yes, looks like it was modified with references to customized xxx.css. However, I'll need to keep that customization but make the file work...somehow.

Re-creating a new SSP in the same environment will not fix this as the admin application pages are shared across web applications. You need to go to a fresh box and take a backup of the files and do a diff. Aravind http://aravindrises.blogspot.com

It appears that the application.master (custom) did not have all the Content Navigation tag sections. Took out all the references to the invalid sections PlaceHolderGlobalNavigationSiteMap on all aspx files in the Sharepoint aspx files and the SSP is now functional.