Monday, January 28, 2008
WSS 3.0 enable search
To enable the search on a WSS Site, the following three actions need to be completed :
- In Central Administration / Operation / Services On Server ==> Start "Windows SharePoint Services Search" Service. (the first time you'll probably need to create a searchDatabase)
- In Central Administration / Application Management / Content Databases ==> Select the content database and set the searchserver
- Done!
Two Sites, one server, two versions of .Net framework, IIS 6.0. How to make this work?
the two following links helped me a lot in solving the problem :
http://weblogs.asp.net/owscott/archive/2006/05/30/ASPNet_5F00_regiis.exe-tool_2C00_-setting-the-default-version-without-forcing-an-upgrade-on-all-sites.aspx
http://weblogs.asp.net/owscott/archive/2005/07/29/421058.aspx
With the command "aspnet_regiis -i" executed in the folder of a certain .Net framework, you install this version of the dotNet framework on all the sites in IIS.
With the command "aspnet_regiis -sn W3SVC/2/ROOT/" you can install the framework on a certain site. 2 is the siteID. You can find the siteID by looking at the name of the logfiles. It should be something like : W3SVC781/***.log. 781 is the siteID.
Attention! In one appPool can execute a lot of sites, but they all must use the same version of the .Net framwork. If this is not the case, ... make an additional AppPool.
This solved the problem for me. All sites were able to execute again.
http://weblogs.asp.net/owscott/archive/2006/05/30/ASPNet_5F00_regiis.exe-tool_2C00_-setting-the-default-version-without-forcing-an-upgrade-on-all-sites.aspx
http://weblogs.asp.net/owscott/archive/2005/07/29/421058.aspx
With the command "aspnet_regiis -i" executed in the folder of a certain .Net framework, you install this version of the dotNet framework on all the sites in IIS.
With the command "aspnet_regiis -sn W3SVC/2/ROOT/" you can install the framework on a certain site. 2 is the siteID. You can find the siteID by looking at the name of the logfiles. It should be something like : W3SVC781/***.log. 781 is the siteID.
Attention! In one appPool can execute a lot of sites, but they all must use the same version of the .Net framwork. If this is not the case, ... make an additional AppPool.
This solved the problem for me. All sites were able to execute again.
