Finding site template names and ID’s in SharePoint 2010

Every now and then we talks about sites, site templates, more technically- the site ID’s etc…

There might be a requirement that you have deployed any solution package with respect to site definition and that will be available under custom tab while creating the site by means of central administration. 

We all know that every site template contains a specific ID associated with it and has multiple benefits with respect to requirement arises.

If you wanna find out the site template ID of all the templates which are installed in your farm then it might be a hectic task.

It’s quite easy if we follow the following article and Million Thanks to Phil Childs who has published this article for the SharePoint Community. 

Very useful article and valuable too as its saving tons of efforts. Thank you Phil :)

http://get-spscripts.com/2011/02/finding-site-template-names-and-ids-in.html

not able to activate the feature in SharePoint 2010

Problem Description: not able to activate the feature in SharePoint 2010

I was facing the following error messages while activating the feature at the site level.

Where exactly:

-Site actions

-Site settings

-Manage site features

Error Message:

Site

The feature being activated is a Site scoped feature which has a dependency on a Site Collection scoped feature which has not been activated. Please activate the following feature before trying again: SharePoint Server Publishing Infrastructure f6924d36-2fa8-4f0b-b16d-06b7250180fa

Web

The Site scoped feature being activated has a dependency on hidden Site scoped feature 'FeatureDefinition/22a9ef51-737b-4ff2-9346-694633fe4416' (ID: '22a9ef51-737b-4ff2-9346-694633fe4416'). Hidden features cannot be auto-activated across scopes. There may be one or more visible Site scoped features that auto-activate the dependent hidden feature.

From the above error message, it is quite clear regarding the resolution we need to apply to get rid of this message.

Resolution:

Let me explain in details, step by step:

-Open the site on which you are facing this problem

-site actions

-site settings

-site collection administration

-site collection features

-activate the appropriate feature as per your requirements.

Note: if you are not able to see the ‘site collection administration then you don’t have appropriate rights to activate that feature.

What you need to do in such situations? - Please contact your site collection administrators and mention the complete details so that they can activate the feature for you / tell them to assign you site collection admin rights -(this is sometimes difficult if they follow the policy)

Product Applies to:

-SharePoint Server 2010

-SharePoint Foundation 2010

If you have any queries/questions regarding the above mentioned information then please let me know.

I would be more than happy to help you as well as resolves your issues, thank you.

Logparser: Calculate No. of hits for different Browser type from IIS Logs

In our organization we had a request to know how many requests are coming to our SharePoint webservers form different browsers.

While working on this, I got a nice post form Mr. Jaskis 
Why you need to know this:

To figure out what kind of browser(IE, Firefox, Safari) requests are coming for your application.So that you can make sure your application is compatible with that browser type.

To read complete article, please follow http://blogs.msdn.com/b/jaskis/archive/2008/11/13/logparser-calculate-no-of-hits-for-different-browser-type-from-iis-logs.aspx

Known issues when you install Office 2010 SP1 and SharePoint 2010 SP1

Found this KB should be easily available for all my users .

This article lists the known issues and behavior changes that you may experience when you install Service Pack 1 (SP1) for Microsoft Office 2010, Microsoft SharePoint Server 2010, Microsoft SharePoint Foundation 2010, and Office server products.

Resolution:

The following are issues that you may experience when you install these service packs:

• SharePoint Server 2010 SP1 has an issue that causes workflow tasks to become locked and unrecoverable, as follows. Assume that you have a running out-of-box (OOB) workflow task (for example, an "Approval – SharePoint 2010," "Collect Feedback – SharePoint 2010," or "Publishing Approval" task). When a task assignee edits the workflow task (for example, by approving or rejecting the trial), the task is locked and cannot be recovered. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  2737435 "In Progress" Workflow tasks are locked after updating to SharePoint 2010 SP1
  
  To resolve this issue, install the hotfixes that are provided in the following articles in the Microsoft Knowledge Base:
  2687614 Description of the SharePoint Server 2010 hotfix package (Coreservermui-xx-xx.msp): October 30, 2012
  2687557 Description of the SharePoint Foundation 2010 hotfix package (Wss-x-none.msp): October 30, 2012
  Note You must install these hotfixes after you install SharePoint 2010 SP1.
• Before you install the SP1 packages, make sure that you have sufficient disk space. For caching, the packages may require up to four times their file size in remaining disk space during installation.
• You must restart the computer at the end of the installation process.
• If Office Web Apps will be used in a mixed version environment, where Office Web Apps has SP1-or-later applied while SharePoint Server 2010 remains on the RTM version, you must install the following two updates before you install SP1 for Office Web Apps:
  • 2510639 Description of the SharePoint Server 2010 update: April 12, 2011
  • 2510648 Description of the Office Web Apps update: April 12, 2011
