Sharepoint 2010

SharePoint

Tag Archives: sharepoint

High Memory and CPU Usage by fixmlindex.exe FAST 2010 for SharePoint

 

I had the FAST Search server 2010, SharePoint 2010 and SQL Server 2008 R2 installed on a single demo machine. Though this is not something which Microsoft recommends, it was very important when you visit clients for showing a demo showcasing the capacity of FAST.

When I tried to verify the memory and CPU consumption in the Task Manager, it did not took a long time to understand that the SQL Server and a FAST Search Server exe was one of the major culprits in bringing the system down on many of the occasions.

It appeared that continuously adding managed properties continuously across all the demos was leading to a continuous update in the index for the properties, which led to a high memory and CPU usage.

To overcome this, you should perform the following steps:

  1. Perform complete schema update
  2. In the FAST powershell run the command “nctrl stop”
  3. delete the file  “etc\config_data\Schema\webcluster\summaryclasses.xml”
  4. In the FAST powershell run the command “nctrl start”

This should handle most of the issues  related with high CPU and memory usage.

Advertisements

Unknown server tag ‘asp:ListView’ error with SharePoint 2010

Problem Statement

I had created a SharePoint 2010 Web Part which was using the ASP.NET List view. The code compiled fine and was deployed properly. However, when I was trying to add the web part to the Web part page, I was getting the following error:

Unknown server tag ‘asp:ListView’

Resolution

Open the web.config and add the following entry in <Controls>

<controls>
       <add tagPrefix=”asp” namespace=”System.Web.UI.WebControls” assembly=”System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/>
  </controls>

Indexing Very Large Files in SharePoint 2010

 The limitation of indexing Files greater than 16 MB in size still exists in SharePoint 2010. The limitation was enforced to avoid network clogging and improve SharePoint performance.

In all such scenarios, where the file format is Compatible to SharePoint and the size of the file is larger than the max threshold size, the indexer is able to index the metadata of the file. however, the content of the file is not indexed.

For all files which are smaller than 16 MB in size and the file format is compatible to SharePoint, the content as well as the metadata of the file is indexed.

The major problem is that in SharePoint 2007, all such scenarios where the File Size was greater than 16 MB, were logged in as warning in the Crawl logs. However, there is no such warning generated in case of SharePoint 2010 and hence it is very difficult to understand the issue.

This whole behavior is guided by two registry values:

  • MaxDownloadSize :  This specifies the maximum size of the document text that is filtered.
  • MaxGrowthFactor : This specified how large the output of the index filter can be.

 

By default , the MaxDownloadSize is 16 MB and the MaxGrowthFactor is 4 MB in Size. This basically implies that:

  • The maximum size when you index file share will be 16 * 6 = 64 MB
  • The maximum size when you index document on the web site will be 16 MB.

 

Before SharePoint 2010, this settings were modified by modifying the registry information at

HKEY_LOCAL_MACHINE -> SOFTWARE –> Microsoft –> Office Server -> 12.0 –> Search –> Global –> Gathering Manager

However for some reasons these settings don’t persist when applied in SharePoint 2010 environment. you need to alter the settings using the PowerShell.

image

 

The max value supported by “MaxDownloadSize” is 2 GB.

Execute VSeWSS Projects in Visual Studio 2010

 

The solutions developed in VSeWSS extensions are not directly portable into Visual Studio 2010.

To Run the VSeWSS Projects in Visual Studio 2010, an import tool has been released in MSDN which helps in executing the VseWSS Projects. This tool gets installed as a Visual Studio 2010 add in and provides a new SharePoint Project Template .

The tool is available at the following location:

http://code.msdn.microsoft.com/VSeWSSImport

 

All the discussions related with this tool is available at

http://code.msdn.microsoft.com/VSeWSSImport/Thread/List.aspx

SharePoint 2010 Recycle Bin

The recycle bin in SharePoint is synonymous to Recycle bin in windows and helps the users in recovering files which have been deleted accidentally.

The files in the recycle bin can either be recovered or can be deleted after a pre defined period of time.

 

Recycle Bin Stages

SharePoint supports two levels of Recycle bin. The initial or First level Recycle bin comes in picture when the user deletes an item from a list. Once the item is deleted again from the First level of Recycle bin it moves to the second stage of Recycle bin.

 

image_thumb[1]

 

image_thumb[8]

Access Restrictions on Recycle Bin

The restoration access on the First Stage Recycle Bin is available to all the site users. However, restoration access on the second stage Recycle Bin is available only to the Site Collection Administrators.

 

Number of Recycle Bin

There is one First Stage recycle bin available per site in a site collection. However, there is only one Second Stage Recycle Bin available per Site Collection.

 

