02 February, 2013

Server based Search- Exact match and Prefix match in Lync Server 2010

Server based Search- Exact match and Prefix match in Lync Server 2010
Guys,

We are using Lync Serer 2010 since long however you know how the server based search is work? Here are few scenarios; basically Server-based search usage can be configured by using the in-band provisioning setting, AbsUsage.
This in-band provisioning setting having three possible values:
1.    WebSearchAndFileDownload. IP phones (for example, Polycom CX700 IP desk phone) use server-based search, and Lync 2010 clients use GAL download. This is the default.
The Lync desktop client defaults to GAL download for the following reasons:
·       There may be temporary outages for the Address Book Service depending on the server maintenance schedule. When the Address Book Server is unavailable, all prefix and exact match searches fail.
·       Server-based search does not work in branch office resiliency mode.
2.    WebSearchOnly. Both IP phones and Lync 2010 clients use Server-based search.
3.    FileDownloadOnly. Both IP phones and Lync 2010 clients use GAL download.
Server-based search can be used for both exact and prefix searches. The exact and prefix match searches are different, and the various scenarios when the Lync client would perform an exact match search versus prefix match search.
The Lync client sends a SOAP query through HTTPs to the user’s Front End pool. Search results are returned in an XML format.

Exact match search is performed by the Lync client whenever it needs GAL contact data for a specific contact. In an exact match query, the Lync client requests the GAL contact data by using a SIP URL or email address. Passing a SIP URL or email address in the request ensures the GAL contact data returned is unique because the SIP URI and email address are both unique contact identifiers.

Prefix search is invoked when a user initiates a search from the following:
·       The main UI search box.
·       The People picker dialog box (that can be opened, for instance, from the Conversation Window, the call forwarding dialog box, or call transfer).

When a prefix search is performed, the client sends a SOAP query with the search term and number of search results to be returned by the Address Book Service. Lync client shows the top 50 results whereas IP phones and Lync mobile clients show the top 20 results.

Thank you.

31 January, 2013

Enabling and Using Developer Dashboard - Sharepoint 2010

Today I was working with one Client who was having some issues with performance . In Sharepoint 2010 . I found a Out of box Feature which helps in monitoring the performance of the site Developer Dashboard.

The Developer Dashboard is an instrumentation framework introduced in Microsoft SharePoint Foundation 2010. Similar in concept to ASP.NET page tracing, it provides diagnostic information that can help a developer or system administrator troubleshoot problems with page components that would otherwise be very difficult to isolate.

For example, a developer can easily introduce extra SPSite or SPWeb objects into his or her code unknowingly or add extraneous SQL Server queries.

In the past, the only way to debug performance problems caused by the extra overhead of these instances in code would be to attach a debugger to the code and monitor SQL Server Profiler traces. With the Developer Dashboard, a developer can identify this type of problem, either programmatically by using the object model or visually by looking at page output.

Although performance issues and resource usage information is available in the Unified Logging Service (ULS) logs, interpreting the raw data can be very time consuming. With the Developer Dashboard, all the related information is correlated, which makes identifying these types of issues much easier.

How to enable Developer Dashboard and how to use this?

Enable / Disable over stsadm:

stsadm -o getproperty -pn developer-dashboard



stsadm –o setproperty –pn developer-dashboard –pv “On”





Enable / Disable over powershell

Turn On: for onDemain Mode
$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$addsetting =$service.DeveloperDashboardSettings
$addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand
$addsetting.Update()


Turn On
$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$addsetting =$service.DeveloperDashboardSettings
$addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::On
$addsetting.Update()


Turn Off
$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$addsetting =$service.DeveloperDashboardSettings
$addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::Off
$addsetting.Update()
 


On – Displays the output all the time at the end of the page content
Off – Switch off Developer Dashboard and nothing is rendered
OnDemand – Displays a DeveloperDashboard icon to make dashboard output visible if needed.

In ON Demand - you will see a icon on the top right hand side corner of the site . as Shown below .



also you will see the following details when you click on the icon .



How to use the Developer Dashboard?
Developer dashboard is designed to find performance bottleneck during the page load.
To get an overview about the whole page load performance take a look in the upper right side  on category “web server”. On my test environment the total time of page rendering  is 3801.71 milli seconds.





At the left side you will see the ASP.NET rendering process of all involved controls with their time to render. Here is makes sense to focus only on long running controls.






In this case the longest operation is GetWebPartPageContent (1815.92 ms)

Because sharepoint controls will request data from database, the developer dashboard lists also corresponding sql requests with their execution time.



If you click on the sql command than a popup windows display more details. The long running sql request on my test environment is “Declare @…”





