Apple iPhone 6s vs Samsung Galaxy S6

Easily determining the exact error by using Correlation ID in SharePoint 2010

Making sense of the Correlation IHave you encountered an error that looks like this screenshot below?

Well, if you develop items in SharePoint, then most probably you have seen that not just once but a lot of times unless you are a really good developer that does not commit any mistakes.

Now you are presented with a GUID without any other information so you might be wondering what the hell that means, so you Google your problem and seesome solutions on how to determine what that Correlation ID means by going to the server and in this folder location:

Hide   Copy Code

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS

and voila! You see a ton of logs that SharePoint had generated over time.

You then open the log specific to the time when your issue happened and to your surprise, the GUID is non-existent. To your dismay, you search other logs that are near the time your issue happened but still there’s no luck. Well, there are other easier means for searching for what you want and that is through the Microsoft SharePoint 2010 Administration Toolkit v2.0.

That toolkit has some of the tools you need for diagnosing issues like such, plus more; it has Load Testing Toolkit, User Profile Replication, Content Management Interoperability Services, and much more. Viewing logs has never been easier as the results are presented in a meaningful way. So how do I use the tool to check what that correlation ID means? Well, here are the steps:

1. Install the tool in your server or even in your local machine that can connect to that server; the installation file can be downloaded here for free. Once downloaded, the installation is straightforward.
2. Once installed, it is time to create your project. First, find the application on your Start menu, then go to SharePoint 2010 Administration Toolkit -> SharePoint Diagnostic Studio. Open that, then click New Project, you will then be presented with a screen similar to below. Put your server name on the text box, then hit “Create Project”. Be patient, it will take sometime to process that.


3. Once finished, you will be presented with this screen, with some information. In other slower servers, you might see it a bit later and it will show “building report please wait…”, but don’t worry, it is processing in the background. Also, if there’s no data, it retains that message.


4. Now you can start searching for your issue by clicking the Search button on top.
5. Populate the needed text boxes and hit OK.


6. Now you will be presented with what you are looking for.

D in SharePoint 2010.

A MUST HAVE SharePoint Interview Questions

What is SharePoint?

Microsoft SharePoint is an extensible platform that provides a range of products that can help organizations with solution for a variety of business needs. Primarily, SharePoint was introduced as an Enterprise Content Management System but later on Web Publishing, Collaboration, Business Process Management (BPM) and Business Intelligence (BI) features were introduced through a variety of ways.

What are the Core features of SharePoint?

With every new version, new and exciting tools were added to SharePoint platform but core of the tools that makes SharePoint an outstanding platform for Content management, Business Process Management, Collaboration and Web Publishing are:

• SharePoint Sites facilitates to create websites.
• SharePoint Communities plays it’s role to collaborate with other peoples.
• Contents makes SharePoint a true CMS (Content Management System)
• Search Engine provides smart and efficient searching of enterprise contents.
• Insights brings information together from different data sources.
• Composition makes SharePoint an extensible platform and extends it’s capabilities by using different tools like SharePoint Designer etc.

Can you briefly explain SharePoint Version History?

Latest version of the product is SharePoint 2013 but if we look into version History, it will be as follows:

What’s new in SharePoint 2013?

New and exciting features are released with every version of SharePoint. SharePoint 2013 also bundled with lots of new features. Few of them are listed here:

• Improved Performance
• Cross-Site Publishing
• Design Manager for Publishing Sites
• Improved and better Search
• Changes in SharePoint Workflow Architecture
• Office Web Apps Server
• Improved Social Computing Features
• Optimized User Interface for Mobile Devices
• Shredded BLOBs for Storage
• New Features to BCS (Business Connectivity Services)
• and much more…

For details on new and updated features in SharePoint 2013, please follow here.

What specific features Improve Performance in SharePoint 2013? Kindly elaborate.

SharePoint 2013 introduces following features that improves performance significantly.

• Distributed Cache Service
• Minimal Download Strategy and
• Shredded Storage by introducing Shredded BLOBs.

What is a SharePoint Farm?

SharePoint Farm is a collection of one or more SharePoint server(s) working together in order to provide a set of
SharePoint Services. Servers in a SharePoint Farm normally share common resources and owns a single Central Configuration database.

Web Applications Vs Site Collections Vs Sites in SharePoint.

SharePoint Site basically is a website. SharePoint allows us to create websites of specific types like Personal site, a Team Site, a social media site, a blogs or a Wiki Site etc.

On the other hand, a Site Collection in SharePoint is a collection of SharePoint sites that share common features like Content types, Templates, Site columns, permissions, Web Parts etc.

A Web Application is a collection of Site Collections in SharePoint OR in order way a site collection resides in a
web application. Normally a SharePoint web application is corresponds to a website in IIS means when a SharePoint Web application is created, it creates a WebSite and an application Pool in IIS .

Above can be understood by following diagram:

What is the concept of Content Type in SharePoint?

SharePoint is about Contents, so Content Type is a reusable collection of settings and metadata to represents a certain type of content. For Instance, a Student Content Type may have set of metadata like Student Enrollment ID, Name, year of enrollment etc.

Content Type in SharePoint facilitates to organize contents in more meaningful way. It supports inheritance of properties, behaviors and appearances.

What is a Theme?

Themes are used to apply customization to a SharePoint Site and applying a lightweight branding by changing overall site layout, colors, fonts, background image etc. In SharePoint 2013, Microsoft has extensively improved  theming Engine. Now, Theme customization is available by creating Font Schemes and Color Palletes. Further, we can add custom themes to Theme Gallery.

What are Master Pages in SharePoint?

Master Pages in SharePoint serves the same purpose as that of ASP.NET Master Pages. Certain parts of a web page normally remains same like header, footer or navigation bar etc. So, We create Master Pages with these common parts in order to achive a consistent look and feel for a SharePoint Site.
Using Master pages provides lots of benefits including:

• Common Controls in one location only
• Writing less Code and Centralized Updating
• Better User Experience
• Flexibility
• Easier management of SharePoint Sites

Important Note:

• A SharePoint Farm can have one or more Web Application(s).
• A SharePoint Web Application can have one or more Site Collection(s).
• A SharePoint Site Collection can have one or more Site(s).
• A SharePoint Site can have one or more List(s).
• A SharePoint List can have one or more List Item(s).

 

SharePoint 2013 and .NET framework 4.6

SharePoint 2013 SP1 is supported on .NET framework 4.6 but there is a known issue when installing SharePoint 2013 on top of .NET framework 4.6

During the installation the installer verifies if .NET framework 4.5 is available and fails to install SharePoint 2013 if .NET framework 4.6 is installed.

The reason is that .NET framework 4.6 replaces .NET framework 4.5 and is not a side-by-side installation. As the installer is not able to match .NET framework 4.6 to .NET framework 4.5 it will prevent the installation.

The solution for this issue is to postpone the installation of .NET framework 4.6 till after SharePoint 2013 SP1 has been installed.

More details in the following KB article:

• KB 3087184 - SharePoint 2013 Setup error occurs if the Microsoft .NET Framework 4.6 is installed

Learn about SharePoint 2016

If you would like to get first information about SharePoint 2016 I would recommend the following two blog posts:

• Evolution of SharePoint - from Julia White, general manager for the Office Product Management team
• The SharePoint related session list from Microsoft Ingite in Chicage 
• Top 3 sessions to learn more about SharePoint Server 2016 at Microsoft Ignite - from Bill Baer (I guess you know Bill, right?)

Features deprecated in SharePoint Server 2016 IT Preview

The following features and functionality have been deprecated or removed in SharePoint Server.

SharePoint Foundation

SharePoint Foundation 2013 remains available for use. For more information, see SharePoint Foundation 2013.

Previous releases of SharePoint Server included SharePoint Foundation, a free edition of SharePoint that included most of the core functionality and architecture provided by the commercial editions of SharePoint. SharePoint Foundation is no longer available in the SharePoint Server 2016 release.

Standalone Install mode

SharePoint Server 2016 IT Preview doesn't support the standalone install option, so it is no longer available in the setup program. Use the MinRole during installation and choose one of the available install options. The Single Server Farm option where everything is installed on the same computer is supported for dev/test/demo purposes. When you use this option, you must install SQL Server yourself and then run the SharePoint Server 2016 farm configuration wizard.. For more information, see "MinRole farm topology" in New and improved features in SharePoint Server 2016 IT Preview.

ForeFront Identity Manager client (FIM)

Earlier versions of SharePoint used ForeFront Identity Manager client (FIM) to synchronize between Active Directory and SharePoint. SharePoint Server 2016 IT Preview no longer uses FIM as the synchronization client. The default process is Active Directory Import. You can also use any synchronization tool such as Microsoft Identity Manager 2016, or any third-party tool. We'll soon release tools to help you deploy and configure Microsoft Identity Manager 2016 to work with SharePoint Server 2016 IT Preview for identity synchronization.

Excel Services in SharePoint

Excel Services and its associated business intelligence capabilities are no longer available in SharePoint Server. Excel Services functionality is now part of Excel Online in Office Online Server Preview, and SharePoint users can use the services from there.

The following Excel Services functionality has been deprecated:

