RSS

Category Archives: administration

Configuring SharePoint 2013 Search Topology on Production Environment


Introduction

When you create Search Service application from central administration , a default search topology will be created automatically where all Search components are assigned to the server which is running the Central Administration but  in multi servers farm scenario you need to change this topology using PowerShell.

Sample Scenario

In the following scenario I’m using 6 search servers. You can change according to your requirement.

  • 2 Front end servers – running the Query Processing component to handle search query requests from user.
  • 4 Back end Servers – running rest of the search components

SearchTopology

Before You Begin

  1. Make sure you have created a Search service application from central admin
  2. Make sure currently logged user is added as admin in Search service application
  3. Make sure index files are empty, Navigate to search service application administration and see Searchable Item appears as 0

Start configuration

Step 1: Prepare the Topology Variables

$hostA = Get-SPEnterpriseSearchServiceInstance -Identity "SERVER1"

$hostB = Get-SPEnterpriseSearchServiceInstance -Identity "SERVER2"

$hostC = Get-SPEnterpriseSearchServiceInstance -Identity "SERVER3"

$hostD = Get-SPEnterpriseSearchServiceInstance -Identity "SERVER4"

$hostE = Get-SPEnterpriseSearchServiceInstance -Identity "SERVER5"

$hostF = Get-SPEnterpriseSearchServiceInstance -Identity "SERVER6"

 

Start-SPEnterpriseSearchServiceInstance -Identity $hostA

Start-SPEnterpriseSearchServiceInstance -Identity $hostB

Start-SPEnterpriseSearchServiceInstance -Identity $hostC

Start-SPEnterpriseSearchServiceInstance -Identity $hostD

Start-SPEnterpriseSearchServiceInstance -Identity $hostE

Start-SPEnterpriseSearchServiceInstance -Identity $hostF

Note: Wait for a while till above instances get started and proceed below to verify status

Step 2: Check Service status

Get-SPEnterpriseSearchServiceInstance -Identity $hostA

Get-SPEnterpriseSearchServiceInstance -Identity $hostB

Get-SPEnterpriseSearchServiceInstance -Identity $hostC

Get-SPEnterpriseSearchServiceInstance -Identity $hostD

Get-SPEnterpriseSearchServiceInstance -Identity $hostE

Get-SPEnterpriseSearchServiceInstance -Identity $hostF
NOTE: Make sure status is online for all instance, then proceed to next

Step3 : Setting up Topology

NOTE: Make sure below mentioned root directory is created manually on all servers including central admin server

$ssa = Get-SPEnterpriseSearchServiceApplication

$newTopology = New-SPEnterpriseSearchTopology -SearchApplication $ssa

NEW-SPENTERPRISESEARCHADMINCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTA

NEW-SPENTERPRISESEARCHCRAWLCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTA

NEW-SPENTERPRISESEARCHCONTENTPROCESSINGCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTA

NEW-SPENTERPRISESEARCHANALYTICSPROCESSINGCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTA

 

NEW-SPENTERPRISESEARCHADMINCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTB

NEW-SPENTERPRISESEARCHCRAWLCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTB

NEW-SPENTERPRISESEARCHCONTENTPROCESSINGCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTB

NEW-SPENTERPRISESEARCHANALYTICSPROCESSINGCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTB

 

 

NEW-SPENTERPRISESEARCHQUERYPROCESSINGCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTC

NEW-SPENTERPRISESEARCHINDEXCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTC -INDEXPARTITION 0 -RootDirectory “E:\SearchIndex”

 

NEW-SPENTERPRISESEARCHQUERYPROCESSINGCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTD

NEW-SPENTERPRISESEARCHINDEXCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTD -INDEXPARTITION 0 -RootDirectory “E:\SearchIndex”

 

NEW-SPENTERPRISESEARCHQUERYPROCESSINGCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTE

NEW-SPENTERPRISESEARCHINDEXCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTE -INDEXPARTITION 1 -RootDirectory “E:\SearchIndex”

 

NEW-SPENTERPRISESEARCHQUERYPROCESSINGCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTF

NEW-SPENTERPRISESEARCHINDEXCOMPONENT -SEARCHTOPOLOGY $NEWTOPOLOGY -SEARCHSERVICEINSTANCE $HOSTF -INDEXPARTITION 1 -RootDirectory “E:\SearchIndex”

Step 4: Activate The Topology

SET-SPENTERPRISESEARCHTOPOLOGY -IDENTITY $NEWTOPOLOGY

Step 5: Verify the Topology

GET-SPENTERPRISESEARCHTOPOLOGY -SEARCHAPPLICATION $SSA

Step 6 : Verify Each Component

GET-SPENTERPRISESEARCHSTATUS -SEARCHAPPLICATION $SSA -TEXT
 

Tags: ,

Sharepoint “Workflow Auto Cleanup” mystery


Does anyone know that SharePoint workflow history is getting deleted after 60days. By default there is a timer job called “Workflow Auto Cleanup” associated with your web application which will delete all your workflow task history after 60 days  if the status is  Completed or Cancelled.

Now the question is, Does it really deletes whole workflow history?

No, Technically, the workflow history is not deleted. The association between the workflow (what you see on the workflow status page) and the history list is removed. This is done for performance reasons. Once a workflow is completed, by default the connection between the workflow and the workflow history is deleted after 60 days.

