I had seen that sometimes when user is going to search something on site he get this error message: -
"The search request was unable to connect to the Search Service".
Why it is coming??? How it can be solved???
Is coming becuase of your web front end server is not able to search database. The must be either the user don't have permission to connect with database or Index server is not set for search. No issue we have some solutions by this we can get the results not the error message:-
Solution 1:-
Step 1
* Central Admin -> Application Management -> Office SharePoint Server Shared Services -> Create or Configure this farm's shared services
* Shared Services Provider (drop down) -> Edit Properties
* Edit Shared Services Provider -> Index Server: Verify the index server is set
Step 2
Single Server Farm
On the MOSS 2007 server:
* Start -> Run -> CMD -> stsadm.exe -o osearch -action stop
* Start -> Run -> CMD -> stsadm.exe -o osearch -action start -role queryindex
Hopefully your search will be start.
If not then try another solution:
Solution 2:-
1. Go to Run ->type inetmgr.
2. Open the application pools.
3. Select the application pool related to Shared Service.
4. Right click on it and select properties.
5. On Identity tab change the Identity from Network Service to Configurable with passing your User name(with your domain name) and password .
6. Go to run and iisreset.
Enjoy Search Results!!!
(If still not getting the results then check search services on the farm they are start or stop if stop then must start them)
Sunday, May 18, 2008
How to delete a default SSP (Shared Service Provider) in MOSS 2007
I had one SSP sites on my farm. I found that there is something wrong with this SSP site. So i decide to delete this SSP site. I go to Central Administration site and click on the Shared Services Provider. Here i got the link of my SSP site. When i go to delete the SSP what is this!!! there is no link to delete the Default SSP site.
I googled up and found on some site the command by which i can delete my default SSP site. Oh god finally i saved myself.
So here i am putting this command to help out the SharePoint guys.
To delete it, either type in the URL: http:///_admin/deletessp.aspx?sspId=??? or
use stsadm –o deletessp –title
Enjoy!!!!!!
Note:- If you will delete default SSP may be you need to reconfigure the whole Shared Service Provider again. So be careful.
I googled up and found on some site the command by which i can delete my default SSP site. Oh god finally i saved myself.
So here i am putting this command to help out the SharePoint guys.
To delete it, either type in the URL: http:///_admin/deletessp.aspx?sspId=??? or
use stsadm –o deletessp –title
Enjoy!!!!!!
Note:- If you will delete default SSP may be you need to reconfigure the whole Shared Service Provider again. So be careful.
Unfortunately if you deleted the SSP Admin Site Collection…
Hey - we’ve all made mistakes. We all know that "oh my god" moment after we realize what we’ve done! Often times this occurs right after we click a friendly “Are you sure??” dialog। Of course I’m sure - if I wasn’t sure I wouldn’t have chosen to do it in the first place! Stupid computer।
Anyway, I recently had a situation where someone (honestly, in this case it wasn’t me) accidentally deleted the Site Collection for the SSP admin site (/ssp/admin). Since this was for a SharePoint farm in production I really didn’t want to have to re-create the entire SSP but I couldn’t figure out how to just re-create the site collection itself. I figured there had to be a site template for the site but since it didn’t show up in the Create Site Collection UI I went and looked on disk. Sure enough, a site template exists for the SSP Admin site. It’s called OSRV.
So to create a new SSP admin site, run this command line.
stsadm.exe -o createsite -url http://:/ssp/admin -owneremail -ownerlogin -sitetemplate OSRV#0 -title "Shared Services Administration: "
This might take a little while to complete, but it does eventually finish.
Next you need to edit the SSP to point to the recreated site.
stsadm.exe -o editssp -title "" -sspadminsite http://:/ssp/admin
That’s it। You should be back up and running।
Anyway, I recently had a situation where someone (honestly, in this case it wasn’t me) accidentally deleted the Site Collection for the SSP admin site (/ssp/admin). Since this was for a SharePoint farm in production I really didn’t want to have to re-create the entire SSP but I couldn’t figure out how to just re-create the site collection itself. I figured there had to be a site template for the site but since it didn’t show up in the Create Site Collection UI I went and looked on disk. Sure enough, a site template exists for the SSP Admin site. It’s called OSRV.
So to create a new SSP admin site, run this command line.
stsadm.exe -o createsite -url http://
This might take a little while to complete, but it does eventually finish.
Next you need to edit the SSP to point to the recreated site.
stsadm.exe -o editssp -title "
That’s it। You should be back up and running।
Step by Step Install and configure the Sharepoint Server
This is my first blog so i just want to start the things from the base. so lets start with the installation and configuration of Share Point. Basically i am interested step by step explanation with pictures so that beginner should feel relax and nobaody face any problem regarding installation and configuration.
May be this bolg is very very long for the person who is just reading this as an artical but will be very useful who will do this practical.
Lets start!!!!!
Install SharePoint
The first step is to install SharePoint on all SharePoint servers in your SharePoint farm.
1. Run the SharePoint install program
2. Enter your license key and accept the licence agreement
3. Click Advanced when asked what installation type you want
4.
5. Next, on the Server Type screen, choose Complete
6.
7. Click Install Now
8. Once the installation is complete, leave the "Run the SharePoint Products and Technologies Configuration Wizard now" checkbox checked and click Close
Configure SharePoint
1. If it's not already running, run the SharePoint Products and Technologies Configuration Wizard.
2. Click Next on the first screen of the wizard.
3. On the Connect to a server farm page, choose No, I want to create a new server farm
4.
5. On the Database Configuration screen, enter the name of the SQL Server which will host your SharePoint databases. If you want to change the name of your configuration database you can but I recommend a consistant prefix for all SharePoint databases. In this walkthrough we will use SP_ as the prefix for all database names.
6. Enter the username and password for your chosen Farm Account and click Next
7.
8. Next you must configure the SharePoint Central Administration website. This will be the web-based application that you use to configure and manage SharePoint. I recommend choosing a specific port number that will be easy to remember for this site. So check the Specify a port number checkbox and enter a value you will remember. This walkthrough does not deail with configuring Kerberos so leave NTLM checked and click Next
9.
10.Finally review your settings and if everything is correct, click Next. SharePoint will now attempt to create the intial databases and configure itself on the current server. This can take a while.
Post-Install Configuration
At this point SharePoint is installed, but it cannot be used because it requires additional configuration. The next steps will include starting the required services, creating a Shared Services Provider, and creating your first Site Collection.
Starting the Services
1. If it isn't already open, launch SharePoint Central Administration from the start menu.
2. Click on the Operations tab and choose Services on Server
3. Locate the Office SharePoint Server Search item in the list of services and click Start.
4.
5. You will now be taken to the search configuration screen. Check the first two boxes and enter an email address for the search contact email address.
6. Next, enter the credentials for the Farm Account in the Farm Search Service Account area.
7. Leave the other options on this screen at their default settings.
8.
9. Next, back on the Services on Server page, locate the Document Conversions Load Balancer Service and click Start
10.Next, locate the Document Conversions Launcher Service and click Start
11.
12.On the Launcher Service Settings page, for the Load Balancer, choose the current server from the drop down box and click OK.
13.Now, back on the Services on Server page, locate Excel Calculation Services and click Start.
14.At this point your service list should look like this:
15.
Email Settings
1. Go back to the Operations tab in SharePoint Central Administration
2. Click on the Outgoing e-mail settings link
3. Enter the address or name for your SMTP relay server. Be sure that the server you choose will accept email relay from your SharePoint server. Also enter a From address and Reply-to address here. Then click OK
Create the Shared Services Provider
1. On the left navigation bar (Quick Launch) click Shared Services Administration
2. Now click New SSP
3. On the next screen enter a name for your new SSP. Typically you can just call this SharedServices.
4. Next we must create a web application to host the SSP Administration site (similar to central administration, but to manage the SSP). Click Create a new Web application
5.
6. First enter a name for the IIS web site. Best practice is to use the same name as you chose for your SSP.
7. Specify an easy to remember port number for this website.
8. Optionally, change the last portion of the path to be the name of the IIS web site instead of the port number. I find that this makes it easier to find if you ever need to modify the web.config or add files to the bin directory.
9.
10.You can leave the options in Security Configuration at their default settings.
11.Scroll to the Application Pool section
12.For the Application pool name, enter the same name as you used for your SSP
13.In the account section, enter the username and password for your Farm Account
14.
15.Scroll to the Database Name and Authentication section.
16.Enter the name of your database server.
17.For the database name, follow your database naming conventions but since this will be a SSP database, add SSP_ after your prefix. The database name should be something like SP_SSP_Content
18.
19.Click OK
20.Once the operation finishes you will be back on the New Shared Services Provider screen. You should see something like this:
21.
22.Scroll to the My Site Location section. We are going to host My Sites in the same web application as our portal so again we need to create a new web application. Click Create a new Web application
23.
24.First enter a name for the IIS web site. This time, name the application something like SharePointPortal or Portal
25.Use port 80
26.Optionally, change the last portion of the path to be the name of the IIS web site instead of the port number. I find that this makes it easier to find if you ever need to modify the web.config or add files to the bin directory.
27.
28.You can leave the options in Security Configuration at their default settings.
29.Scroll to the Application Pool section
30.For the Application pool name, enter the same name as you used for the IIS Web site above
31.This time, in the account section enter the username and password for your Portal Account
32.
33.Scroll to the Database Name and Authentication section.
34.Enter the name of your database server.
35.For the database name, follow your database naming conventions. The database name should be something like SP_SharePointPortal_Content.
36.
37.Click OK
38.Once the operation finishes you will be back on the New Shared Services Provider screen. Be sure to select your new web application for the My Site Location web app and enter a relative URL like /mysite.
39.
40.In the SSP Service Credentials section, enter the username and password for your Farm Account
41.In the SSP Database section enter your database server name and a database naming conforming to your naming conventions, but using the SSP_ convention for SSP databases. It should be something like SP_SSP_DB 42.
43.In the Search Database section enter a name for the SSP search database. Again, it should use your prefix and SSP_ and should look something like SP_SSP_SearchDB
44.
45.You can leave the rest of the settings at their default values and click OK
46.Once the operation is complete your Shared Services Provider will be set up.
Configure the Default Crawl Account
3. In the Search section, click the Search settings link
4. Click the Default content access account link
5.
6. Enter the credentials for your Crawl Account and click OK
8. In the Templage Selection section, click Publishing and choose Collaboration Portal (For Internet Facing site always prefer Publishing portal or publishing site)
9. Next, enter up to two users who will be Site Collection Administrators. These users will have full administrative rights to this site.
10.
11.Click OK. Once the operation is complete SharePoint will be ready to use.
May be this bolg is very very long for the person who is just reading this as an artical but will be very useful who will do this practical.
Lets start!!!!!
Install SharePoint
The first step is to install SharePoint on all SharePoint servers in your SharePoint farm.
1. Run the SharePoint install program
2. Enter your license key and accept the licence agreement
3. Click Advanced when asked what installation type you want
4.
5. Next, on the Server Type screen, choose Complete
6.
7. Click Install Now
8. Once the installation is complete, leave the "Run the SharePoint Products and Technologies Configuration Wizard now" checkbox checked and click Close
Configure SharePoint
1. If it's not already running, run the SharePoint Products and Technologies Configuration Wizard.
2. Click Next on the first screen of the wizard.
3. On the Connect to a server farm page, choose No, I want to create a new server farm
4.
5. On the Database Configuration screen, enter the name of the SQL Server which will host your SharePoint databases. If you want to change the name of your configuration database you can but I recommend a consistant prefix for all SharePoint databases. In this walkthrough we will use SP_ as the prefix for all database names.
6. Enter the username and password for your chosen Farm Account and click Next
7.
8. Next you must configure the SharePoint Central Administration website. This will be the web-based application that you use to configure and manage SharePoint. I recommend choosing a specific port number that will be easy to remember for this site. So check the Specify a port number checkbox and enter a value you will remember. This walkthrough does not deail with configuring Kerberos so leave NTLM checked and click Next
9.
10.Finally review your settings and if everything is correct, click Next. SharePoint will now attempt to create the intial databases and configure itself on the current server. This can take a while.
Post-Install Configuration
At this point SharePoint is installed, but it cannot be used because it requires additional configuration. The next steps will include starting the required services, creating a Shared Services Provider, and creating your first Site Collection.
Starting the Services
1. If it isn't already open, launch SharePoint Central Administration from the start menu.
2. Click on the Operations tab and choose Services on Server
3. Locate the Office SharePoint Server Search item in the list of services and click Start.
4.
5. You will now be taken to the search configuration screen. Check the first two boxes and enter an email address for the search contact email address.
6. Next, enter the credentials for the Farm Account in the Farm Search Service Account area.
7. Leave the other options on this screen at their default settings.
8.
9. Next, back on the Services on Server page, locate the Document Conversions Load Balancer Service and click Start
10.Next, locate the Document Conversions Launcher Service and click Start
11.
12.On the Launcher Service Settings page, for the Load Balancer, choose the current server from the drop down box and click OK.
13.Now, back on the Services on Server page, locate Excel Calculation Services and click Start.
14.At this point your service list should look like this:
15.
Email Settings
1. Go back to the Operations tab in SharePoint Central Administration
2. Click on the Outgoing e-mail settings link
3. Enter the address or name for your SMTP relay server. Be sure that the server you choose will accept email relay from your SharePoint server. Also enter a From address and Reply-to address here. Then click OK
Create the Shared Services Provider
1. On the left navigation bar (Quick Launch) click Shared Services Administration
2. Now click New SSP
3. On the next screen enter a name for your new SSP. Typically you can just call this SharedServices.
4. Next we must create a web application to host the SSP Administration site (similar to central administration, but to manage the SSP). Click Create a new Web application
5.
6. First enter a name for the IIS web site. Best practice is to use the same name as you chose for your SSP.
7. Specify an easy to remember port number for this website.
8. Optionally, change the last portion of the path to be the name of the IIS web site instead of the port number. I find that this makes it easier to find if you ever need to modify the web.config or add files to the bin directory.
9.
10.You can leave the options in Security Configuration at their default settings.
11.Scroll to the Application Pool section
12.For the Application pool name, enter the same name as you used for your SSP
13.In the account section, enter the username and password for your Farm Account
14.
15.Scroll to the Database Name and Authentication section.
16.Enter the name of your database server.
17.For the database name, follow your database naming conventions but since this will be a SSP database, add SSP_ after your prefix. The database name should be something like SP_SSP_Content
18.
19.Click OK
20.Once the operation finishes you will be back on the New Shared Services Provider screen. You should see something like this:
21.
22.Scroll to the My Site Location section. We are going to host My Sites in the same web application as our portal so again we need to create a new web application. Click Create a new Web application
23.
24.First enter a name for the IIS web site. This time, name the application something like SharePointPortal or Portal
25.Use port 80
26.Optionally, change the last portion of the path to be the name of the IIS web site instead of the port number. I find that this makes it easier to find if you ever need to modify the web.config or add files to the bin directory.
27.
28.You can leave the options in Security Configuration at their default settings.
29.Scroll to the Application Pool section
30.For the Application pool name, enter the same name as you used for the IIS Web site above
31.This time, in the account section enter the username and password for your Portal Account
32.
33.Scroll to the Database Name and Authentication section.
34.Enter the name of your database server.
35.For the database name, follow your database naming conventions. The database name should be something like SP_SharePointPortal_Content.
36.
37.Click OK
38.Once the operation finishes you will be back on the New Shared Services Provider screen. Be sure to select your new web application for the My Site Location web app and enter a relative URL like /mysite.
39.
40.In the SSP Service Credentials section, enter the username and password for your Farm Account
41.In the SSP Database section enter your database server name and a database naming conforming to your naming conventions, but using the SSP_ convention for SSP databases. It should be something like SP_SSP_DB 42.
43.In the Search Database section enter a name for the SSP search database. Again, it should use your prefix and SSP_ and should look something like SP_SSP_SearchDB
44.
45.You can leave the rest of the settings at their default values and click OK
46.Once the operation is complete your Shared Services Provider will be set up.
1. On the left nav bar you should now see a link to your SSP under the Shared Services Administration header. Mine is called SharedServices because that's the name I chose when creating the SSP. Click this link.
2.
2.
3. In the Search section, click the Search settings link
4. Click the Default content access account link
5.
6. Enter the credentials for your Crawl Account and click OK
Create the Portal Site Collection
1. Finally we need to create a new Site Collection for the portal. Navigate back to SharePoint Central Administration
2. Click on the Application Management tab
3. Under SharePoint Site Management click Create site collection
4. First, be sure to choose the Web Application that is using port 80. By default one of your other web applications may be selected such as the Central Administration web app or SSP Admin web app.
5. Next, enter a name for your new site collection (you can change this later)
6. For the Web Site Address, choose the root /
7.
2. Click on the Application Management tab
3. Under SharePoint Site Management click Create site collection
4. First, be sure to choose the Web Application that is using port 80. By default one of your other web applications may be selected such as the Central Administration web app or SSP Admin web app.
5. Next, enter a name for your new site collection (you can change this later)
6. For the Web Site Address, choose the root /
7.
8. In the Templage Selection section, click Publishing and choose Collaboration Portal (For Internet Facing site always prefer Publishing portal or publishing site)
9. Next, enter up to two users who will be Site Collection Administrators. These users will have full administrative rights to this site.
10.
11.Click OK. Once the operation is complete SharePoint will be ready to use.
Subscribe to:
Posts (Atom)
