Display User field in search result

How to display custom user field in search result .

This includes two steps field definition and create a managed metadata property.

1. Field Definition

<Field ID=”{AE6EFA2E-DF0E-4EF5-8AB7-309FBC5465B9}”

Group=”My Columns”
Mult=”FALSE”
UserSelectionMode=”0″
Type=”UserMulti” List=”UserInfo”
Name=”helloauthor” DisplayName=”helloauthor”
SourceID=”http://schemas.microsoft.com/sharepoint/v3&#8243;
StaticName=”helloauthor”

/>

2. Before creating managed property add some data to the field may be in your
documents library or custom list etc… and then crawl the search , once
your property is propagated  then create managed property.

Now re crawl your search and the perform search based on user name.

Upload file in SharePoint Style Library using Powershell

This Powershell code snippet upload xsl file into style library.

 

 

if ( (Get-PSSnapin -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue) -eq $null )
{
Add-PsSnapin Microsoft.SharePoint.PowerShell
}

#Script settings
$webUrl = “http://MKS&#8221;

function UploadFile( [String] $FilePath)
{
#Open web and library
$web = Get-SPWeb $webUrl

$file =Get-Item $FilePath
write-host “Started Uploading File……”$file.FullName

#Open file
$fileStream = ([System.IO.FileInfo] (Get-Item $file.FullName)).OpenRead()

$folder =  $web.getfolder(“Style Library”)

$web.GetFile($folder.Url + “/XSL Style Sheets/” + $file.Name).CheckOut()

$spFile = $folder.Files.Add($folder.Url + “/XSL Style Sheets/” + $file.Name, [System.IO.Stream]$fileStream, $true)

$spFile.CheckIn(“Checkin by Powershell”)
$spFile.Publish(“Published by Powershell”)

write-host $webUrl”/”$folder.Url”/XSL Style Sheets/”$file.Name

write-host “Successfully Copyied file ” $file.Name

$fileStream.Close();

$web.Dispose()
}

UploadFile -FilePath “C:\***.xsl”

SharePoint 2010 FAST 2010 Unexpected error occured while communicating with Administration

One of the annoying error in FAST 2010 when you clicks on the manage property
it blows up and throw error..

Unexpected error occurred while communicating with Administration … ThreadAbortException : Thread was being aborted. at System …

To avoid this type of error just need to make the deployment and configuration

clean from the beginning.

1. Create a domain user give that user sufficient Administrative privileged.

2. Go to SQL Server give permission to create database permission or
add it in serveradmin role.

3. Login with newly created user and run the FAST setup.

4. After that run the FAST Configuration wizard.

5. Go to Active directory and verify “FASTSearchAdministrators” group and
the members inside.

6.Install the certificates and follow the instruction.
http://technet.microsoft.com/en-us/library/ff381253.aspx

7. run the command [nctrl status] verify if services are running
if not running then start it using powershell command or from services.

8. Go to central admin create Search Query and Connector and give permission.

Feature receiver not working when activating through the powershell script

Sometime while deploying package using powershell script it works fine and also activates
the feature, but any feature receiver event does not fire.

To solve this issue:-

Try to close the powershell command window and open new powershell  window.
and then run the deployment script once again and this worked for me.

The operation could not be completed because item was removed from the gallery

This is common Webpart deployment error

Some time after deploying the wsp package containing webpart doesnot work properly.

When tried to add into the webpart it throws error:-

 The operation could not be completed because item was removed from the gallery

 To solve this problem go to webpart gallery delete the webpartentry from the gallery and then deactivate and activate the webpart feature.

 

SharePoint 2010 FAST Search : Property doesn’t exist or is used in a manner inconsistent with schema settings

In order to fix error Property doesn’t exist or is used in a manner inconsistent with schema settings ,

1. Double check the data-type of any newly created Managed Property with respect to the crawled property.

2. Start full crawl the content source and verify if search started working properly.

3. In case search result still shows the same error, then run the following command in FAST Powershell ,  followed by full crawl, read.

                                        nctrl restart qrserver

 

 

How to create a Lookup Field From Sub-Site List to Root-Site Collection List (Cross-Site Lookup)

This solution is based on power shell script for creating cross site look up field.

For example there is a sub site http://mksportal/site1 which contains a list “Product Name”  and
there is another sub site http://mksportal/site2/site3.
In order to make cross site look up field available to sub site through content type,
this can be achieved by using power shell script.

There are couple of things mandatory, when cross site look up is created on that time both sub site and list must exist because it is dependent on list ID.
This is basic script, one can customize further like add reference field for the same lookup field mapped to other field like ID etc.
try
{

$mksWebSite =  “http://mksPortal/Site1&#8221;

$spweb = Get-SPWeb $mksWebSite
$webids=$spweb.ID

$lst = $spweb.Lists[“Product Name”]

$fieldXML = ‘
<Field ID=”GUID”
Name=”mksField”
Group=”MKS
Type=”Lookup”
DisplayName=”mksField”
StaticName=”mksField”
List=”{‘ + $lst.ID +’}”
ShowField=”Title”
Overwrite=”TRUE”
WebId=”‘ + $webids + ‘”  ></Field>’

$field = $spweb.Site.RootWeb.Fields.AddFieldAsXml($fieldXML)
$fieldRef = $spweb.Site.RootWeb.Fields.AddFieldAsXml($mksFIELDRef)
$spweb.Site.RootWeb.Update()
$ctypeParent = $spweb.Site.RootWeb.availablecontenttypes[“My Custo CType”]
$newContentType = $spweb.Site.RootWeb.ContentTypes[$ctypeParent.ID];
$fieldLink = new-object Microsoft.SharePoint.SPFieldLink($spweb.Site.RootWeb.Fields[ $fieldInternalName])
$newContentType.FieldLinks.Add($fieldLink)
$newContentType.Update()

$spweb.Dispose()

}

catch [System.SystemException]

{

write-host “Execution stopped due to: “+$_.Message -foregroundcolor Red

}