Application Server Administration job failed – HTTP status 401: Unauthorized
On a SharePoint 2007 environment we continually received the below error message in the windows event log.
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 9/09/2008
Time: 11:41:44 AM
User: N/A
Computer: SYDSRVPROD0010
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (77fb83be-b023-4802-9d23-d246a1ce3b09).Reason: The request failed with HTTP status 401: Unauthorized.Techinal Support Details:
System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)
at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(WellKnownSearchCatalogs catalog, SearchSharedApplication application)
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The following message appears in the SharePoint diagnostic logs:
05/26/2008 14:46:52.71 OWSTIMER.EXE (0×0898) 0×152C Search Server Common MS Search Administration 86×4 High Configuring the Search Application web service Url to ‘https://index:56738/MOSS%20Shared%20Services/Search/SearchAdmin.asmx’.05/26/2008 14:46:52.72 OWSTIMER.EXE (0×0898) 0×152C Windows SharePoint Services Topology 0 Medium Adding DOMAIN\account_ssp to local group 0.05/26/2008 14:46:52.72 OWSTIMER.EXE (0×0898) 0×152C Search Server Common MS Search Administration 86ze High Exception caught in Search Admin web-service proxy (client). System.Net.WebException: The request failed with HTTP status 401: Unauthorized. 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)05/26/2008 14:46:52.72 OWSTIMER.EXE (0×0898) 0×152C Office Server Office Server Shared Services 7u16 Critical Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (77fb83be-b023-4802-9d23-d246a1ce3b09). Reason: The request failed with HTTP status 401: Unauthorized. Techinal Support Details: System.Net.WebException: The request failed with HTTP status 401: Unauthorized. at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn) at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(WellKnownSearchCatalogs catalog, SearchSharedApplication application) at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() at Microsoft.Office.Server.Administration.Appl…
The following message also appears in the IIS logs on the index server:
2008-07-01 09:54:22 W3SVC1720207907 192.168.1.86 POST /MOSS+Shared+Services/Search/SearchAdmin.asmx – 56738 – 192.168.1.72 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.1433) 401 1 0
To Fix the problem we hard to change the authentication back from kerberos to ntlm using the following command:
C:\>STSADM.exe -o SetSharedWebServiceAuthn -ntlm
Operation completed successfully.
After running the event log displayed the following message
Event Type: Information
Event Source: Office Server Search
Event Category: Search service
Event ID: 10042
Date: 9/09/2008
Time: 11:44:38 AM
User: N/A
Computer: SYDSRVPROD0010
Description:
A new query machine, ‘SYDSRVPROD0010′, has been added to the query rotation based on changes to farm topology. Component: 2e3c638e-00d0-4d7e-862e-64abcd47d883For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Apparantly this issue is resolved by the infrastructure updates to MOSS.
Bookmark/Search this post with:
