SharePoint 2013: Error occurred in deployment step 'Install App for SharePoint': Failed to install App for SharePoint.

The scenario: You want to start building SharePoint-hosted app for SharePoint 2013 on your dev machine(!). You have SharePoint installed (and some basic configurations about) SharePoint 2013. You download working code form internet or use an empty VS 2012 app template. Run VS solution and you get the following error.

The problem: Error in VS 2012: “Error occurred in deployment step 'Install App for SharePoint': Failed to install App for SharePoint.”

The solution: Verified that you have correctly configured your environment to support SharePoint-hosted app.

Notes:
Visual Studio doesn’t give you much information why the step 'Install App for SharePoint' failed.
In my case – I lose one day before I realized that I haven’t configured my environment. (Sound stupid but thinking about all this app stuff, I have missed the basic.) So if you experience the above error, I will recommend you first to double check if you have everything in the list:

- developing against Developer Site template;
- service applications (App Management Service and Subscription Service) are configured and running
- App domain setup is performed (records in host file or DNS)
- LoopbackCheck is disabled
- IE is configured for your app domain

There are many post about setting all this. Just search for “sharepoint 2013 on-premises app configurations”. Here is the MSDN article which can be a starting point.

Comments

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed. The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before. There is a new control called ClientPeoplePicker . How to use it: 1. Add this references <% @ Register TagPrefix ="wssawc" Namespace ="Microsoft.SharePoint.WebControls" Assembly ="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 2. Add the following control declaration < wssawc : ClientPeoplePicker Required ="true" ValidationEnabled ="true" ID ="peoplePicker" runat ="server" ...

SharePoint 2016: High Availability Farm Topology

MinRole concept was introduced in SharePoint 2016 and it aims to simplify the process of designing the farms. However, I still find ambiguous information about the count of servers in SharePoint 2016 farm. Let's ask ourselves the question - What is the minimum number of servers which allow High Availability MinRole farm? According to technet we have the following options: Small High Availability (HA) MinRole farm 4 Four servers with two shared roles: · Two Front-end with Distributed Cache servers · Two Application with Search servers Medium High Availability (HA) MinRole farm (Search optimized) 6 Six servers with both dedicated and shared roles: · Two Front-end with Distributed Cache servers · Two Application servers · ...

SharePoint User Group Bulgaria

In the past year I invested my free time in activities related to the SharePoint User Group Bulgaria. This is the reason why I stopped writing in this blog. Please start following this new place www.sugbg.com . I promise you that you will find there truly valuable content.

SPObject.Resolve()

Search This Blog