Is it Possible to disable this timer job?

Yes, You can disable the “Workflow Auto Cleanup” timer job if you wish to keep the workflow data. however, this is not really recommended due to the potential impact to performance of allowing these lists to grow indefinitely.

To disable automatic workflow cleanup follow below steps

  • From Central Administration, click the Monitoring tab 
  • On the Monitoring page, click Review job definitions.
  • On the Timer Job Definitions page, click Workflow Auto Cleanup to edit the appropriate timer job.
  • On the Edit Timer Job page, click Disable and then click OK to disable the Workflow Auto Cleanup feature.

NOTE: If you later decide that you want to enable automatic workflow cleanup, access this page again and click Enable to enable automatic workflow cleanup.

What is the alternate solution to audit my workflows?

Unfortunately, this auditing report is not available out of the box. However, a custom audit report can be created in Visual Studio in order to extend the auditing functionality to include workflows.Read here

 

Tags: , ,

Manually run PSCONFIG.exe after Installing SharePoint 2010 Patches


Patching  SharePoint 2010  is a two-step process now.

  1. First updated patch binaries has to be installed
  2. Then psconfig.exe must be run manually to update the SharePoint databases.

In order to update the SharePoint databases, you must manually run the PSconfig.exe utility. Follow below steps:

1. Open an command prompt as adminitrator.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

Note: The sharepoint site will be inaccessible while the command is running. It is best to run the command after office hours.

Known Issues:

Sometimes you might face following error: Sharepoint 2010 Product configuration wizard failing at step 9/10. below is the fix for it.

Solution

  • try clearing the cache.ini
  • you can find it in location C:\ProgramData\Microsoft\SharePoint\Config\GUId
  • go inside the GUID and look for cache.ini
  • reset the value to 1
  • run the command stsadm -o execadmsvcjobs
  • try running the below command
  • psconfig.exe -cmd upgrade -inplace b2b -wait -force
 
1 Comment

Posted by on October 17, 2012 in administration, Sharepoint Server 2010

 

Tags: ,

SharePoint 2010 Version Build Numbers


Last updated on: June 23 ,2011

Build

Release

Component

Download Link

14.0.4763.1000 RTM All components Download
14.0.4762.1000 RTM Farm Build Version
14.0.5114.5003 June 2010 CU SharePoint Foundation 2010 KB2028568
14.0.5114.5003 June 2010 CU Microsoft Shared Components KB2281364
14.0.5114.5003 June 2010 CU Microsoft SharePoint Portal KB983497
14.0.5114.5003 June 2010 CU Microsoft User Profiles
14.0.5114.5003 June 2010 CU Microsoft Search Server 2010 Core
14.0.5114.5003 June 2010 CU Microsoft Web Analytics Web Front End Components KB2204024
14.0.5123.5000 August 2010 CU SharePoint Foundation​ 2010 KB2352346
14.0.5123.5000 August 2010 CU SharePoint Server 2010 KB2352342
14.0.5128.5000

October 2010 CU​ SharePoint Foundation​ 2010 KB2394323
14.0.5128.5000​ October 2010 CU​ SharePoint Server 2010​ KB2394320
14.0.5130.5002​ ​December 2010 CU SharePoint Foundation 2010

KB2459125
14.0.5130.5002​

December 2010 CU​ SharePoint Server 2010​ KB2459257
14.0.5136.5002​ February 2011 CU​ SharePoint Foundation 2010

KB2475880​
14.0.5136.5002​ February 2011 CU​ SharePoint Server 2010​ KB2475878
14.0.5138.5000 ​April 2011 CU ​SharePoint Foundation 2010 KB2512804​
14.0.5138.5000 ​April 2011 CU SharePoint Server 2010​ KB2512800
14.0.5138.5000 ​April 2011 CU ​Project Server 2010 KB2512801

Here is the reference to terminologies used

 

Tags: ,

Backup and Restore Strategies in MOSS 2007 by Sahil Malik


Here is a very informative article for MOSS  administrators about Backup and Restore in MOSS 2007.

http://blah.winsmarts.com/2007-10-Backup_and_Restore_Strategies_in_MOSS_2007.aspx?postID=345

 
Leave a comment

Posted by on April 13, 2009 in administration, Backup/Restore

 

Tags: , ,

Working with large lists in Office SharePoint Server 2007


A Sharepoint single list should not have more than 2,000 items per list container. A container in this case means the root of the list, as well as any folders in the list — a folder is a container because other list items are stored within it. Maximum number of items supported in a list with recursive folders is 5 million items….(Content Source: http://technet.microsoft.com)

Here is  a white paper provided by  Microsoft. worth reading….Read/Download:Working with large lists in Office SharePoint Server 2007(White Paper)

 

Tags: , , , ,

SharePoint Work Acceleration Toolkit 2007 aka (SWAT) – Free download


SharePoint Work Acceleration Toolkit (SWAT) is a windows based utility aimed at simplifying and accelerating the creation and testing of SharePoint Solutions. With a whole host of time saving capabilities and planned integration with Universal SharePoint Manager 2007, you’ll never want to take on SharePoint without it again. read more…..

http://www.idevfactory.com/products/swat/default.aspx

 
Leave a comment

Posted by on April 5, 2009 in administration, New Releases

 

Tags: