Search Configuration on MOSS 2007

By -
Created a VM environment for one of my customer and did the following to configure search - pretty straight forward.




Start and configure the Search service
  1. On the SharePoint Central Administration home page, click the Operations tab on the top navigation bar.
  2. On the Operations page, in Topology and Services, click Servers in farm.
  3. On the Servers in Farm page, click the server on which you want to configure the search service.
  4. Click Start next to Office SharePoint Server Search.
  5. On the Office SharePoint Server Search Settings page, in the Query and Indexing section, make sure that the Use this server for indexing content and Use this server for serving search queries check boxes are selected.
  6. In the Default Catalog Location section, type a path to a physical folder to store the index files, or use the default location that is specified.
  7. In the Contact E-Mail Address section, specify a valid e-mail address.
  8. In the Service Account section, click Configurable, and in User name and Password, type the user name and password for the user account under which you want the Search service to run. The user account must be a member of the Administrators group on the computer that is running the Search service. If you want to use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers, see the Known Issues/Readme for Office SharePoint Server 2007 Beta 2. The user name must be in the format DOMAIN\username.
  9. In the Web Front End And Crawling section, do one of the following:
    • If you are configuring the search service on a server that provides Web services and renders Web content, click No dedicated Web front-end computer for crawling
    • If you are configuring the search service on a server that is a standalone search server that does not provide Web services and render Web content, click Use a dedicated web front end computer for crawling, and then, in Select a web front end computer, click the computer you want to use for crawling.
  10. Click Start.
Start the Windows SharePoint Services Web Application service You must start the Windows SharePoint Services Web Application service on every computer that you want to act as a Web server and was set up using the Complete option during Setup. This service is started by default on servers that were set up using the Web Front End option. To enhance security, you can leave this service turned off on application servers that do not provide Web content to client computers. Also, you do not need to turn this service on to use SharePoint Central Administration on a server.
  1. On the SharePoint Central Administration home page, click the Operations tab on the top navigation bar.
  2. On the Operations page, in Topology and Services, click Servers in farm.
  3. On the Servers in Farm page, click the server on which you want to start the Windows SharePoint Services Web Application service.
  4. Click Start next to Window SharePoint Services Web Application.
Create the Shared Services Provider
  1. On the SharePoint Central Administration home page, click the Application Management tab on the top navigation bar.
  2. On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm's shared services.
  3. On the Manage this Farm's Shared Services page, click New SSP.  Important: If you have not created a Web application for the SSP administration site, you need to create one before you create the SSP. If you have already created a Web application for the SSP administration site, skip to step 14.
  4. On the New Shared Services Provider page, click Create a new Web application.
  5. On the Create New Web Application page, in the IIS Web Site section, click Create a new IIS web site, and do not modify the default settings in this section.
  6. In the Security Configuration section, under Authentication provider, select the appropriate option for your environment, and do not modify the default settings in the remainder of this section.
  7. In the Load Balanced URL section, do not modify the default settings.
  8. In the Application Pool section, click Create new application pool.
  9. In Application pool name, enter the name of your application pool or use the default name.
  10. Click Configurable, and in User name and Password, type the user name and password for the user account under which you want the application pool to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
  11. In the Database Name and Authentication section, verify the database information and make sure that Windows Authentication (recommended)is selected.
  12. In the Search Server section, do not modify the default settings.
  13. Click OK. Upon successful creation of the Web application, the New Shared Services Provider page appears.
  14. In the SSP Name section, in Web Application, select the Web application that you created for the SSP, and do not modify any of the default settings in this section.
  15. In the My Site Location section, do not modify any of the default settings.
  16. In the SSP Service Credentials section, in User name and Password, type the user name and password for the user account under which you want the SSP to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
  17. In the SSP Database section, you can either accept the default settings (recommended), or specify your own settings for the database server, the database name, or the SQL authentication credentials.
  18. In the Search Database section, you can either accept the default settings (recommended), or specify your own settings for the search database server, the database name, or the SQL Server authentication credentials.
  19. In the Index Server section, in Index Server, click the server on which you configured the Search service.  Note: If there is no index server listed in the Index Server section, then no server in your farm has been assigned the index server role. To assign the index server role to a server in your farm, follow the instructions in the "Configure the Search service" section earlier in this topic.
  20. In the SSL for Web Services section, click No.
  21. Click OK. Upon successful creation of the SSP, the Success page appears.
  22. On the Success page, click OK to return to the Manage this Farm's Core Services page.
