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.