Delete or reset the site usage statistics for WSS 3.0 site

Steps :
•    On the Central Administration home page, click Operations.
•    On the Operations page, in the Logging and Reporting section, click Usage analysis processing.
•    On the Usage Analysis Processing page, in the Logging Settings section, uncheck Enable logging.
•    Click Ok
•    Then navigate to the location which you have specified to collect log data
•    Move those files to some other location
•    Disable Usage Reporting (this config is in SSP admin site)
•    Disable Usage Reporting (this is site collection feature)

Event ID: 10036 A database error occurred

Issue:

Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10036
Date: 4/16/2012
Time: 3:39:02 AM
User: N/A
Computer: CORP-SUR-IDX02
Description:
A database error occurred.

Source: Microsoft OLE DB Provider for SQL Server
Code: 1205 occurred 17 time(s)
Description: Transaction (Process ID 132) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Context: Application 'SSP'

Resolution:

1. Try restarting the Windows Sharepoint search service.
2. IISreset
3. Increase the intervals b/w the SharePoint crawls.

Installation of Windows Server 2003 R2

Installation Process Types:-1. BASIC
2. RIS (Remote Installation Services)
3. NETWORK

BASIC:-
Normal Installation Type, through Product Installation CD.

The Normal install consists of two types Attended and Unattended install.

Attended install is where you sit in front of the machines and install the whole operating system , this process may not be feasible if you are working with more than one machine, suppose you want to install OS on 15 machines you will be using the method called Unattended install where you will be creating an answer file, for the setup

• The answer file will be provided by the floppy drive, so the OS Compact Disk works on the Data provided by it

• To create answer file copy the file at drive \setup\support\tools\Deploy.cab\setup.manager.exe

• Copy it to another location on network then run the wizard and add the information like the CD key, regional settings, machine names to be given, organization name etc. then save it, the file will be saved anywhere like C:\setup\unattended.

• This will create 3 files
Unattended.bat
Unattended.txt
Unattended.udc

• Now to make sure the process runs successfully you will have to perform some changes as
Rename Unattended.bat to “winnt.bat”
Rename Unattended.txt to “winnt.sif”

• Now this will only work if you have the Boot priorities set to
I – CD ROM
II – Floppy Drive
III – HDD

RIS (Remote Installation Services)

RIS supports two types of operating system images:
 CD-based images (images created by using RISetup)
 Remote Installation Preparation (RIPrep) images.

The CD-based option is similar to setting up a server operating system directly from the Windows Server 2003 product CD, except that the source files reside on a RIS server.
You can create a RIPrep image from a server that is running Windows Server 2003 with SP2, and you can then deploy this image to other similar servers that are connected to the network.

Creating a CD-based (RIS setup) image to add to a RIS server
After you install RIS, perform the following steps to create the image and then add the image to your RIS server.

To create an image of Windows Server 2003 with SP2 and add it to your RIS server
1. Create an integrated version of the operating system with SP2.
2. To create an image, click Start, click Run, and then type: risetup.exe /add
3. The Remote Installation Services Setup Wizard appears. Follow the instructions in the wizard. When the Installation Source Files Location page prompts you for the image source, enter the path to the shared folder that contains the integrated version that you created in Step 1.
4. A box appears showing the progress of the installation. After the RISetup image is complete, you can install the image on each server as described in Remote Installation Services on the Microsoft TechCenter Web site.

Creating a Remote Installation Preparation (RIPrep) image to deploy to other servers

If you want to add additional programs or settings to your integrated installation image, you must have a CD–based image of Windows Server 2003 with SP2 on your RIS server. Note that you cannot use the /integrate option to integrate SP2 directly into an existing CD-based image or a RIPrep image.

