I am brand new to SharePoint. I am using SP 2007 right now. I am trying to create a new SSP but when I get to the New Shared Services Provider page there is already an error before I even do anything. It says the error is No indexers. Down at the Index Server section the 'Index Server' drop-down is disabled and blank and it says "No indexers" underneath it. The 'Path for index file location' text box is also disabled? What exactly does this mean and what do I have to do to fix it so that I can create my SSP?

No Indexers 1. Go go SharePoint Central Administration 2. Click on the Operations tab (Middle one). 3. Select Services under Topology and Serivces4. Find 'Office SharePoint Server Search' service and start it.5. On 'Configure Office SharePoint Server Search Service Settings on server' 6. Check 'Use this server for indexing content' option, fill other required (Note, for all SharePoint configuration accounts follow DOMAIN\USERNAME, if not in some cases you will encounter errors that hardly ever explain where it stems out from.)7. Hit the OK button. 8. On the side menu click "Shared Services Administration" 9. Hit the "New SSP" in the bar. 10 There you go, no more Indexer Error. Amir Kayvan SharePoint / Web Developer administrator@dobuydirect.com

Hi Amir, The problem for me (and many, many others out here) is that step4 above (Configure Office Sharepoint Search service) simply doesn't exist. I installed from the MOSS cd and other MOSS features exist but not this one. I can find nothing in the install logs as to why other MOSS features exist but not this one! I can not find any PSCONFIG parameters that will install Office Sharepoint Search. I can not find anySTSADM parameters that will install Office Sharepoint Search. There is no Office SharePoint service listed in the SERVICES.MSC list - only Windows Sharepoint Services Search. Using STSADM to start the service simply returns the message "No Search Service" A Google groups post suggests uninstalling MOSS and ensuring the Advanced/Complete option is selected. I'm very, very reluctant to un-install MOSS again as last time the uninstall scratched IIS6's metabase which took me the best part of 5 hours to rebuild! Surely there is another way? ... In a multi-server serverfarm environment I'd have thought shifting services around would be easy! I'm just a single server and I can't even find a way to introduce this service. There must be ... But how ???? Help!

Please tell me someone has an answer to this gentleman's ^^^ question. I'm in the exact same boat here and uninstalling MOSS is pretty much the last thingI want to to do. Is there no way to get this service onto the machine without a full reinstall??

hi i am new toMOSSand working from last 3 weeks in this tool. m struggling regarding hiding default properties of SSP. for example i dont want the picture property(dafault) of SSP to appear in my user profilepage of useras i already made custom webpart for it. what are the possible things that can be done for it are: 1. either hide the picture property in profile page of the user. 2. if above cant be done...delete the picture property from SSP. can u please help me regarding this with any of the solution. what can else be done please suggest.

Hi there, Same problem here. Is somebody from Microsoft reading this? Yours truly, Fred

Hi there, Sorry for being a little upset in my previous post. Here's how I got the problem solved for me: Open SharePoint Products and Technologies Configuration Wizard, confirm all Windows with YES, OK and FINISH, settings stay default Central Administration | Operations | Topology and Services |Services on Server, "Windows SharePoint Services Search" Click on Start, configure the accounts and settings appropriately Central Administration | Applications Management | SharePoint Web Application Management | Content Databases, click on "WSS_Content", in "Select Windows SharePoint Services search server" click on the drop down field and select your server Finally I restarted the services IIS and Windows SharePoint Services Search (dont know whether thats necessary or not) I hope I haven't forgot a step... Maybe you can post whether it helped you, too. Yours truly, Fredo

This worked for me thanks a million. If someone is using a MOSS Site and I create a new SSP for the current site do I need to make users aware this is happening or this is an independent process ? Thanks

Thanks This helped me a lot. I have a question though. If I need to create a new SSPprovider for current site . Do I need to make users aware that this is happening or this is an independent process

This worked. THANKS!! -BW

If this doesn't work, I would suggest trying to remember what installation options you entered when you install the MOSS binaries... If you select Web Front End (instead of Complete) then no Index or Query functions will be available to the MOSS instance. This was my problem, and I had to uninstall-reinstall...

Is there any way to do this without fully reinstalling MOSS? I must have selected Front-End because when I look at shared services I don't see the search index service and when I try to start it with stsadm I get an error "No Indexer Service". Also, will uninstalling and reinstalling cause me to lose my sites so I'll have to reconfigure or restore etc? Blah, there has to be a better way than uninst/install.

Hy Fredo Thanks a lot! Seems to work fine now. Thomas

Thomas,There is not other option than uinstall and reinstall. take a back up of all the SQL Db's and resotre them once you have resinstalled MOSS. This will save a lot of time and work.Harish

thanks..amir....its configured now

This does not work.... the service will not start because there is no indexer....and you can't configure it because there is no indexer server listed.... does anyone know of way to fix this ?

This does not work.... the service will not start because there is no indexer....and you can't configure it because there is no indexer server listed.... does anyone know of way to fix this ? Got around this problem of no indexer available. 1.) Run the SharePoint Configuration Wizard and disconnect your server from the farm. This keeps your farm configuration and all web applications and content intact... note where your configuration database is located. 2.) Uninstall SharePoint, select the option to remove all IIS web apps, etc. from your server. (and reboot) 3.) Reinstall SharePoint. Be sure to select Advanced mode and the Complete option. 4.) Run the SharePoint Configuration Wizard and reconnect to your server farm. You'll have to tell it where your configuration database is. 5.) When you setup your Services on Server, you should now have the Office Search service available, and can setup your SSP. 6.) After you this point, you'll have to reinstall any features, solutions or make config changes that you had installed/done before.

This does not work.... the service will not start because there is no indexer....and you can't configure it because there is no indexer server listed.... does anyone know of way to fix this ? Got around this problem of no indexer available. 1.) Run the SharePoint Configuration Wizard and disconnect your server from the farm. This keeps your farm configuration and all web applications and content intact... note where your configuration database is located. 2.) Uninstall SharePoint, select the option to remove all IIS web apps, etc. from your server. (and reboot) 3.) Reinstall SharePoint. Be sure to select Advanced mode and the Complete option. 4.) Run the SharePoint Configuration Wizard and reconnect to your server farm. You'll have to tell it where your configuration database is. 5.) When you setup your Services on Server, you should now have the Office Search service available, and can setup your SSP. 6.) After you this point, you'll have to reinstall any features, solutions or make config changes that you had installed/done before. Moderator Note: You proposed two posts as answers. The first asn't an answer. The second was written by you. In future please only propose as answer posts from *other people* (not yourself) and preferably only when they really are an answer to the OP's question.

Good day The first and quite simple check that you need to do is to make sure that you include the DOMAIN\USERNAME in the user details that you specify, if there is no people picker always go this route Cheers

Thanks amir...your answer helped me lot.....shashi mishra