An unexpected error has occurred in SharePoint 2010

I got this error while opening my sharepoint web site. The error message is "An unexpected error has occurred". Below is the screen shot for reference.

Also you can check out my previous posts on:

- Set the Bing Maps key at the web and farm level in SharePoint 2013

- Audio and Video content type in SharePoint 2013

- custom timer job sharepoint 2010

Solution:
I exactly do not know the reason why this error is coming. But when I refreshed the page again the error went. And my site opened.

SharePoint designer workflows

In this post we will discuss about what are the workflows that can be created using SharePoint designer 2010.

Also you can check out my last article on SharePoint 2010 out of box workflow templates.

Below are the workflows can be created by SharePoint designer:

- List workflow:
This is one of the mostly popular workflow as well as also available in MOSS 2007. This workflow allows

SharePoint Designer 2013 Crashing on Open Site

If you have installed SharePoint 2013 and SharePoint 2010 side by side then sometimes when you click on Open site in SharePoint 2013 designer, it will crash.

Before looking at the solution, you can check out my previous posts on:

- Hide ribbon in InfoPath form in SharePoint 2013

- SharePoint 2010 Centered Fixed Width Design

- New ways to work with video and rich media in SharePoint 2013

I do not know whether it is a feasible solution or not but you can modify the registry entry to solve this error like below:

click on Start -> Run -> Regedit

Then check the ClientGUID value in registry for both SharePoint 2013 and SharePoint 2010.

For SharePoint 2010 designer:
Open the below location:

HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Open Find\Microsoft SharePoint Designer\Settings\Open Site

For SharePoint 2013 designer:
Open the below location:

HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Open Find\Microsoft SharePoint Designer\Settings\Open Site

If both the values are same then delete both the values

It should work now !

New microblogging features in SharePoint 2013

In this article we will discuss what are the micro blogging features improvements in SharePoint 2013.

You can check my previous articles on SharePoint 2013 video tutorials, Hardware and software requirement for SharePoint 2013 and Removed features in SharePoint 2013.

If you’re familiar with popular social networking sites, you’ll feel right at home using the new microblogging features, which allow you to engage in threaded conversations in your Newsfeed. With microblogging, you can:

Windows PowerShell Builder Tool for SharePoint

In this article we will discuss about windows powershell builder tool which is provided from Microsoft. You can also check CAML designer for SharePoint 2013, ULS viewer Tool and SPDisposeCheck tool for SharePoint.

Also you can see SPMetal in SharePoint 2010.

Windows PowerShell for SharePoint Command Builder is a very good tool for developers and administrators. It is suitable for SharePoint Foundation 2010, SharePoint Server 2010, SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Online, and Office 365.

The tool exists in this page and you can download getting started guide from here.

Description:
Verbs: It defines the action to be performed by the cmdlet.
Nouns: Nouns describe what a command acts upon.
Design Surface: This consist of Verb, Noun, Required Fields, Optional Fields and the PowerShell Command View.

You can choose products from the Products dropdown list as shown in the figure below, similarly the
corresponding useful common commands you can select from the Quick Steps dropdownlist.

To start making the command first select one from Verbs (the corresponding Nouns will come automatically)
and then either Drag and Drop to design surface to the Verb area or you can click Send button. Similarly you can do this for Nouns also as shown in the figure below:

Once both these commands comes to the design surface, you can give the required fields , here Backup method, directory as well as Optional fields Backup threads etc. Once you will fill these fields the command will be designed as shown in the figure below:

You can copy the command by click on the Copy to Clipboard and also you can clear the Design Surface by click on the Clear Design Surface button as shown in the figure below:

The installed virus scanner is currently unavailable. If the problem persists, contact your administrator

In this article we will discuss about an error that ususally occured while uploading image or document to document library. The full error message is "The installed virus scanner is currently unavailable. If the problem persists, contact your administrator".

You can also check my previous articles on SharePoint 2013 benefits, JQuery reference in Application pages in SharePoint and how to redirect to new URL from SharePoint 2010 site.

Solution:
Follow below steps to resolve these error.

Add script reference dynamically through code in SharePoint

In this post we will discuss how we can give script reference dynamically using code. You can check my previous posts on JQuery reference in Application pages in SharePoint, Call jQuery to SharePoint page using master page and Deploy jQuery to SharePoint using solution package.

To add script reference dynamically follow below stes:

Step-1:
Open visual Studio 2010, Click on File -> New project. Then from the New Project dialog box, Select Visual C# -> SharePoint -> 2010.

Call jQuery to SharePoint page using Custom Action

In this article we will discuss about how to call jQuery to SharePoint using custom action.

In my previous articles I have discussed about how to deploy jQuery to layouts folder and how to deploy jQuery to site assets library.

Also I have explained how to call jQuery into SharePoint page using content editor web part.

To call jQuery to SharePoint through custom action follow the below steps:

Step-1:
Open Visual Studio 2010, and choose File -> New Project. Select SharePoint -> 2010 -> Empty SharePoint Project. Name the project jQueryCustomAction, and click OK. Also remember to select .Net framework as 3.5. check out the figure below:

Step-2:
In the next dialog box give me local deployment URL as shown in the figure below. Remember to select Deploy as a sandboxed solution.