• Trusted data providers
• Trusted file locations
• Trusted data connection libraries
• Unattended service account
• Excel Services Windows PowerShell cmdlets
• Opening of Excel workbooks from SharePoint Central Administration site

The following Excel Services functionality requires Excel Online in Office Online Server Preview:

• Viewing and editing Excel workbooks in a browser (with or without the Data Model)
• Excel Web Access web part for SharePoint
• ODC file support (no longer requires Data Connection Librariees)
• Programmability features such as JavaScript OM, User Defined Function Assemblies, SOAP and REST protocol support

SharePoint BI capabilities

SharePoint Server 2016 requires updated versions that will ship later this year. The SQL Server 2014 Power Pivot and Power View add-ins for SharePoint 2013 cannot be deployed or used in SharePoint Server 2016 IT Preview. The following business intelligence features won't be available until then:

• Power Pivot Gallery
• Scheduled Data Refresh
• Using another workbook's Data Model as a data source
• Power View reports (standalone or embedded in Excel workbooks)
• Power View Subscriptions and Report Alerting
  Power Pivot Management Dashboard
• BISM Link support

Tags and Notes

The Tags and Notes feature is deprecated in SharePoint Server 2016 IT Preview. Users can no longer create new tags and notes or access existing ones. However, an administrator can archive all existing tags and notes by using theExport-SPTagsAndNotesData cmdlet.

Verify that you meet all of the following minimum requirements.

• You must have membership in the securityadmin fixed server role on the SQL Server instance
• You must have membership in the db_owner fixed database role on all databases that are to be updated.
• You must be a member of the Administrators group on the server on which you are running the Windows PowerShell cmdlet.

Export-SPTagsAndNotesData -Site <http://site.contoso.com> -FilePath <tagsandnotes.zip>

Where :

• <http://site.contoso.com> is the URL to an existing SharePoint root site where you want to export the tags and notes from.
• <tagsandnotes.zip> is the name you give to the .zip file that you want to export.

Stsadm.exe

We recommend that you use Windows PowerShell when you perform command-line administrative tasks. The Stsadm command-line tool has been deprecated, but it is included to support compatibility with previous product versions.

DisableEventFiring is obsolete in SharePoint 2010

ou can check this in msdn. However DisableEventFiring()/EnableEventFiring() still works as per Reflector.
Recommended way now is to use new property EventFiringEnabled. This gives us an option to check current status and save it. I found a great post from Adrian Henke and modified his code using this new feature.

	public class DisabledItemEventsScope : SPItemEventReceiver, IDisposable
	{
	private bool eventFiringEnabledStatus;
	public DisabledItemEventsScope()
	{
	eventFiringEnabledStatus = base.EventFiringEnabled;
	base.EventFiringEnabled = false;
	}
	#region IDisposable Members
	public void Dispose()
	{
	base.EventFiringEnabled = eventFiringEnabledStatus;
	}
	#endregion
	}

view rawDisabledItemEventsScope.cs hosted with ❤ by GitHub

The class DisabledItemEventsScope disable/enable event firing for the current thread and could be used in that manner at any place including code behind for the page or web part

	item["Title"]="New Title";
	using (new DisabledItemEventsScope())
	{
	item.Update(); // will NOT fire events
	}

view rawDisabledItemEventsScopeSample.cs hosted with ❤ by GitHub

BTW: There are couple useful SPList extensions to manage SPListItemEventReceiver collection

	// Sample:
	// list.AddEventReceivers(typeof(TestProject.ListItemEventReceivers.TestReceiver),
	// SPEventReceiverType.ItemAdded, SPEventReceiverType.ItemUpdated);
	public static void AddEventReceivers(this SPList list,Type erClassType,
	params SPEventReceiverType[] erTypes)
	{
	foreach (SPEventReceiverType erType in erTypes)
	{
	list.EventReceivers.Add(erType, erClassType.Assembly.FullName,
	erClassType.FullName);
	}
	}
	// Sample:
	// list.RemoveEventReceivers(typeof(TestProject.ListItemEventReceivers.TestReceiver));
	public static void RemoveEventReceivers(this SPList list, Type erClassType, params SPEventReceiverType[] erTypes)
	{
	List<SPEventReceiverDefinition> receivers = new List<SPEventReceiverDefinition>();
	for (int i = 0; i < list.EventReceivers.Count; ++i)
	{
	SPEventReceiverDefinition r = list.EventReceivers[i];
	if (r.Class.Equals(erClassType.FullName) && (erTypes.Length==0 || erTypes.Contains(r.Type)))
	receivers.Add(r);
	}
	foreach (SPEventReceiverDefinition r in receivers)
	{
	r.Delete();
	}
	}

view rawSPListExtensions.cs hosted with ❤ by GitHub