Tuesday, April 9, 2013

SharePoint 2013 installation issues

Here i have given some some issues when you are installing SharePoint 2013.

these issues are listed earlier but made some changes according to the Release version of SharePoint 2013.

Here is the links for the issues :

Issue 1

Issue 2



visual studio sharepoint not installed

Here is one of the typical issue you will find when you try to create your first SharePoint APP in VS 2012 Ultimate.

visual studio 2012 sharepoint not installed on you server.

This will occure when you try to use App for SharePoint 2013 template in VS 2012

Root cause :

Untill you install Microsoft Office developer tools for SharePoint your Dev platform will not recognize your sharepoint.

Resolution :

You need to install Web Platform installer 4.0 or 4.5 based on your SharePoint Version ( Choose the latest default ):

This download file you can get here

After installation is done open the Web Platform installer.

Search For SharePoint in search area

Then Select Microsoft Office Developer tools for Visual Studio 2012 RC and click on install.

Then Restart is required to make this will effect without fail.

This will fix the issue.



Thank You !!



sharepoint 2013 sign in as different user

This is strange that Microsoft has removed the SignIn as diffarent user option from welcome user control.

But i found very interesting article by nick how to enable this option.

Click on this link to find the solution



Thank you !!

Monday, April 1, 2013

SharePoint The Subscription Settings service and corresponding application and proxy needs to be running in order to make changes to these settings

When you are working with sharepoint usually you need to configure the APP url in Central administration.

But when you click on the Configure App URL section in Central administration you will get this URL.

Root Cause :

This is expecting A new service application created on its dedicated App Pool is required to be created in SharePoint.

This Can be achieved with PowerShell scripting.

Here is the Piece of code ( This has taken from MS reference documents Change it according to business needs ):

You must runt this powershell and make sure you change the Managed account name in the script.

Run PowerShell as Administrator





add-pssnapin "Microsoft.Sharepoint.Powershell"

$manaccount = Get-SPManagedAccount SP2013Server\Administrator

Remove-SPServiceApplicationPool -Identity SettingsServiceAppPool

$appPoolService = New-SPServiceApplicationPool -Name SettingsServiceAppPool -Account $manaccount

$appService = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPoolService -Name SettingsServiceApp -DatabaseName SettingsServiceDB

$proxyService = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $appService 

This will create a service application in Sharepoint then you can configure the URL in CA App section.

SharePoint The requested service, could not be activated. See the server’s diagnostic trace logs for more information



This is the issue you will find when you deploy APP in sharepoint evnivronment.

Here this issue will arise not just because of the service is not running.

Root Cause :

The root cause for this issue is lack of memory in the machine from sharepoint end.

Resolution :

Open Services wizard :

Go to Start -> type Services.msc

This will launch the services windows there you can find the service with name Sharepoint search host controller

Just right click on and Restart ( It will taken around 4-5 mins time ). But it will release all the leaked memory and consumed memory. You can verify the same in memory section from you windows manager just for your verification.

Then ReDeploy your solution this time it will sure go on successfully.


SharePoint Memory gates checking failed because the free memory is less than 5% of total memory. As a result, the service will not be available for incoming requests. To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element



This is the one of the strange issue you will find when you deploy your SharePoint App to app domain.

This issue will occur because of the memory issue most of it will be consumed by the SharePoint.

Here is the solution :

Open Services wizard :

Go to Start -> type Services.msc

This will launch the services windows there you can find the service with name Sharepoint search host controller

Just right click on and Restart ( It will taken around 4-5 mins time ). But it will release all the leaked memory and consumed memory. You can verify the same in memory section from you windows manager just for your verification.

Then ReDeploy your solution this time it will sure go on successfully.