Quantcast
Channel: SharePoint 2013 - Setup, Upgrade, Administration and Operations forum
Viewing all articles
Browse latest Browse all 21070

set up index server /crawler in my 3 server sp 2013 environment

$
0
0

hi,

 i have to set up a 3 server  env in my sp 2013 farm. i am having 3 boxes, with 3rd box  configured as db server, sql server 2012 being installed.

in my first server- server1  central admin is configured  with http://myservername:1230/. now i want to configure the second server as  index server/crawler such that i have  a  dedicated server for crawling.

would like to know how to set up crawler in my env.

note: when customer gave us this 3 servers :

1) am having central admin created.

2)in the 2nd server also, i am able to see the same  central admin .

whats exactly is the meaning of this? does  this  2nd server is not acting as a index server?

does this 2nd server also acting as a WFE ? , ie, am having 2 WFEs and 1 DB server. 

3) if i wanna configure crawler ,should i run the config wizard on the 2nd server with a new central administration created with a port num.?

when i was trying to run the already created search serv appln. it gave me " search serv admin. not running " error.

and

4) i have created a new search serv appln and created a  content source and crawled the contents.

but when i crawled the contents i am not able to get the crawled properties or managed properties[ i have created 2 columns one single line of text data type and other being managed metadata column in a  test document library and uploaded few dummy documents.] is this because of crawler is not configured properly?

5) i have ran that power shell script  provided by Paul Stork  in one of the threads in this  forum to provision the SSA.

6) so i am having a kind of conflicting env. in my sp farm, so what steps i need to apply  in order to configure crawler .

help is highly appreciated! 


Viewing all articles
Browse latest Browse all 21070

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>