Step-3:
Right-click the project in the Solution Explorer and choose Add -> New Item. Select Empty Element, and call it jQueryCustomActionElement as shown in the figure below:

Step-4:
Now open the Elements.xml file and add  the custom action attribute like below:

<CustomAction ScriptSrc="~SiteCollection/SiteAssets/jQuery/jquery-1.6.2.min.js" Location="ScriptLink"
   Sequence="100">
  </CustomAction>

Now the full Elements.xml file will be like below:

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <CustomAction ScriptSrc="~SiteCollection/SiteAssets/jQuery/jquery-1.6.2.min.js" Location="ScriptLink"
   Sequence="100">
  </CustomAction>
</Elements>

Here ScriptSrc is the attribute that contains the jQuery file path where the jQuery is deployed.

Now deploy the solution and the jQuery will be available to the page.

Deploy jQuery to site assets library using SharePoint solution package

In this article we will discuss about how to deploy jQuery files to SharePoint Asset library, so that it will be available to the particular site collection only. You can also check my last article on how to deploy jQuery files to the layouts folder using solution package in SharePoint 2010.

You can also check some various articles on SharePoint 2013. Check SharePoint interview questions and answers, SharePoint customization articles and SharePoint administration articles.

Follow below steps:
Step-1:
Open Visual Studio 2010, and choose File -> New Project. And then Select SharePoint -> 2010 -> Module. Give a Name to the project DeployjQuery, and click OK. Remember to select .Net framework version 3.5 as shown in the figure below:

Step-2:
In the next step select the local deployment URL and select "Deploy as a sandboxed solution".

Step-3:
Now if you will open the solution explorer it should be look like below:

Step-4:
In the next step Rename the Module1 module to Assets, and delete the Sample.txt file. Remember after doing this the Elements.xml file contains also changed accordingly.

Step-5:
Now copy the jQuery files and put it inside the Assets folder. Now the elements.xml file will change automatically but you need to add URL attribute to the Module like below:

<Module Name="Assets" Url="SiteAssets">

The full elements.xml file should be like below:
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <Module Name="Assets" Url="SiteAssets">
  <File Path="Assetsjquery-1.6.2.min.js" Url="Assets/jquery-1.6.2.min.js" />
</Module>
</Elements>

Now if you deploy and check the Site Assets folder the jQuery files should be there.

But before deployment it is good to give a good name to the feature.

So expand the Features folder and rename Feature1 to jQueryFeature and then double click on jQueryFeature.feature. From there change the Title and Description and also you can set the Scope of the feature.

Now you can deploy the solution. Once the deployment is over the jQuery files can be browse like below:
http://URL/SiteAssets/DeployjQuery/jquery-1.6.2.min.js

If you want to deploye the wsp through powershell or stsadm then follow this article.

Page Layout not appearing in SharePoint designer

In this article we will discuss about how to bring page layout option in SharePoint designer in Team site.

You can also check my last article on Difference between Team site and Publishing site in SharePoint 2010,  Blob Cache in SharePoint 2010  and Working with List using SharePoint 2013 client object model.

Page Layout option appear perfectly for publishing web sites, But if you are using Team site and if your publishing feature is not activated then Page Layout option will not appear in SharePoint designer.

Page Layout option appears if SharePoint publishing feature is enabled. By default in Team site SharePoint server publishing feature is not enabled. Below are the steps to do that:

1- Activate SharePoint Server Publishing Infrastructure feature of Site collection

To activate  SharePoint Server Publishing feature of the Site Go to Site Actions -> Site Settings. This will open the Site Settings page. From there click on Site collection features under Site Collection Administration section as shown in the figure below:

This will open list of features of the site collection, Click on Activate SharePoint Server Publishing Infrastructure as shown in the figure below.

2- Activate SharePoint Server Publishing feature of Site:

To activate  SharePoint Server Publishing Infrastructure feature of the Site collection, Go to Site Actions -> Site Settings. This will open the Site Settings page. From there click on Manage site features under Site Actions section as shown in the figure below:

This will open list of features, Click on Activate SharePoint Server Publishing feature as shown in the figure below.

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

Hi All I am getting the below error while trying to activate SharePoint publishing feature in a team site in SharePoint 2010. Below is the full 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

Detected use of SPRequest for previously closed SPWeb object SharePoint 2010

I got this error message while checking in event viewer in SharePoint server. The full error message is "Detected use of SPRequest for previously closed SPWeb object. Please close SPWeb objects when you are done with all objects obtained from them, but not before".

Sometime also you can get error like this "An SPRequest object was not disposed before the end of this thread. To avoid wasting system resources, dispose of this object or its parent (such as an SPSite or SPWeb) as soon as you are done using it."

SharePoint 2010 root directory

In this blog we will discuss about SharePoint 2010 root directory.

In my previous articles we have discussed about Developer Dashboard, Difference between Team site and Publishing site in SharePoint 2010 and Client object model in SharePoint 2013.

You can also check out some SharePoint 2013 articles.

SharePoint stores some template files in a special directory on the local file system of each front-end Web server, which is know as SharePoint root directory. It is also know as 14 hive directory in SharePoint 2010 and 12 hive directory in MOSS 2007.

If SharePoint is installed in C drive then it usually will be in the below location:

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

