Dennis Bottjer | ASP.NET + SharePoint Architect, Trainer & Speaker

"An Ounce of Prevention is Worth a Pound of Cure" - Ben Franklin
posts - 168, comments - 59, trackbacks - 41

My Links

News

Add to Technorati Favorites The views expressed in this blog are mine and mine alone, not that of my employer, Microsoft, or anyone else’s. No warrantee is given for the quality of any material on this site.

Tag Cloud

Archives

Post Categories

Cannot configure crawling schedules for MOSS 2007 SSP content sources

Problem:

We just installed a Medium MOSS 07 Farm.  The Farm has two front end webs and a dedicated indexing server.  The two front end webs are configured to execute search queries.  The SSP Admin site was loading and a search content source could be selected.  However, after specify a schedule for the selected content source and clicking ok an access denied error would appear on the schedule management window.  The message said "Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))."  The MOSS Error Logs captured the following nastiness:

w3wp.exe (0x0B5C) 0x0E48 Search Server Common MS Search Administration 86zc High Exception caught in Search Admin web-service proxy (client). System.Web.Services.Protocols.SoapException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.Office.Server.Search.Administration.SearchWebServiceProxy.RunWithSoapExceptionHandling[T](String methodName, Object[] parameters)

... and more

Resolution:

The log and error message hinted at some kind of permission issue.  We also noticed that the logs specifically implicated our third server in the farm, our dedicated index server.  After some searching on MSDN and TechNet we learned that the C:\Windows\Tasks directory was not configured properly.  The local WSS_WPG machine needed to be given read and write permissions to the C:\Windows\Tasks directory.  Once we had assigned appropriate permissions and completed an IISReset form good measures we were able to save a schedule. 

For more info review this MS KB posting: http://support.microsoft.com/kb/926959

 

Print | posted on Wednesday, January 23, 2008 3:44 AM | Filed Under [ SharePoint ]

Feedback

Gravatar

# SharePoint Search Tips

4/29/2009 5:23 AM | drowningintechnicaldebt.com
Comments have been closed on this topic.

Powered by: