Deploying SharePoint 2010 Solution on SharePoint 2013

As you know, in SharePoint 2010 there was 14 hive where you deploy your files. And then you reference them like below:


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

Virtual Path: “/_layouts/<your folder>/<your files>”


In SharePoint 2013, there is new 15 hive

Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS

Virtual Path: “/_layouts/15/<your folder>/<your files>”


If you have SharePoint 2010 solution (.wsp file) and you need to deploy it on SharePoint 2013, then you have the following options:

First, you have to add the solution to your farm using PowerShell as following:

  • Add-SPSolution C:\SP2010Project.wsp


  • Deploy to 14 hive è
    Install-SPSolution sp2010project.wsp
  • Deploy to 15 hive è Install-SPSolution sp2010project.wsp -CompatibilityLevel 15

Virtualizing SQL Server in SharePoint 2010 Farm is not Recommended

The database server is responsible for storing, maintaining, and fetching data for other server components and services.

Virtualization of the database server is not recommended. Reasons to avoid virtualizing the database server are as follows:

  • Virtualization introduces latency downstream in the application and UI server components of a SharePoint farm. If every data request takes more time, the scenario quickly becomes a challenge, especially when a single transaction needs multiple round trips for completion.
  • The database server experiences heavy CPU, memory, disk I/O, and NIC usage.
  • If overall performance evaluation or virtual machines are not adequately specified, end users may experience slower response times and, in background processes, slower performance of long-running operations, which can increase operation timeouts.

for more details, visit this link  [Page 24]

New Document Disabled in PowerPivot Gallery

When you create a new PowerPivot site and go to Power Pivot Gallery, you find the “New Document” disabled by default.


Go to “Library Settings

Click on “Advanced settings

Choose “Yes” in “Allow management of content types?

Now,,,, fixed

Manage content and structure in SharePoint 2013

In SharePoint 2010, there was a link for “Manage content and structure” as below image.

In SharePoint 2013, this link has been removed from this menu.

So, where is the link??

Site Settings è Site Administration

Here is a screen shot

Get HTTP Sub status Number for Troubleshooting

When you get an error like 401,404 or 500 you want to troubleshoot it, the first thing you should do is determine what “type” (i.e. HTTP sub status).

Go to %SYSTEMROOT%\System32\LogFiles\W3SVC########\

Replace ########with the number in the above screen

EX: %SYSTEMROOT%\System32\LogFiles\W3SVC86032275\

The W3C log entries look like the following, with the HTTP status, substatus, and Win32
error codes highlighted.


For all HTTP Status code, visit here : The HTTP status code in IIS 7.0, IIS 7.5, and IIS 8.0

Save InfoPath Attachment to SharePoint 2010 Document Library

I have a requirement where the business needs to save an attachment form InfoPath form to SharePoint document library direct.

1: Build the InfoPath form

Create three fields

  • WebSiteURL: string
  • DocLibName: string
  • Attachment: base64Binary

2: Build the Web Service

3: Connect InfoPath to Web Service

For more information, Calling Web Service from InfoPath 2010 with Parameters

4: Verify

Download source files (InfoPath & Web service)

SharePoint 2013 Workflow is not available

After installing SharePoint 2013 and SharePoint Designer 2013, you will notice that no SharePoint 2013 workflow is available!! Only SharePoint 2010 is there.

We can summarize the steps:

  1. Install Workflow Manager 1.0
  2. Configure Workflow Manager 1.0
  3. Register Workflow Manager 1.0
  4. Verify Workflow Manager 1.0

To install SharePoint 2013 Workflow, do the following:

  1. Install Workflow Manager 1.0 from here

Click on Install button to start installation.

  1. After finishing downloading and installation, you will see the following screen shot

  2. The Workflow Manager Configuration Wizard automatically appear

  3. User the first option, you can follow this link for more
  4. Register your workflow manager with your SharePoint farm

    Register-SPWorkflowService –SPSite “<SiteCollection>” –WorkflowHostUri “http://ServerName:12291″ –AllowOAuthHttp

  5. Verify using SharePoint Designer 2013

    Note: a new IIS website added to your IIS