• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 614
  • Last Modified:

Office SharePoint Server 2007, Office SharePoint Server Search : unhandled exception occurred in the user interface

An unhandled exception occurred in the user interface. Exception information:Unable to connect to remote server

I am installing a fresh MOSS 2007 farm on three servers + DB server.As I try to start Office SharePoint Server Search from the central admin, on server "B", i am getting this error.

What can be going wrong?
0
Paawan
Asked:
Paawan
  • 4
  • 2
2 Solutions
 
garignackCommented:
1. Check the firewall to ensure that you aren't blocking any of the SharePoint backend communication ports on server "b" (typically 56737, 56738).  If you are using Windows 2k8, you will have to add an exception in the inbound firewall for these ports.  You may want to enable firewall logging on server "b", attempt start office search, and see if there were any blocked packets from the Central Admin Server (Server "a"?).

2. Check that the Farm Service account is in the local administrator group of the second server.

3. You may also have to manually setup the search on the second server ->

Goto run-> services.msc
Ensure the Office SharePoint Server Search is set to automatic and is running under the domain credentials you are using for the search service.
Open a command prompt and goto the 12 hive bin folder ("C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN")
run: stsadm -o osearch -action start -role index
0
 
PaawanAuthor Commented:
Thank you for that...

Finally I got rid of that UI error, now I am using Server A for Indexing content and Server B for serving search queries. When I started with automatic option it said it couldnt start propogation, so i opted for manual stsadm

I used the below to start:
stsadm -o osearch -action start -role query

Now the new error is "Object reference not set to an instance of an object"
your help in this is highly appreciated.
0
 
PaawanAuthor Commented:
Above refers.

Eventhough it says "Object ref not set to an insta...." in the central admini its says the service started on Server B.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
PaawanAuthor Commented:
Few screen shots for the above.
services.jpg
failprop.jpg
0
 
garignackCommented:
To manually setup the Propagation Share, log into the Server "B" with an account that has Database Access and local adminsitrative rights and run:

STSADM.exe –o osearch –propagationlocation "c:\SearchIndexes"  (note: the location must exist before running this command.)

See:
http://blogs.msdn.com/martinkearn/archive/2008/10/29/manually-configuring-search-propagation-location-using-stsadm.aspx

You will still probably want to check the permissions on your service accounts.  Ensure that the Farm Service Account has administrative priviledges on each of the servers (except for the DB server)  You may be able to remove it's elevated priveledges after everything is configured and the Entire farm is working.
0
 
PaawanAuthor Commented:
That was perfect and I have started the services.
0

Featured Post

Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now