During this request i see the complete SQL query and the corresponding call stack to identify the correct control. Additionally at the end we see the IO Stats in case of a slow running SQL server based on too many IO-operations. 


One additional category exist for webparts to identify the slow running ones. In this case the ListView-Webaprt of the “Shared Document Library” is the slowest one.


Hope This Post helps administrators on resolving Performance issues .



Reference sites- http://msdn.microsoft.com/en-us/library/ff512745(v=office.14).aspx

http://blogs.technet.com/b/patrick_heyde/archive/2009/11/16/sharepoint-2010-enable-using-developer-dashboard.aspx

28 January, 2013

Psconfig Steps with their Operations performed at each task

Today Lets check out What happens when we run the Post Setup configuration Wizard . After setup is run the post setup configuration wizard must be run to complete the process of either creating a new farm or joining a server to an existing farm.
Psconfig Steps with their Operations performed at each task. 
Task 1 -      Initialize SharePoint products and technologies configuration 
Note - It Initializes the configuration and has very less chances of failing on this step.
Task 2 -    Create Configuration database
Note - It creates a new configuration Database in the sql . You need to have proper rights to create a database. 
Setup user account - The Setup user account is used to run the following:
  • Setup
  • SharePoint Products Configuration Wizard
    • Domain user account.
    • Member of the Administrators group on each server on which Setup is run.
    • SQL Server login on the computer that runs SQL Server.
    • Member of the following SQL Server roles:
      • securityadmin fixed server role
      • dbcreator fixed server role
If you run Windows PowerShell cmdlets that affect a database, this account must be a member of the db_owner fixed database role for the database.

If you find an issue Connecting Sharepoint to the Sql server. Create a UDL file and check for the connectivity. For further information on UDL check the link below

http://blogs.msdn.com/b/farukcelik/archive/2007/12/31/basics-first-udl-test.aspx
Task 3 -      Install help collections
Task 4 -       Secure SharePoint resources
Task 5 -            Register SharePoint Services
 Successfully provisioned service: Windows SharePoint Services  Usage.
Successfully installed service instance: Windows SharePoint Services Usage
Successfully provisioned service instance: Windows SharePoint Services Usage
Successfully installed service: Microsoft.SharePoint.BusinessData.SharedS
BdcService.
Successfully provisioned service: Microsoft.SharePoint.BusinessData.Share
e.BdcService.
 Task 6 -        Register SharePoint features
Successfully installed feature C:\Program Files\Common Files\Microsoft Sh…
Server Extensions\14\Template\Features\SPSearchFeature\Feature.xml.
Successfully installed feature C:\Program Files\Common Files\Microsoft Sh
b Server Extensions\14\Template\Features\TenantAdmin\feature.xml.
Task 7          Provision Central Administration Web application and site if   
                        Standalone install.
Task 8 -          Register SharePointHealth Analysis rules 
Task 9 -            Create sample data and provision default Web application 
Task 10 -         Install application content files
Installing the application content files...
Installing the SharePoint Central Administration Web Application content.
Installing the SharePoint Web Application content files...
Task 11 -Finalize SharePoint product and technologies configuration
One new feature of SharePoint Foundation 2010 is that it will automatically set up inbound Windows firewall rules when provisioning a Web application or Web services. During PSConfig, steps above firewall rules will be created for newly created Web applications and services.

Business Data Connectivity connectors are currently enabled in a partitioned environment: SharePoint 2013.

Problem: You could see in SharePoint Health Analyzer rule "Business Data Connectivity connectors are currently enabled in a partitioned environment."
Background:  Business Data Connectivity (BDC) Models containing External Content Types with database, WCF, Web service or custom connectors can be used by tenants to elevate their user permissions. In a partitioned environment, we recommend you disable the Business Data Connectivity connectors.
Reason for error: Business Data Connectivity connectors are currently enabled in a partitioned environment.
Resolution: Disable unwanted connectors by using Windows PowerShell.
To disable unwanted connectors, follow these steps:
1.      Click Start, click All Programs.
2.      Click Microsoft SharePoint 2010 Products.
3.      Click SharePoint 2010 Management Shell.
4.      At the Windows PowerShell command prompt, type the following command, and then press ENTER:
Get-SPServiceApplicationProxy
5.      Note the Business Data Connectivity proxy instance.
6.      You must set the EnableSystemType property to false for each unwanted connector. To do this, at the Windows PowerShell prompt, type the following command, and then press ENTER:
$proxy.EnableSystemType("Connector_type",$false)
Applies to:
·        SharePoint Server 2013 
·        SharePoint Foundation 2013