For SharePoint foundation, it contains set of images, templates, features, and pages. But if you install SharePoint server then it contains images, templates, features, and pages and some template files which provides additional functionality apart from SharePoint Foundation.

Below is an image of a 14 hive directory of SharePoint server.

Below are some sub directory and the type of template files it contains:
/ISAPI:
This directory contains all the Web Services (.svc, .ashx, .asmx) as well as the required dlls for SharePoint like Microsoft.SharePoint.client.dll, Microsoft.SharePoint.dll etc.

/Resources:
 This directory contains all the Resource files (.resx). This is the ideal location to deploy your custom Resource files if you are using any.


/TEMPLATE/ADMIN:
 This directory contains Application pages used exclusively in Central Administration.

/TEMPLATE/CONTROLTEMPLATES:
This directory contains ASP.NET User Controls (.ascx) files, like user controls used in Visual Webpart.

/TEMPLATE/FEATURES:
 This directory contains Feature definition files (.xml).

/TEMPLATE/IMAGES:
This directory contains Images (.gif, .jpg, and .png) and if you have to use custom images then you can create a sub directory and put your custom images.

/TEMPLATE/LAYOUTS:
This directory contains Application pages (.aspx).

/TEMPLATE/LAYOUTS/1033/STYLES:
This directory contains all the default CSS Files (.css) files used in SharePoint. You can put custom css files in this directory.

/TEMPLATE/LAYOUTS/ClientBin:
This directory contains Silverlight components (.xap).

/TEMPLATE/SiteTemplates:
 This directory contains Site Definition files (onet.xml).

/TEMPLATE/XML:
 This directory contains Custom field type definition files (fdltype*.xml).

/LOGS:
This folder contains all the Log files maintain by SharePoint.

/Help:
This contains the help files.

Difference between Standalone Installation and Server Farm installation

In this article we will discuss about What is the difference between Standalone and Server Farm installation. You can also check SharePoint 2013 installation video and also you can check SharePoint workflow video tutorial.

There are two types of installation can be done, Standalone Installation and Server Farm installation. While installing SharePoint 2010, it will ask you which installation you want to do.

Backup and Restore Site Collections in SharePoint 2010 using PowerShell

In this post we will discuss how to take Backup and Restore site collections using PowerShell in SharePoint 2010.

In my previous articles I have explained about on Get System Accounts using PowerShell, Some PowerShell commands for SharePoint 2010.

Also check how to Switch from Classic to Claims Authentication in SharePoint 2010 and check how to

SharePoint 2013 workflow development tools

In this post we will discuss about various tools to work with SharePoint 2013 workflow. As we know SharePoint 2013 has improved workflow experience like Windows Azure Workflow.

There are several tools that come together to provide a rich workflow development experience, like:

1. Visual Studio 2013:
Visual Studio 2013 can be used to develop workflows similar to SharePoint Designer 2013. Apart from that you also can develop custom actions and tasks such as a workflow action that interacts with a custom application.

2. SharePoint Designer 2013:
SharePoint Designer 2013 provides a rich set of features specifically designed for workflow development against both the SharePoint 2010 Workflow platform and the SharePoint 2013 Workflow platform.

3. Visio 2013:
Visio 2013 is an Office application that is used to build diagrams by using shapes and connectors. You can use Visio 2013 to build workflows based on the SharePoint 2013 Workflow platform. You can import workflows from Visio 2013 into SharePoint Designer 2013, and vice versa.

4. InfoPath 2013:
InfoPath 2013 is a tool designed for form development. Using InfoPath 2013 you can customize the forms that a workflow uses as users interact with it.

5. A supported web browser such as Internet Explorer, Firefox, or Chrome Web browsers will be used to to interact with SharePoint Server 2013 sites. You can check browsers supported by SharePoint 2013.

New master pages in SharePoint 2013

In this blog we will discuss about new master pages in SharePoint 2013. Master pages are very much useful for the look and feel of a site.

You can also check my last articles on Master Pages in SharePoint 2010, also you can check how to fix  centered fixed design here, also check How to change master page programmatically SharePoint 2010.

Here are some new SharePoint 2013 master pages which are newly introduced.

- App.master

Working with SharePoint 2013 client object model

In this article we will discuss about SharePoint 2013 client object model.

In my previous articles I have also explained about What's new in Visual Studio 2012 for SharePoint? , Difference between SharePoint 2013 and SharePoint 2010 and Social networking feature in SharePoint 2013.

In this article we will discuss about how we can update web site properties like Title and Description using SharePoint 2013 client object model. Below is the code:

Error were found when compiling the workflow. The workflow files were saved but cannot be run.

I got this error while working with SharePoint designer 2010 workflow. The full error message is "Error were found when compiling the workflow. The workflow files were saved but cannot be run.

Unexpected error on server associating the workflow".

I found a very good and simple solution in Snahta blog. The solution of the above error is very simple.

Open the web.config file of the web application which we usually found in

Get all users from web application in SharePoint using PowerShell

In this article we will discuss how to get list of all users in a web application using PowerShell in SharePoint 2010. You can also check this article for some powershell commands to work with SharePoint database.

We can retrive list of users inside a web application using PowerShell.

First Open PowerShell command window in Administrator mode. (Start -> All Programs -> Microsoft SharePoint 2010 Products and then Right click on SharePoint 2010 Management Shell)

Once it will open in Admin mode, type the command like below:

Get-SPWebApplication [Web application URL] | Get-SPSite | Get-SPWeb | Get-SPUser

Ex: Get-SPWebApplication http://bsahoo3:2500 | Get-SPSite | Get-SPWeb | Get-SPUser

Also you can try for each SPWeb object like below:

In the PowerShell command prompt type:

Get-SPUser
Then it will ask you to give the SPWeb name (as shown in the figure below)
Enter the web name like
 http://bsahoo3:2500/sites/TestSiteCollection

Then it will show the output of the list of users.

Check the figure below for both the commands.

What's new in Visual Studio 2012 for SharePoint?

As we know Visual Studio 2012 has been released, in this article we will discuss about What's new for SharePoint in visual studio 2012. You can also check out some SharePoint 2010 and SharePoint 2013 articles.

Visual Studio 2012 comes in grey color now with a good look and feel. As usual it contains lots of templates for Windows, web, office, cloud, reporting, silverlight, wcf, windows phone, workflow & SharePoint etc in different languages like Visual Basic, Visual C#, Visual C++, Visual F# etc.

Here we will discuss about the feature for SharePoint.

Visual Studio 2012 simplifies the Project templates and Project item templates like below:

Project Templates:

It contains 5 project templates like below:

1. SharePoint 2010 Project: This project template helps us to create sharepoint 2010 projects.

2. SharePoint 2010 Silverlight Web Part: SharePoint 2010 Silverlight Web Part projects enable you to create web parts for SharePoint that display Silverlight applications.

3. SharePoint 2010 Visual Web Part: This template helps us to create visual web parts in SharePoint 2010.

4. Import SharePoint 2010 Solution Package: Import SharePoint 2010 Solution Package projects let you import all or part of an existing SharePoint 2010 site, exported to a SharePoint solution (.wsp) file, into Visual Studio.

5. Import Reusable SharePoint 2010 Workflow: Import Reusable SharePoint 2010 Workflow projects let you import a reusable, declarative workflow created in SharePoint Designer 2010 into Visual Studio.
Project Item Templates:
Apart from the above project templates Visual Studio 2012 contains the below project item templates. They are:

1- Silverlight Web Part:
Silverlight web part project items enable you to create web parts for SharePoint that display Silverlight applications.

2- Visual Web Part:
This template helps us in creating visual web parts. This contains items like Elements.xml definition file, a Web Part item, and a User Control.

3- Web Part:
This type of projects runs inside web part page and this template helps us to build a web part for SharePoint site.

4- Application Page (Farm Solution Only):
This templates works in farm solution only and this helps us to create an aspx page for SharePoint site.

5- Business Data Connectivity Model (Farm Solution Only):
This item enables you to integrate business data into SharePoint.

6- Content Type:
This item template helps us to create custom content type for SharePoint.

7- Empty Element:
This is a very helpful template and contains elements.xml file
8- Event Receiver:
This template helps us to create an event receiver for SharePoint.

9- List:
This template helps us to create a List for SharePoint.

10- Module:
This type of project item template helps us in deploying items to sharepoint server like image, css, master page etc.

11- Sequential Workflow (Farm Solution Only):
Through this type of project item template we can create Sequential workflow and this works in farm solution only.

12- Site Column:
This template helps us to create a site column for SharePoint.

13- Site Definition (Farm Solution Only):
This helps us to create custom site definition and it works only with farm solutions.

14- State Machine Workflow (Farm Solution Only):
Through this type of project item template we can create state machine workflow and this works in farm solution only.

15- User Control (Farm Solution Only):
We can add asp.net or sharepoint controls to user control and deploy to the sharepoint server.

In the above as there are written Farm Solution Only, means we can add project items to farm solution only, it will not work in sandboxed solution environments.

Disable Mobile access in SharePoint 2010

In this article we will discuss about how to disable mobile access in SharePoint 2010, so that mobile users will able to see the original version of the site rather than the mobile version of the site.

Also you can check out:

- Communities in SharePoint 2013

- SharePoint 2013 JavaScript Client Object Model Example

- SHAREPOINT\System account in SharePoint 2010

Recently I came accross a situation where my client wants to see the original version of the site rather than the mobile version of the site, whenever wants to see from mobile. By default SharePoint 2010 has a good feature for mobile users. If any request comes from mobile users then SharePoint will redirect the user to the mobile version of the site.

There will be 2 URLs for a site collection one is the Site URL and another one is the Mobile Site URL. If you will go to the site settings page then you will able to see the details in the Site Information section as shown in the figure below.

There are some modifications needed to disable the mobile access URL.

For this Open the directory C:inetpubwwwrootwssVirtualDirectories80App_Browsers

Inside that there will be a file called as compat.browser. Open that file using Notepad.

Now find for <capability name="isMobileDevice"  value="true" />

And Replace the above line with
<capability name="isMobileDevice" value="false" />

Then do an IISRESET which is very much important.

Now it should work.

Communities in SharePoint 2013

In this article we will discuss about the new communities feature in SharePoint 2013. You can also check more SharePoint 2013 articles.

Also you can check out:

- Architectural changes in SharePoint 2013

- SharePoint 2013 JavaScript Client Object Model Example

- Introduction to SharePoint 2013 REST service

