Sign in as different user menu is missing in SharePoint 2013

It’s been noted that the “Sign in as a Different User” menu command is missing in SharePoint 2013. This “Sign in as Different User” menu item is very useful when testing applications, but it can lead to some problems when opening documents. So, it may be for these reasons that the option has been removed in SharePoint 2013.

You can add the menu item back in, but I would suggest only doing this on test or development SharePoint servers.

To do this, please follow the below steps:

1.      Go to the file \15\TEMPLATE\CONTROLTEMPLATES\Welcome.ascx and open in a text editor.

2.      Add the following element before the existing element with the id of “ID_RequestAccess”

           <SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser"

            Text="<%$Resources:wss,personalactions_loginasdifferentuser%>"  

            Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>" 

            MenuGroupId="100"  Sequence="100"  UseShortId="true"

           />

 3.      Save the file.

Now, go to the menu and check. It shall be displaying.

Hope this helps.

Filter web parts are not displaying in Add Web part catalog

Reason:  Your server is not Enterprise version or you did not activate the features. If your server is enterprise version then directly follow the “Enable enterprise Features steps”

If  your SharePoint server is not enterprise version then u will not be able to see filter webparts. This means your server is standard version, first update your server to Enterprise version and then you will find filter webparts.

Solution: (Requires Product key to activate to Enterprise version)

1.      Go to Central Administration

2.      Select “Upgrade and Migration” heading.

3.      In Update and Migration page select Enable Enterprise Feature.

4.      Now, select Enterprise option and enter the Product key to activate the feature.

Enable enterprise features

1.      Go to site collection where you want to use filter webparts

2.      Go to site settings

3.      Under Site Collection Administration select site collection features

4.      Activate “SharePoint server enterprise site collection feature” feature.

5.      Now go to the sub-site where you want to use webparts. Then go to Site settings

6.      Go to “Manage site features”

7.      Activate "SharePoint server enterprise site feature" feature.

8.      Now go and check whether filter webparts are displaying or not. It will work.

Hope this helps.

New option is disabled in central administration -> manage web application. How to Enable it?

In order to enable “New” option in “Manage Web Application” tab, please go through the below steps:

1.     Go to Start.

2.     Type Central Administration.

3.    Select SharePoint Central Administration -> open (right click and select “Run As Administrator”)

4.    Now your browser shows all the options.

Reason: The browser is not run under administrator mode.

Hope this helps you.

Copy/Move SharePoint 2010 Designer Workflows

Most often, we require moving or copying SharePoint designer workflows from one site or site collection to another. There is an option in SharePoint Designer 2010, "Export to Visio" which exports your workflow as .vwi file, and can be imported in to another site using the option "Import from Visio".  But when you try that option, you will get the below message.

This workflow cannot be imported because it was created in SharePoint Designer for a different site, or the original workflow has been moved or deleted. To move a workflow between sites, use× Save as Template (.wsp file) instead of a Visio workflow drawing.

So, to achieve our goal (copy/move workflow) please follow the below mentioned steps : 

1.      In the source site (From where you want to copy WF), create the required workflow and publish it.

2.      Now select Export to Visio option which allows you to save the workflow with a .vwi extension. (Let’s refer this as source workflow).

3.      Now go to the destination site where you want the workflow to be copied, and create a new workflow with the same name as the previous one & publish it.

4.      Now select Export to Visio option which allows you to save the workflow with a .vwi extension. (Let’s refer this as destination workflow).

5.      Now you will be having two .vwi files (one of source workflow’s – SourceWorkflowName.vwi and other of the destination workflow’s – DestinationWorkflowName.vwi). Now add .zip extension to both the files. Now your files names should be SourceWorkflowName.vwi.zip & DestinationWorkflowName.vwi.zip.

6.      Now open both the zip files, copy workflow.xoml.wfconfig.xml from destination workflow to source workflow. (Its destination to source and not source to destination).

7.      From now on, we will not use the file DestinationWorkflowName.vwi.zip.  So ignore that file.

8.      Remove the .zip extension from SourceWorkflowName.vwi.zip which gives you the SourceWorkflowName.vwi file.

9.      Now, go to the destination site, open workflows and click Import from Visio and browse to the SourceWorkflowName.vwi file.

10.  That’s it and your workflow is copied. You can publish the workflow and run it.

NOTE: In case if your list’s GUID’s (for those lists that you have used in workflow – tasks list, history list or any other lists used in workflow steps) have been changed from source & destination site, you may need to update those steps in the workflow.

Hope this helps you.

Microsoft.SharePoint.SPEndpointAddressNotFoundException: There are no addresses available for this application.

Microsoft.SharePoint.SPEndpointAddressNotFoundException: There are no addresses available for this application.    at Microsoft.SharePoint.SPRoundRobinServiceLoadBalancer.BeginOperation()     at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.<>c__DisplayClass2f.<RunOnChannel>b__2d()     at Microsoft.Office.Server.Security.SecurityContext.RunAsProcess(...)     at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.RunOnChannel(...)  .....

The Problem with the above message is caused by the Service Application "Managed Metadata Web Service" and Proxy being configured and started, however The Service On Server Managed Metadata Web Service  not running.

Solution : 

Step 1 : Central Admin -> System Settings  -> Manage Service on Server (Under Servers Heading)
Step 2 : Start "Managed Metadata Web Service".

Now, the Exception will be removed and works fine. In order to use this service, you need to wait for some time because it takes time to apply changes in server level.

Extension for solution : 

The same message might appear in relationship with any service/service application. What you need to do is to check the call stack for the service application name and check the associated service on Server status.

Create Group in SharePoint 2010 Programmatically

To Create group in site collection level use the following command:

   string siteUrl = SPContext.Current.Web.Url;

   using (SPSite spsite = new SPSite(siteUrl))

   {

      using (SPWeb web = spsite.OpenWeb())

      {

          web.SiteGroups.Add("GroupName", web.CurrentUser, web.CurrentUser, "GroupDescription");

          web.Update();

      }

   }

To Create group in site level use the following command:

   string siteUrl = SPContext.Current.Web.Url;

   using (SPSite spsite = new SPSite(siteUrl))

   {

      using (SPWeb web = spsite.OpenWeb())

      {

          web.Groups.Add("GroupName", web.CurrentUser, web.CurrentUser, "GroupDescription");

          web.Update();

      }

   }

How to find public key token for a .NET DLL or assembly

Steps :
1. Go to Start and search for "Visual Studio Command Prompt" and open it.
2. Type the DLL file path and type the following command.
     Command: sn -T myDll.dll

Example: E:\ExampleProject\bin\Debug> sn -T ExampleProject.dll

The output will be as follows:

Microsoft (R) .NET Framework Strong Name Utility  Version 4.0.30319.1
Copyright (c) Microsoft Corporation.  All rights reserved.
Public key token is 4e4ed2e4e49b94ff