• Install the service packs in the following order on every server in the farm:
  1. Service Pack 1 for SharePoint Foundation 2010
  2. Service Pack 1 for SharePoint Foundation 2010 Language Pack (if applicable)
  3. Service Pack 1 for SharePoint Server 2010
  4. Service Pack 1 for SharePoint Server 2010 Language Pack (if applicable)
• After you install Service Pack 1 you must run the SharePoint 2010 Products Configuration Wizard or the psconfig –cmd upgrade –inplace b2b -wait command one time on every server in the farm. This step updates the farm to the latest version and is required in order to have full SharePoint functionality. If you do not run the wizard, the farm will run with reduced capacity. For example, Search will not be able to index content.
• You must restart the User Profile Synchronization service after installing Service Pack 1. For more information about how to start the service, see the "Start the User Profile Synchronization service" section of the following Microsoft website:
  Configure profile synchronization
• After SharePoint Server 2010 SP1 is installed, the Workflow feature is disabled when a new site collection is created. To use the Workflow feature in a new site collection, enable it in the Site Collection Settings page.
• After you install SharePoint Foundation 2010 SP1 and SharePoint Server 2010 SP1, we strongly recommend that you install the install the June 2011 Cumulative Update refresh package. The June Cumulative Update includes several important security and bug fixes that are not included Service Pack 1. For more information about these updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
  2536601 Description of the SharePoint Foundation 2010 cumulative update package (SharePoint Foundation server-package): June 30, 2011
  
  2536599 Description of the SharePoint Server 2010 cumulative update package (SharePoint server-package): June 30, 2011

  Applies to

  • Microsoft Office Home and Student 2010
  • Microsoft Office Home and Business 2010
  • Microsoft Office Professional 2010
  • Microsoft Office Professional Plus 2010
  • Microsoft Office Standard 2010
  • Microsoft Office Starter 2010
  • Microsoft SharePoint Foundation 2010
  • Microsoft SharePoint Server 2010

  
  Reference : http://support.microsoft.com/kb/2532126

Kerberos configuration known issues (SharePoint Server 2010)

Kerberos authentication and non-default ports

There is a known issue where some Kerberos clients (.NET Framework, Internet Explorer 7 and 8 included) do not correctly form service principal names when attempting to authenticate with Kerberos enabled web applications that are configured on non-default ports (ports other than 80 and 443). The root of the problem is the client does not properly form the SPN in the TGS request by specifying it without the port number (as seen in the Sname of the TGS request).
Example:
If the web application is running at http://intranet.contoso.com:1234, the client will request a ticket for a service with a SPN equal to http/intranet.contoso.com instead of http/intranet.contoso.com:1234.
Details regarding the issue can be found in the following articles:

• Internet Explorer 6 cannot use the Kerberos authentication protocol to connect to a Web site that uses a non-standard port in Windows XP and in Windows Server 2003 (http://support.microsoft.com/kb/908209/en-us)
• Configure Kerberos authentication (Office SharePoint Server 2007) (http://go.microsoft.com/fwlink/p/?LinkId=196987)

To work around this issue, register SPNs with and without port number. Example:

• http://intranet.contoso.com:12345

• http/intranet
• http/intranet.contoso.com
• http/intranet:12345
• http/intranet.contoso.com:12345

We recommend that you register the non-default port to ensure that if the issue is resolved in some future service pack or hot fix, the applications using the workaround will still continue to function.
Note that this workaround will not work if the following conditions are true:

• There is more than one web application running on a non-default port
• The web applications either bind to the host name of the server or bind to the same host header (on different ports)
• The web application IIS application pools use different service accounts

• http://server.contoso.com:5000 AppPool Id: contoso\svcA
• http://server.contoso.com:5001 AppPool Id: contoso\svcB

If these conditions are true, following the recommendation in this workaround will yield duplicate SPNs registered to different service accounts which will break Kerberos authentication.
If you have multiple web sites sharing a common host name running on multiple ports, and you use different IIS application pool identities for the web applications, then you cannot use Kerberos authentication on all web sites. (One application can use Kerberos, the rest will require another authentication protocol.) To use Kerberos on all applications in this scenario, you would need to either:

1. Run all web applications under 1 shared service account
2. Run each site with its own host header
   
   
   Reference : http://technet.microsoft.com/en-us/library/gg502606%28v=office.14%29.aspx