14 April, 2009

Usage Analysis Processing - Server Out of Memory error

In our company's project, We have Two enviornments Windows SharePoint Services and Microsoft office SharePoint Server 2007. Both are classified into 3 stages as Tes, QA and Production. In WSS 3.0 Test enviornment, when we tried to enable Usage Analysis processing, we got an error message :
"Server Out Of MemoryThere is no memory on the server to run your program. Please contact your administrator with this problem."

I can't find anything in the EVENT LOGS on the server that indicate an issue with this.
After doing lots of troubleshooting for more than 2 days, we found out the resolution.You can't believe it but the resolution is very simple and straightforward.

We found out that the application pool account was running under Network Service. We changed it to Domain admin account and after that did IISRESET.

Issue Resolved.
Cheers !

Note:-
The domain account should have the following rights as follows:-
1. It should be present in the WSS_WPG,WSS_ADMIN_WPG and IIS_WPG and Administrator group.
2.It should be present in the SQL SERVER Logins Section.
3. It should have DBCREATOR & SECURITY ADMIN Permissions in the SQL SERVER.

The application pool identity is essentially what the ASP .Net code of the site will be executing as. The user account used here must have the standard rights in order to run an application pool, and must obviously have rights to read and write to the SQL Server databases for the site.

Thanks...

How to configure Usage Analysis Processing on a Web server that is running Windows SharePoint Services 3.0

To turn on Windows SharePoint Services usage logging in an Office SharePoint Server farm, you must first turn on Usage Analysis Processing in Windows SharePoint Services 3.0, and then turn on Advanced Usage Analysis Reporting service in Shared Services Administration. To do this, follow these steps:

1.Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
2.On the Central Administration page, click Operations.
3.On the Operations page, under Logging and Reporting, click Usage Analysis Processing.
4.In the Logging Settings section, click to select the Enable logging check box.
5.In the Log file location box, type the location where you want to store the log file.The default location for the log file is \Program Files\Common Files\Microsoft Shared\Web Server Extension\12\Logs.
6.In the Number of log files to create box, type a number between 1 and 30. In general, use a number that is one to three times the number of database servers in your server farm, with a maximum number of 30 log files.
7.In the Processing Settings section, click to select the Enable usage analysis processing check box.
8.Under Run processing between these times daily, specify the range of times to start the usage analysis log processing.In the Start box, select the earliest time of day to start running log processing. In the End box, select the latest time to start running log processing.
9.Click OK.


Refferance:-
http://support.microsoft.com/kb/825541

How to configure Usage Analysis Processing on a Web server that is running Windows SharePoint Services 2.0

Usage analysis processing is set up through SharePoint Central Administration. To do this, follow these steps:

-Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
-Under Component Configuration, click Configure usage analysis processing.
-In the Logging Settings section, click to select the Enable logging check box.
-In the Log file location box, type the location where you want to store the log file.The default location for the log file is c:\Windows\system32\LogFiles\STS.
-In the Number of log files to create box, type a number between 1 and 30. In general, use a number that is one to three times the number of database servers in your server farm, with a maximum number of 30 log files.
-In the Processing Settings section, click to select the Enable usage analysis processing check box.
-Under Run processing between these times daily, specify the range of times to start the usage analysis log processing.In the Start box, select the earliest time of day to start running log processing. In the End box, select the latest time to start running log processing.
-Click OK.


Refferance:-
http://support.microsoft.com/kb/825541

Move, Lock, and Delete Site Collections

Microsoft has recently released an update to the Central Administration site that makes it easy to move a Site Collection between different Content Databases. The Batch Site Manager can be very handy if you need to break up your content across multiple Content Databases – possibly sitting on different SQL Servers.

Batch Site Manager is a feature that is designed to be used by SharePoint farm administrators to manage and administrate bulk operations that involve moving, locking or deleting one or more site collections within a single Web application. To access the Move, Lock, and Delete Multiple Site Collections page, click the Move, Lock, and Delete Site Collections link located on the Application Management page of Central Administration. The same tool also allows you to lock and delete site collections:

http://technet.microsoft.com/en-us/library/cc508852(TechNet.10).aspx

Download Microsoft SharePoint Administration Toolkit

Move site collections
Lock site collections
Delete site collections
Batch Site Manager files

10 April, 2009

How to rename a SharePoint Server machine name.

Renaming a MOSS server is tough job. If anything goes wrong along the way chances are that you need to reconfigure your whole MOSS environment.

Here are the steps to take, and the order in which to take them if you want to rename a server that has MOSS already installed and configured on it:

1.Change each alternate access mapping for your MOSS/WSS deployment in Central Administration:

-Open Central Administration, "Operations" Tab, "Alternate access mappings" link -Modify each mapping item to reflect your newly chosen server name

2.Use stsadm.exe to invoke the "renameserver" command option:

-Open a command prompt window

-cd "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN"

-stsadm -o renameserver -newservername -oldservername

3.Rename your Server via Change Name Operation in Windows Server 2003: Start Menu Control Panel System, "Computer Name" tab, "Change" button.

4.Input your new server name

5.Reboot the server NOW.

6.After reboot, open command prompt
-cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN -stsadm -o updatefarmcredentials -userlogin -password -iisreset /noforce

7.Check all application pool identities in IIS, update where the old machine name is still there.

8.If you already have a search index drop this, and rebuild it.

Your server is now renamed.