Sharepoint 2007 - Start MS Office Search Service Fails

Hi there,

I'm doing an installation of Microsoft SharePoint 2007 on a three server farm.  I have one back end database server, a front end server and one I plan on usiing for indexing.

The web server was the first server to be installed on the farm and the index server was the second.  I have installed the full product on both.  All is fine on the web server however when I try to start the MS Office Search Server from the second box I get an error.

"An unhandled exception occurred in the user interface.Exception Information: Could not connect to server <SERVER>. This error might occur if the server is not responding to client requests, the firewall or proxy configuration is preventing the server from being contacted, or the search administration Web service is not running on the affected server. "

As the central admin site is running on the web server I took a closer look at the logs and found the following: (See Code Below)

Effectivly from what I can see one of the services on one of the servers is trying to get out via the proxy which we have which is stopping it getting to the index server.

I have logged in as all service accounts of both machines and set the proxy settings in IE to no proxy and removed the automatically detect box as well.  These settings stick and all looks fine but I still can get no joy starting this service on my machine.

The two boxes in question are Windows 2008 x64 R2 machines.

Has anyone ever seen anything like this before?  

I have tried a number of things to get roud this, manually specifying the IIS application pool credentials, using different user accounts but I just can't get any joy.

I look forward  to your responses!



03/23/2010 14:34:57.07 	w3wp.exe (0x0A70)                       	0x0A2C	ULS Logging                   	Unified Logging Service       	8pbf	Medium  	Not reporting 837w to Watson because the appropriate timespan hasn't passed	 
03/23/2010 14:34:57.16 	w3wp.exe (0x0A70)                       	0x03C4	Search Server Common          	MS Search Administration      	86z7	High    	Configuring the Search admin web service proxy Url to 'http://hs-spse01:56737/SearchAdmin.asmx'.	 
03/23/2010 14:34:57.18 	w3wp.exe (0x0A70)                       	0x03C4	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 407: Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied.  ).     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)	 
03/23/2010 14:34:57.18 	w3wp.exe (0x0A70)                       	0x03C4	Search Server Common          	MS Search Administration      	0	High    	SearchServiceInstanceSettings.Page_Init threw exception: 'System.Net.WebException: The request failed with HTTP status 407: Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied.  ).     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.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode)     at Microsoft.Office.Server.Search.Internal.UI.SearchServiceInstanceSettings.Page_Init(Object sender, EventArgs e)'.	 
03/23/2010 14:34:57.18 	w3wp.exe (0x0A70)                       	0x03C4	ULS Logging                   	Unified Logging Service       	872l	Medium  	Not reporting to Watson because the appropriate timespan hasn't passed	 
03/23/2010 14:34:57.18 	w3wp.exe (0x0A70)                       	0x03C4	Office Server                 	Office Server General         	837w	Exception	Unhandled page level exception. Path: /_admin/SearchServiceInstanceSettings.aspx, Error: Could not connect to server HS-SPSE01. This error might occur if the server is not responding to client requests, the firewall or proxy configuration is preventing the server from being contacted, or the search administration Web service is not running on the affected server., Details: Microsoft.SharePoint.SPException: Could not connect to server HS-SPSE01. This error might occur if the server is not responding to client requests, the firewall or proxy configuration is preventing the server from being contacted, or the search administration Web service is not running on the affected server.     at Microsoft.Office.Server.Search.Internal.UI.SearchServiceInstanceSettings.Page_Init(Object sender, EventArg...	 
03/23/2010 14:34:57.18*	w3wp.exe (0x0A70)                       	0x03C4	Office Server                 	Office Server General         	837w	Exception	...s e)     at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)     at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)     at System.Web.UI.Control.OnInit(EventArgs e)     at System.Web.UI.Page.OnInit(EventArgs e)     at System.Web.UI.Control.InitRecursive(Control namingContainer)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Microsoft.SharePoint.SPException: Could not connect to server HS-SPSE01. This error might occur if the server is not responding to client requests, the firewall or proxy configuration is preventing the server from being contacted, or the search administration Web service is not running on the affected server.     at...	 
03/23/2010 14:34:57.18*	w3wp.exe (0x0A70)                       	0x03C4	Office Server                 	Office Server General         	837w	Exception	... Microsoft.Office.Server.Search.Internal.UI.SearchServiceInstanceSettings.Page_Init(Object sender, EventArgs e)     at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)     at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)     at System.Web.UI.Control.OnInit(EventArgs e)     at System.Web.UI.Page.OnInit(EventArgs e)     at System.Web.UI.Control.InitRecursive(Control namingContainer)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)	 
03/23/2010 14:34:57.18 	w3wp.exe (0x0A70)                       	0x03C4	ULS Logging                   	Unified Logging Service       	8pbf	Medium  	Not reporting 837w to Watson because the appropriate timespan hasn't passed

Open in new window

Jase_xAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jase_xAuthor Commented:
Also I notice that I can start the service on the first web server but not the second.  I have done a complete install just to make sure but to no avail.  Does anyone know which part of SharePoint would be looking for this proxy server?
0
Jase_xAuthor Commented:
Never mind I appear to have fixed it.  For further reference if you find that you cannot start the search service on a second SharePoint server in your farm and you have ISA running you can edit the web.config file used to configure the Sharepoint Central Administration Service and add the following section under <system.net>

     <proxy
          usesystemdefault = "false"
          proxyaddress="http://servernameorip:port"
          bypassonlocal = "true"

     />
<bypasslist>
  <add address = "[a-z]+\.test\.internal" />
  <add address = "10\.0\..*" />

</bypasslist>
</defaultProxy>

Where obviously you can change your exceptions and proxy server address to suit.

Hope this helps someone who is stuck in the same position as me!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.