SharePoint 2013 provides 2 new site templates to work with, namely Community Site and Community Portal. These templates are working same as SharePoint 2010 discussion board. Though SharePoint 2013 supports discussion boards also, but it has some advanced feature in these 2 new templates.

Community Site:
Community site is like forum where people in a organization go and do discussion in some topics. This helps in exchanging information between members inside organization.

Also you can organize discussions into various categories. Visitors can view the discussions and become members if they want to contribute to those discussions. Moderators manage the community by setting rules, reviewing and addressing inappropriate posts, marking interesting content as featured discussions, and so on. Moderators can also assign gifted badges to specific members to visually indicate that the member is recognized as a specific kind of contributor in the Community Site, such as an expert or a moderator. Each Community Site contains information about member and content reputation, which members earn when they actively post in discussions, and when their content is liked, replied to, or marked as a best answer.

There are different ways to deploy a community site:
1- By deploying a stand-alone community:
With a stand-alone community, you can create the Community Site at either a site collection or a site level.

2- By activating community features:
You can activate community features on any site, which provides the core Community Site pages, moderation, membership, and reputation functionality within the existing site without creating a separate Community Site.

The 2nd option is very much helpful, if you want to add community feature to your existing sites.

Community Portal:
The Community Portal is a search-driven page that surfaces SharePoint site collections and sites in the SharePoint farm that use the Community Site template. Users can visit the Community Portal to discover popular communities and to search for communities that they might want to join. The Community Portal relies on enterprise search for security trimming, and displays only Community Sites for which a user has at least read permissions.

Newsfeed in SharePoint 2013

In this article we will discuss about Newsfeed in SharePoint 2013. You can also check what are the features removed from SharePoint 2013?

Newsfeed is one of the popular improved feature in SharePoint 2013. The new Newsfeed is more likely to facebook or twitter. If you are familar with Twitter or Facebook, you will definitely like SharePoint 2013 Newsfeed.

The new UI is linke Facebook wall. In the new Newsfeed In the left hand side you will able to see your pics and links like about me, Task, Edit Profile, Site Contents. This links are helpful as its like quick links.

In the right hand side you can see the search box. And also see the your follow details. like how many people or documents or sites you follow. You can see this article to know more about follow/unfollow feature of SharePoint 2013.

In the middle portion of the wall, you will able to post Newsfeed like micro-blogging and also like in facebook you can give security for those content. Like you can set wether Everyone will be able to see the content or only sites you are following. For each thread you can also Like or give thread Reply also. You can also post youtube videos or document links also.
SharePoint 2013 supports @ and # tag. When entering a tag, SharePoint helpfully provides some recommendations for the user to select from with auto complete feature. If a user is identified using the @ tag, they will receive a Mention in their Newsfeed.

You can see Chris O'Brien wall for a UI looks:

Also you can check out:

- Create custom permission level in SharePoint 2013

- Create webpart page in SharePoint 2013

- Enable Sign in as Different User Option in SharePoint 2013

What is NOT there in SharePoint 2013?

In this article we will discuss some of the features which are not there in SharePoint 2013. You can check also check SharePoint 2013 Apps and browsers supported by SharePoint 2013.

1. SharePoint 2013 also removed one feature in SharePoint 2010 designer. Previously SharePoint 2010 designer has Design, Split and Code view for editing Aspx/Html pages. But SharePoint 2013 removed Design and Split view, now only Code view is presented in SharePoint 2013. This changed feature is

Difference between SharePoint 2013 and SharePoint 2010

As we know Microsoft has released the next version of SharePoint 2010 which is called as SharePoint 2013(preview), here we will discuss about some new features of SharePoint and some features missed from SharePoint 2010.

1- In SharePoint 2013 a very new thing introduced known as Cloud App Model. You can check this article for more on SharePoint 2013 apps.

Social networking feature in SharePoint 2013

In this article we will discuss something about social networking features improved in SharePoint 2013. In this article we will discuss some Twitter terms in SharePoint 2013 like follow, @, #tag etc.

A user can follow  People, Documents, Sites and Tags. Following is a good feature introduced in SharePoint 2013 to stay connected with people and content the user likes.

1. Follow or UnFollow:
A user can follow people, content etc. If you follow a people, then  the posts and activities of the followed people show up in the user's newsfeed. You can also work with follow using client object model or server object model. You can check this article http://msdn.microsoft.com/en-us/library/jj163133(v=office.15).aspx

User also can follow contents. When users following documents, sites, or tags, they get status updates about the followed items in their newsfeed. The features related to following content can be seen on the Newsfeed and the Following content pages on My Site. You can also work with follow or unfollow using SharePoint client object model or server object model. You can follow the msdn site for more. http://msdn.microsoft.com/en-us/library/jj163217(v=office.15).aspx

If you do not want any updates, you can UnFollow them.

2. @ and #tag:
Like in Twitter we use @ and #, Here in SharePoint 2013 we can use @ and # tag for content as well as people. If user enters a tag, SharePoint helpfully provides some recommendations for the user to select from. If a user is identified using the @ tag, they will receive a Mention in their Newsfeed, as well as an email the way it works in Twitter.

Apps in SharePoint 2013

As we know SharePoint 2013 has some improved features, in this article we will describe What are Apps in SharePoint 2013? You can also check hardware and software requirements in SharePoint 2013.