To update existing RIPrep images
1. Use RIS to install the RISetup image on your computer.
2. Add the additional programs and settings that you want to include in the image.
3. Run RIPrep to create an image on the RIS server. For instructions on how to run RIPrep on RIS servers running Windows Server 2003, see:
• Remote Installation Services (http://go.microsoft.com/fwlink/?LinkId=36940 )

• Automating and Customizing Installations (http://go.microsoft.com/fwlink/?LinkId=44324 )

4. You can now deploy your RIPrep image to other servers.

NETWORK:-

Installing SP2 using source files that are located on a network share
To install SP2 from the network, first extract the installation files to a shared distribution folder. Then install SP2 on each computer using these files.
To install the service pack using a network share

1 Connect to the network or computer where you want to create the distribution folder.

2 In the shared folder, create a distribution folder.
For example, to create a distribution folder named WS2003SP2, type mkdir Drive:\WS2003SP2 at the command prompt (Drive: represents the drive where you want to store the distribution folder).

3 To extract the files to the distribution folder, type the following at the command prompt, where Path is the location of the distribution folder:
WindowsServer2003-KB914961-SP2-XXX-LLL.exe /X:Path

4 For each computer that you plan to update, back up the files and close programs before you continue (unless you plan to force programs to close during the installation).

5 To install the service pack from the shared distribution folder, run Update.exe. For example, to install from a distribution folder named WS2003SP2, type the following at the command prompt using the desired command-line options :
Drive:\WS2003SP2\i386\Update\Update.exe

6 Follow the instructions in the Setup Wizard.

7 After Update.exe has completed, restart the computer to complete the installation. SP2 will not be fully installed until you restart your computer.

8 If you disabled your antivirus software, enable it after you restart the computer.

Your License for Microsoft search server has expired in Search Server 2008

Troubleshooting Search server 2008:

Search server 2008 Express edition gives Error message as “Your License for Microsoft search server has expired”

Search server 2008 can also be used at your Organization even if you are not using SharePoint at all, in this scenario you can crawl your File share, Search server 2008 indexes the files then you can use the search center to insert the key words.
Now if you are using the Search server 2008 express edition and you face a problem while search as an error message as “Your License for Microsoft search server has expired”

You will have to check the following

• Check if the Help search that us Windows SharePoint Help search service and Office SharePoint search is running with same account
• Check the content access account
• Check if the help search is working
• In case it’s not or the accounts configured for both the services is different Stop and start the services using Services on server link under operations tab
• Then you are sure that the new databases are at work
• Then you will have to migrate to Add remove programs and locate the Search server Express and run a repair
• Then reboot the machine
• Then run the PS config wizard again
• Let it finish
• Launch the Search dashboard
• The search will not show any license errors now.

The path for the index location is not valid

"The path for the index location is not valid"

I recently faced this issue with the Sharepoint on the Central administration page that gives "The path for the index location is not valid" error message on the Manage search settings page on Application management

Reason:

================

The problem occurs when you have changed the default location of the index file path

Resolution:

================

+ Either you can try bringing the index location back to where it was

+ Try stopping and starting the Osearch service give it the new location, and start it again, to do this make command line your friend.

+ To stop and start WSS search with command line use http://technet.microsoft.com/en-us/library/cc288507.aspx

+ To stop and start Office search with command line use http://technet.microsoft.com/en-us/library/cc262920.aspx

+ Try giving WPG group as full permissions on the index file location folder

+ Also give permissions to the C:\windows\tasks folder

+ As its a system folder and it will not give you permissions to edit the attributes on the command prompt run attrib -s C:\windows\tasks the go to security tab and add permissions and then again on command prompt run attrib +s C:\windows\tasks, to get the system folder attributes in place

Assume that the new index location you have provided is Drive D,

so go to the D drive and add the network service and the Worker Process Group (WPG) group as the following permissions listed

Permissions:

Traverse Folder / Execute File, List Folder / Read Data, Read Attributes, Read Extended Attributes, and Read Permissions

And I bet it going to work, if you are wondering why, this is because O search is controlled by a service named Office server web services and this service runs with the service account as Network service.

you can determine this from the IIS