Item not available in Recycle Bin

If you try to find an item in the recycle bin and fail to locate it then you need to verify the following :

  1. The contents in the recycle bin are driven by the access control. The user who has deleted the content will be able to see the content in the recycle bin. Other users will not be able to see the items in the recycle bin.
  2. If you have deleted a top level item like a folder or a list, and try to find a document available at an inner location, then the item will not be viewable. By default the Recycle bin shows the top level content and does not have the capability to show the items in a tree structure or drill down mode.
  3. The contents in the recycle bin contains only the items within the site. A deleted site is outside the scope of the Recycle bin and is not available for deletion.
  4. The recycle bin contains the items for a pre defined period which can be set from the Web Application –> General Settings. if the thresh hold is crossed, the item is deleted permanently.

 

Configure Recycle Bin

Recycle Bin can be configured from the central administration.

  1. Click on Manage Web Applications
  2. Select the Web Application for which the recycle bin configuration needs to be configured.
  3. Click on General Settings in the Ribbon –> General Settings from the drop down as well.

image_thumb[6]

 

Remove “Recycle Bin” Link from SharePoint Site

  1. Open the SharePoint Designer
  2. Check out the master page
  3. Open the master page in SharePoint Designer 
  4. Find the </Head> tag
  5. Add the following text above the <HEAD> tag.
   1: <style> 

   2: .s4-specialNavLinkList

   3: {

   4:     display:none!important;

   5: }

</style> 

6. Check in the master page

SharePoint 2010 Migration–IN place Upgrade Part II

During an in place upgrade process, the entire SharePoint 2007 box is upgraded to SharePoint 2010. The up gradation process upgrades the entire SharePoint 2007 installation.

 

In Place upgrade for SharePoint standalone Installation

For upgrading a SharePoint standalone installation, the process is as follows:

  1. The installation of SharePoint 2010 is executed on the Standalone machine. This process kicks off the installation process in the in-place upgrade mode directly.
  2. Install the Language Packs that are used by the Site Collections.
  3. Once the installation process is complete, the “SharePoint Configuration Wizard” is run. This upgrades the server, central administration configuration database, services and Content Databases.
  4. Once the configuration wizard is executed, a timer service is created which upgrades all the site collection in the server.

Points to Consider

  1. Once the upgrade process starts, there is no rollback.
  2. The process takes the Web Server offline for the upgrade process and brings it online only when the process is complete.

SharePoint 2010 Migration – Part I

There are many types of migration opportunities available for migrating to Sharepoint 2010:

1. Migrate from Sharepoint 2003 to Sharepoint 2010

2. Migrate from Sharepoint 2007 to Sharepoint 2010

3. Migrate from other content management systems to Sharepoint 2010

There are many approaches of migrating from older version of sharepoint to sharepoint 2010.

1. In-Place Upgrade

2. Gradual Upgrade

3. Database migration (advanced)

4. Site and List Definition upgrade

However, till date there is no such pre defined approach for migrating to Sharepoint 2010. It mostly depends on the judgment of the administrator who is migrating the sharepoint site.

Feasibility verification for migrating to Sharepoint 2010

To understand the feasibility of migration, we can take the help of steam command. This command generates a HTML report for the same.

Syntax

stsadm -o preupgradecheck

   -[rulefiles <rule file>]

   -[listrulefiles]

   -localonly

Preupgradecheck

This command was first introduced with wss 3.0 sp2. This command is intended to run a set of rules that will assist the administrators to prepare the existing sharepoint 2007 installation to a future sharepoint 2010 version.

The parameter –rulefiles takes a valid rule file and is an optional parameter. It requires a quoted, delimited (comma or semicolon) list of rule file names. By default this command is run for all the available rule files. The rule files are available in the 12 hive\config\preupgradecheck folder.

The parameter –listrulefiles lists all rule files without executing the check routine. This is also an optional parameter.

The parameter –localonly is a required parameter and checks the local server with the rules marked as local only and evaluates them.

Temporary Database for Analysis

Once you run this command it creates a tmpdb_preupgradecheck_guid and stores all the analysis information over there before flushing out the information in the xml and html reports.

After the reports are generated and the command is completed, the databases are deleted by themselves.

Result

Once the command is run, it generates an xml and html based report to guide you deeper in understanding the approaches for migration. It generates 3 files namely

  1. OssPreUpgradeCheck.xml
  2. OssPreUpgradeCheck.xml
  3. Preupgradecheck.xml files

What if any check fails

You can check the microsoft knowledgebase for corrective actions.

http://support.microsoft.com/kb/960577