Also you can check out:

- Steps to create App Catalog site in SharePoint 2013

- How to get userprofile properties in SharePoint 2013 object model?

- How to disable mobile page redirection for SharePoint 2013?

An app for SharePoint is a web application that is registered with SharePoint using an app manifest. An app manifest is an XML file that declares the basic properties of the app along with where the app will run and what to do when the app is started.

Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. Apps integrate the best of the web and SharePoint; they are targeted, lightweight, and easy-to-use, and do a great job at solving a user need. Users discover and download apps from the SharePoint Store or from their organization's private App Catalog and install them on their SharePoint sites.

 You can use any language, such as HTML, JavaScript, PHP, or .NET, and you can also use Microsoft Visual Studio 2012 also.

Through apps in SharePoint 2013 we can read documents, add posts, can do searches, can connect with people, and so on. We can also connect with and from Search, workflow, social networking, taxonomy, user profiles, BCS, and more from SharePoint 2013 app using SharePoint APIs. We can use 1. REST and JavaScript APIs and 2. Managed APIs (.Net)

SharePoint 2013 apps can be hosted  in 3 different places like:

1- SharePoint 2013 apps can be hosted in SharePoint itself and the code is HTML and JavaScript. When you deploy a SharePoint-hosted app, SharePoint creates a new website called the app web. SharePoint 2010 web store pages, lists, and libraries.

2- Host in the cloud:
SharePoint automatically deploys the app into Windows Azure Web Sites and SQL Azure, and these apps run in the cloud.

3- Can be hosted in mix components in SharePoint and cloud:
SharePoint components run in SharePoint, and components hosted in the cloud run in the cloud.

SharePoint 2013 interview questions and answers

Here are some SharePoint interview questions and answers mentioned inline. Also you can check some SharePoint 2010 interview questions and answers as well as you can check some Asp.Net interview questions and answers here also.

Some SharePoint 2013 interview questions and answers:

What's new in SharePoint 2013 compared to SharePoint 2010?

SharePoint 2013 supports which version of .Net framework?

Difference between SharePoint 2013 and SharePoint 2013 preview?

What are the new features in SharePoint 2013 compared to SharePoint 2013 foundation server?

What are the SharePoint 2013 installation requirement?

What's new for developers in SharePoint 2013?

What's new for IT Pros in SharePoint 2013?

What are Apps in SharePoint 2013?

What are the different browsers supported in SharePoint 2013?

How SharePoint 2013 search works?

What are the new SharePoint 2013 search webparts introduced?

What are the new workflows introduced in SharePoint 2013?

Can I reuse a SharePoint 2010 workflow in SharePoint 2013 Site?

What are the new web parts introduced in SharePoint 2013?

Does SharePoint 2013 supports Passport authentication?

What are the new master pages and page layouts introduced in SharePoint 2013?

Does Sandboxed solutions exists in SharePoint 2013?

Can I open a SharePoint 2013 site using SharePoint 2010 designer?

Can I reuse a SharePoint 2010 designer workflows in SharePoint 2013 site?

What is Windows Azure Workflow in SharePoint 2013?

What are the new improvements in Visual Studio 2012 for SharePoint 2013?

How SharePoint 2013 authentication works?

What are improvements in Social features in SharePoint 2013?

How to migrate from SharePoint 2010 to SharePoint 2013?

Browsers supported in SharePoint 2013

In this article we will discuss about the browsers supported by SharePoint 2013. Also you can check the hardware and software requirements for SharePoint 2013. Also you can check out SharePoint 2013 download links here.

Here we will discuss the browser and version supported by SharePoint 2013 and also some browsers SharePoint 2013 supported with some limitations.

Internet explorer 9:
SharePoint 2013 supports Internet explorer 9 32-bit versions as well as it supports 64-bit versions with some limitations.

Internet explorer 8:
SharePoint 2013 supports Internet explorer 8 32-bit versions as well as it supports 64-bit versions with some limitations.

Google Chrome (latest release versions):
SharePoint 2013 supports Google chrome 64-bit with limitations.

Mozilla Firefox (latest release versions):
SharePoint 2013 supports Mozilla Firefox 64-bit with limitations.

Apple Safari (latest release versions):
SharePoint 2013 supports Apple Safari  32-bit with limitations.

Browsers NOT supported by SharePoint 2013:
The following browsers are not supported by SharePoint 2013:
- Internet explorer 7

- Internet explorer 6

- Google Chrome 32 bit version

- Mozilla Firefox 32 bit version

- Apple Safari 64 bit version

Apart from the above details, browser supports also depends upon the Operation system. Below is the operating systems that support browsers.
Internet Explorer 8 and Internet Explorer 9:
- Windows Server 2008 R2

- Windows Server 2008

- Windows Server 2003

- Windows 7

- Windows Vista

- Windows XP

Google Chrome and Mozilla Firefox:

- Windows Server 2008 R2

- Windows Server 2008

- Windows Server 2003

- Windows 7

- Windows Vista

Apple Safari:
- Mac OSX (Snow Leopard and Lion)

- Windows 7

- Windows Vista

Federated Search in SharePoint 2010

In this article we will discuss about What is Federated Search in SharePoint 2010. Compared to MOSS 2007 SharePoint 2010 has improved Search. You can also check my last article on Fast Search in SharePoint 2010.