Configure indexing settings
  1. On the SharePoint Central Administration home page, click the Application Management tab on the navigation bar.
  2. On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm's shared services.
  3. On the Manage this Farm's Shared Services page, click SharedServices1.
  4. On the Shared Services Administration page, in Search, click Search Settings.
  5. On the Configure Search Settings page, in the Crawl Settings section, click Default content access account.
  6. In the Default content access account section, in Account, Password, and Confirm Password, type the user name and password for the user account that you want to use to crawl content on your sites. This account must be a domain user account. It is recommended that you use the principle of least privilege and select a unique user account that cannot modify content and does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user account that you specify will be added to the Web application Full Read policy for your farm. The user name must be in the format DOMAIN\username.
  7. Click OK.
  8. In the Crawl Settings section, click Content sources.
  9. On the Manage Content Sources page, click Local Office SharePoint Server sites.
  10. On the Edit Content Source page, in the Crawl Schedules section, under Full Crawl, click Create schedule.
  11. In the Manage Schedules dialog box, configure schedule settings for full crawls of your content, and then click OK.
  12. In the Crawl Schedules section, under Incremental Crawl, click Create schedule.
  13. In the Manage Schedules dialog box, configure schedule settings for incremental crawls of your content, and then click OK.
  14. In the Start Full Crawl section, select the Start full crawl of this content source check box, and then click OK.
I faced this following issue since I did the .Net framework 3.5 install before installing the MOSS. Installing 2.0 prior to installing is completely fine. Yes this is wierd. Anyway, I couldn't get the import connection created & couldn't see the crawl log page.

An error occurred while validating or updating the directory service connection. No connection was added.

Solved the same by the following way - Trust me this works if you installed 3.5 before installing MOSS 2007 (It took 2 hour to find this):


http://support.microsoft.com/Default.aspx?id=962928


Also, there is a dazzling post on the entire installation of MOSS 2007 - http://www.datasprings.com/Resources/ArticlesInformation/OverviewonInstallingSharepoint2007/tabid/774/language/en-US/Default.aspx

Comments

Post a Comment

Popular posts from this blog

Linksys Wireless Connection Failure

By -
I configured the Linksys wireless router [WRT54G] couple of years before and it just worked great. I myself configured the password and everything worked great at my home. Anyone comes in home takes my password and it just worked great most of the time. all these were with windows server 2003 and Dell machaines. When I bought a new Hp DV9000 (XP) I had an issue connecting to the home wireless. I started browsing and found this solution: Issue : Couldn't connect to the selected connection. 1. Installed an update http://www.microsoft.com/downloads/thankyou.aspx?familyId=17d997d2-5034-4bbb-b74d-ad8430a1f7c8&displayLang=en Issue after the update : Acquiring Network address status and stayed there. Did the following after that: 1. Browsed http://192.168.1.1/ 2. used the user-id / password of the connection (default userid is empty & pwd is admin) 3. Navigated to wireless (Basic wireless settings), click Reset security and name your userid for SSID 4. Clicked save settings 5. cli
Read more

The security validation for this page is invalid. Click Back in your Web

By -
If you are getting the following error, while renaming the page title using publishingpage object " The security validation for this page is invalid. Click Back in your Webbrowser, refresh the page, and try your operation again ." Code Snippet: PublishingWeb publishingweb = PublishingWeb.GetPublishingWeb(newUri(" http://YourPortal/Plans/ ")); PublishingPage pp =publishingweb.GetPublishingPages()["Pages/TestArticle.aspx"]; pp.Title = e.Node.Text; pp.Update(); You should check for this : Navigate thru the followwing and turn the security validation Off Central Administration--->application management---->web application settings-->"turn security validation off"
Read more

Power Apps toPower Automate Error - The input body for trigger 'manual' of type 'Request' did not match its schema definition , the input String does not validate against the date

By Vinod Thachin -
While working with power Apps to Power automate, passing the Date time values as Text(DateTimeValue) throws error as below. The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'String '' does not validate against format 'date'.'. After checking the Microsoft documentation and few blogs i found out the date values should be passed as a formatted date time. TO pass the date time  we need to use following functions. Text(<<DateTimePicker>>.SelectedDate,"[$-en-US]yyyy-mm-dd") Even after passing the value i am still seeing the same issue and finally found out the default value ids sending as empty and formulae failing for empty values. So we need to make sure the Date Value should not go blank to the formulae and the value should be formatted using the formulae as above. Hope this helps.
Read more