Also you can check out:

- Get icon for different file types in SharePoint 2010

- Hide search box in home page in SharePoint 2013

- Query Search with SharePoint 2013 server object model

Basically Federated Search displays search results for additional content that is not crawled by your search server. We can see the data from several sources without indexing them. This is very much helpful when data is stored in external sources, where we do not have control to crawl or index the data. Federated search passes queries to external search engines. And the results are returned from there to the index server.

For example we can show results from Bing or Google in our SharePoint 2010 site.

SharePoint provides an out of box webparts namely Federated results, which is used in SharePoint to show Federated results. In the properties we can defined the Location.

Here is an advantages of federated search in SharePoint according to MSDN.
- You require no additional capacity requirements for the content index, as content is not crawled by SharePoint Enterprise Search.

- You can take advantage of a repository’s existing search engine. For example, you can federate to an Internet search engine to search the Web.

- You can optimize the content repository's search engine for the repository's specific set of content, which might provide better search performance on the content set.

- You can access repositories that are secured against crawls, but which can be accessed by search queries.

You can see another article on SharePoint Search through Server Object Model 2010 and Fast Search in SharePoint 2010.

The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled

There is a chance that you will get error as "The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled" while working with SharePoint 2010 search. There are different reasons for this, but one of the popular reason is because by default sharepoint crawl a file size of 16MB. So it will always crawl 16 MB file, and after this limit reached, SharePoint show the error message "The file reached the maximum download limit. Check that the full text of the document can be meaningfully
crawled".

Site templates in SharePoint 2010

Site template is a very useful concepts in SharePoint 2010. Site template is nothing but a solution file with the extension of .wsp. Site templates stored in the solutions gallery of the top level site. Also check one article on  Detecting Memory Leaks in SharePoint 2010.

This is nothing but a package of everything like list, libraries, pages, sub sites etc. While packaging we can also save its contents like list items, documents, pages, custom pages, master pages and configurations. But some components like user permissions will not saved.

We can use the site template (solution file) in different site collections, but that server should contain the site definition files installed. Suppose you make the site template that internally derived from the Team site definition, then the other server should have Team site definition installed. Even if you have any content type used then those content types must be recreated in the other site collection.

The .wsp file is actually a cabinet file that contains a lots of xml files like elements.xml, Feature.xml, ONet.xml etc.

We can save the site as a template by using SharePoint designer 2010 or by using the browser.

By using SharePoint designer 2010:

First open the site by using SharePoint designer (Go to Start -> All Programs -> SharePoint -> Microsoft SharePoint Designer 2010). Then click on Open site and give the URL of the site.

Once the site is opened, from the site tab click on Save as Template as shown in the figure below:

This will open the  Save as Template page in the browser. For the rest of the steps we will discuss in the 2nd
option by using browser. Since afterwards both are same.

By using browser:

First open the site in the browser. Then go to Site Actions -> Site Settings.

This will open the site settings page, Navigate to the Site Actions section and click on Save site as template as shown in the figure below.

This will open the Save as Template page where you can give the File Name, Template Name, Template Description, and whether you want to include the content or not. Then click on OK as shown in the figure below:

When click on OK it will show a confirmation dialog box like below.

The solution is stored in the solution gallery. In my case the URL is

http://bsahoo3:2500/sites/TestSiteCollection/_catalogs/solutions/Forms/AllItems.aspx

From browser also you can navigate to the solution gallery.
Go to Site Actions -> Site Settings-> From the Galleries section you can click on Solutions. You will get the site template that we have created just now.

Programmatically get SharePoint Themes

In this article we will discuss how to get all sharepoint themes programmatically using SharePoint 2010 object model. Also you can check my last article on how to create custom theme in sharepoint 2010. Also you can check one more article on how to programmatically apply theme to sharepoint 2010 site.

For this example I am writting the code in a visual web part. All the Themes of the site will be printed in a Label.

Full code:

<asp:Label ID="lblThemes" runat="server"></asp:Label>

using System;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Utilities;
using System.Collections.ObjectModel;
using System.Text;

namespace SharePointPOC.VisualWebPart1
{
    public partial class VisualWebPart1UserControl : UserControl
    {
        protected void Page_Load(object sender, EventArgs e)
        {
            GetAllTheme();
        }

void GetAllTheme()
        {
            StringBuilder sb = new StringBuilder();
            using (SPSite siteCollection = new SPSite("http://bsahoo3:2500/sites/TestSiteCollection/"))
            {
                using (SPWeb web = siteCollection.OpenWeb())
                {
                    ReadOnlyCollection themes = ThmxTheme.GetManagedThemes(siteCollection);
                    foreach (ThmxTheme theme in themes)
                    {
                        sb.Append("\n");
                        sb.Append(theme.Name);
                    }
                }
            }
            lblThemes.Text = sb.ToString();
        }
    }
}

Once you will deploy the code then you will able to see the list of all themes belongs to the site as shown in the figure below

File Not Found error in SharePoint 2010

In this post we will discuss how to resolve File not found error in SharePoint 2010.

Also you can check out:

- Programmatically get SharePoint Themes

- Bind dropdownlist from SharePoint list in InfoPath 2010

- Correlation ID in SharePoint 2010

I got the File Not Found error in SharePoint 2010.

Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator.

Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: ed7664ef-5896-4df5-865b-9feed32468ab

Actually I deployed a visual web part that I made using Visual Studio 2010. When I deploy the web part and try to add in the page I got the above error.

Reason:
There can be any reason for this like:

- As we know SharePoint 2010 supports .Net framework version 3.5, If we have selected the .Net framework version to 4.0 then we might got the issue.
- Another reason might be the Target framework. There are 3 target framework version like: x64, x86 and Any CPU. As SharePoint 2010 supports x64 only, so If you have selected target framework to x86 then the error might appear. The safiest approach is to choose target framework to Any CPU.

- Last reason, the way I solved the issue is quite different which is not related to any .Net framework. My visual web part contains some code like:

using (SPSite siteCollection = new SPSite("http://bsahoo3:2500/sites/TestSiteCollection/"))

Here I have given one site URL but I am deploying and trying to add the web part in a different URL. Once I changed the URL I did not got that issue.

Detecting Memory Leaks in SharePoint 2010

In this article we will discuss how we can detect memory leaks while working SharePoint 2010 object model. You can also check an article on SharePoint 2010 best practices. You can also check an article on SharePoint 2010 designer best practices and also you can check Causes of Performance issues in SharePoint 2010.

Memory leaks are very much in SharePoint. If we will not properly dispose SharePoint objects then you can get error like this: "Detected use of SPRequest for previously closed SPWeb object "

SPDisposeChecker is a very good tool to detect memory leaks in SharePoint 2010. First download

Out of the box SharePoint workflows

In this article we will discuss about the out of the box sharepoint workflows. Also you can check my last article on how to create a sequential workflow using Visual studio 2010 in SharePoint 2010.

SharePoint provides six workflows out of the box that end users can configure on their sites. And we do not need any developers knowledge to configure this workflows. We can configure these workflows using interface.

These out of box workflows are avilable according to the SharePoint 2010 version. In the free version

Working with SharePoint 2010 search web service

In this article we will discuss how to user search web service in SharePoint 2010. We will search by using SharePoint search web service. Also you can check about FAST search here. SharePoint 2010 search is very useful and advanced in SharePoint 2010.

There are different search web services available for SharePoint search and SharePoint Enterprise Search. The service url for sharepoint search is:

http://[URL]/_vti_bin/spsearch.asmx

The web service url for sharepoint enterprise search is:

Modify Zone of an alternate access mapping SharePoint 2010

In this article we will discuss how to change the zone of an alternate access mapping in sharepoint 2010 using Powershell. You can also check my last article on how to retrieve current zone in SharePoint 2010 using sharepoint 2010 object model.

There are 5 different types of zones available in sharepoint 2010 and they are:

Default
Intranet

Google map in SharePoint 2010 site

In this article we will discuss about how to show google map in a SharePoint 2010 site. Also you can check my last article on how to add JavaScript in Content Editor WebPart in SharePoint 2010.

First go to http://maps.google.co.in/maps

From the home page click on the link and copy the html code.

Save this code in the below location:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\STYLES

You can also chose your own location. I save the file with the name as GoogleMap.txt

Now edit the SharePoint page where you want the google map should appear.
Then click on Insert -> Web Part

This will open the web part gallary page. from there select Media and Conent and then select Content Editor web part and click on Add as shown in the figure below:

Then click on Edit Webpart as shown in the figure below:

Then from the content editor properties window in the content link give the url as below:

http://bsahoo3:2500/_layouts/styles/GoogleMap.txt

then click on OK as shown in the figure below:

Then the google map will appear in the page like below:

Also you can directly put the code to the Html source of the web part.

SharePoint Designer 2010 Best Practices

In this article we will discuss about what are the best practices we need to follow while working with SharePoint designer 2010. Also you can check a very good article on SharePoint 2010 Best Practices.

SharePoint designer 2010 is a very good tool to customize SharePoint 2010.

Here are some best practices we should follow while working in SharePoint designer.

- Never customize out of box master pages like v4.master. It is good to create custom master pages and use

Ghosting Unghosting in SharePoint

In this article we will discuss about Ghosting Unghosting concept in SharePoint. You can also check my last article on Site Pages and Application pages here.

Site pages that are loaded from the file system are known as ghosted pages. And when these pages have been customized they are known as unghosted pages. Because once you customize files using SharePoint designer then the changed page content are stored in content database rather in the file system. And after that

How to Check if your SharePoint 2010 Web Application Uses Claims Authentication?

In this small article we will discuss how we can check if a SharePoint 2010 web application is using claims authentication or not. Also you can check my last article on How to Configure Claim Based Authentication in SharePoint 2010 here and also you can check How to Switch from Classic to Claims Authentication in SharePoint 2010 here.

To check if a SharePoint 2010 web application is using claims authentication or not we can use PowerShell command. This command will return True if the web application uses claims authentication and returns False if it does not use claims authentication. Below is the PoweShell command.

$web = Get-SPWebApplication “<URL for Application>”
$web.UseClaimsAuthentication

Refer the figure below for the above command.

Also you can check out:

- Get icon for different file types in SharePoint 2010

- How to Configure SSRS for SharePoint Integration Mode in SharePoint 2010?

- Different authentication types supported in SharePoint 2013