theme-sticky-logo-alt
theme-logo-alt

Troubleshooting setting up an environment for apps for SharePoint 2013

February 13, 2013
by Vlad Catrinescu
42 Comments

While exploring SharePoint 2013, I decided to configure my SharePoint 2013 environment in order to be able to use apps from the SharePoint store, and also use advanced Service Applications, such as Machine Translation services.

As you know, there is not a lot of documentation on SharePoint 2013 yet, so I decided to post the two errors I encountered during the setup, with their fixes!
I used the Technet Guide  to configure my farm, however I am working on a Step by Step guide with Screen Shots and detailed information to help you get it down on the first try. (Will be out 18 February 2013)

Error 1. 

 Let’s Try this again…
Everything is fine, but we had a small problem getting your license. Please go back to the SharePoint Store to get this app again and you won’t be charged for it.
If ‘Retry’ doesn’t work, return to your site and try again later.

Let’s try this again
This is just an error because you are probably using the Farm Account to buy the Application! (Logged in as System Account)!  Log in as another user and it will work just fine.
For more Info on Service accounts visit this link 

Error 2

Server Error in ‘/’ Application
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL
and make sure that it is spelled correctly.
Requested URL:

This error is a bit more tricky.  The source of the problem is that your apps do not run on the same domain as the SharePoint server.  (ex:  SP Server domain:  vlad.com   App Domain: vladapps.com) and IIS is not able to connect the two. The good news is that it’s really easy to fix (by following my tutorial right here )
There is a simple way to fix it, by creating a web application and root site collection without a host header!

Here are the steps:

1.       Go into Central Administration and click Application Management

2.       Go into Manage Web Applications

3.       Click on New, set the Port to 80 and do not enter anything in the Host Header


 The rest is as usual:

 After that, you create a Site Collection using the Team Site

 Now, we have to delete the Default Web Site from IIS!

            Go into IIS Manager as an administrator, and expand your Sites.  Right click on the Default Website, and select Remove
And now it should be fixed!
If you encounter other errors and know the resolutions or need help contact me!

Leave  a comment and don’t forget to like us on Facebook here and to follow me on Google+ here and on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check the SharePoint Community Partners list for other great SharePoint Sites, and vote for my blog if you like my content!

SharePoint Server
Previous Post
Free SharePoint Server 2013 Resources Part 4
Next Post
Step By Step Guide to configure the Managed Metadata Service Application for SharePoint 2013

42 Comments

  • March 27, 2013 at 11:55 pm
    Jonathan Whittaker

    Hi Vlad,

    Do you really need to delete the default website or can you just stop the web application in IIS?

    Reply
    • March 30, 2013 at 12:32 pm
      Vlad Catrinescu

      I guess you can leave it there since it’s stopped by default. Try it without deleting, if it works = it’s fine. If no, delete it :).

      Tell me if it worked!

      Reply
    • April 1, 2013 at 10:51 pm
      Jonathan Whittaker

      Just stopping the default website works. I can now access Store Apps and add them as web parts to pages. Looks like the CNAME Alias was also pointing to the TFS server instead of the SharePoint server -_-

      Reply
  • April 23, 2013 at 2:07 am
    Brian Shurley

    Thank you, thank you, thank you! I’ve been working on this problem for a while and this was the answer. One thing worth mentioning is that you can delete the new Web Application after creating it (at least I did and didn’t see any problems with it).

    Reply
  • April 23, 2013 at 9:07 pm
    Brian Shurley

    I was mistaken… I just hadn’t done an IISRESET after the deletion. You have to leave the other web application in place…

    Reply
    • April 25, 2013 at 7:16 pm
      Vlad Catrinescu

      Thanks for the update! I am glad I could help you solve it!

      Reply
  • April 29, 2013 at 7:23 pm
    Anonymous

    I followed the instructions that you have for Creating a new web app and disabling the default iis site. However, now when I open up the app the page is just blank. There are no errors or anything. Also, the app store is telling me that apps are turned off again.

    Reply
    • April 30, 2013 at 2:06 pm
      Vlad Catrinescu

      Any “Acces Denied” errors in the Event log for SharePoint or SQL?

      Reply
  • May 3, 2013 at 8:15 pm
    Anonymous

    My SharePoint site is already on port 80 so I am not able to create another web application with port 80. It says there is already a site on port 80.

    Reply
    • May 3, 2013 at 8:18 pm
      Vlad Catrinescu

      is the default Website stopped or deleted?

      Reply
    • May 9, 2013 at 5:01 pm
      Erin

      I have the same issue – my sharepoint site is already on port 80. Were you able to resolve this?

      Reply
  • May 9, 2013 at 8:16 pm
    Erin

    Nevermind… DNS was set up incorrectly.

    Reply
  • August 1, 2013 at 8:23 am
    tommy

    Hi Vlad

    i have already sharepoint on port 80 ,what can i do instead? , i get error that port is alreday used?

    /tommy

    Reply
    • August 4, 2013 at 8:24 pm
      Vlad Catrinescu

      You can have more than 1 SharePoint Web Application on port 80. You need one with no host header in order to make sure apps work!

      Reply
      • August 6, 2013 at 10:55 am
        Tommy

        Thansk Vlad
        this help me out
        New-SPSite http://nohostheaders -OwnerAlias “Contoso\admin” -HostHeaderWebApplication $w -Name “nohostheaders” -Template “STS#0”

  • October 18, 2013 at 2:26 pm
    Pavel

    Hi,

    I had the problem when I tried to open the app page and it was blank. I have looked at the event log and saw that there is not enough permissions for the SP_ProfilesAppPool account, which is used only for the mysite web application.

    Only when I have added to this account sysadmin privileges in SQL server, apps started to work.

    Might you have any idea why?

    Reply
    • October 22, 2013 at 11:22 am
      Vlad Catrinescu

      Try only giving it the SPDataAcces role on the ContentDB where the app page is. tell me if it works!

      Reply
  • October 22, 2013 at 4:41 pm
    Pavel

    I have resolved it for now, by setting SP_AppPool account for my site. The same account as my other web applications. After I have done it everything worked fine even without sysadmin.

    Reply
  • December 1, 2013 at 1:52 pm
    Jeremy Thake

    Thanks Vlad. I had modified my “SharePoint – 80” web application that SharePoint had created to a SSL’d host header one. I ended up deleting that. recreating a new “SharePoint – 80” and then a second web app for the SSL’d host header one. What I had to do to get the SharePoint hosted to work is to add an additional binding in IIS for “:443” with no host header for my SharePoint Hosted Apps to work in SSL’d host header one. SharePoint hosted worked fine in first web app.

    Reply
  • December 16, 2013 at 8:43 pm
    lostman

    great documentation on this!
    I have gottedn my sharepoint site and apps to work perfecty on my internal networks and domain PCs and even published my site on internet and have all access mappings for primary domain. now when I try to access a link from the internet, it does not take me to the web app domain server but back to the primary domain sharepoint? is there another mapping I am missing here?

    Reply
  • March 22, 2014 at 4:18 pm
    Andre

    Hi vlad,
    I have the Problem when im Starting a app. Than i have These error:
    App management Service Proxy is Not installed

    Have you a Solution? All Services started

    Reply
    • April 24, 2014 at 10:13 pm
      Vlad Catrinescu

      Looks like the script didn’t install it! Can you post a screenshot?

      Reply
  • January 29, 2015 at 2:17 pm
    Andy

    I followed all the instructions to a T and I am still unable to access my SharePoint store. I have spent weeks on this and cannot find any reason why I cannot access this. Can you help?

    Reply
    • January 29, 2015 at 10:36 pm
      Vlad Catrinescu

      Can you give me some details on the error, logs or stuff like that so I can help?

      Thanks!

      Reply
  • June 9, 2015 at 2:47 pm
    Neel

    Vlad,

    I tried creating a new web application at port 80 and created a root site collection, it is still not helping me out, it is displaying page cannot be displayed, it was uploaded without issues, when the browser came up, that is where the issue, we have set it up with new zone *.companyapps.com pointing to internal domain (company.com is external), do you know of how to set this up properly. for example, out IT person says that microsoftapps.com is created, but it cannot point to Microsoft.com as it is external and I will not be able to ping, need help or any ideas and suggestions

    Thank you
    Neel

    Reply
  • November 18, 2015 at 4:45 pm
    bhashwar bhattarai

    Hello Vlad,
    I am in serious problem. After deleting the default web application in my production environment, users were not able to open the pages. So to solve the problem i add back end host connection, and disable loop back check in the registry on two of our WFE. Now its working fine. But people are saying that i will be in big trouble someday.
    Please Help!!!!!!!

    Reply
    • November 24, 2015 at 12:10 am
      Vlad Catrinescu

      Deleting default web app shouldn’t have anything to do with it. Why do people say you will be in big trouble?

      Reply
      • November 24, 2015 at 11:09 am
        bhashwar bhattarai

        Thank You for the Reply Vlad,
        After a month now, i went back and deleted the back end host connection and disable loop back check from the registry that i had added in the two wfe’s. My sites are running perfectly fine.
        Thank You

  • November 27, 2015 at 9:42 am
    Cris

    Dear Vlad,
    thanks a lot for this post.
    I also have this issue and I think there something I’m doing bad… In IIS have yet a Sharepoint 80 site this one is mycompany Intranet and so I d’nt delete anything, I have deleted de Default Website. So when I try to create a new Site in port 80 from sharepoint Foudnation wiht no host name , I alway have the same problem: this site is used by Sharepoint, try to change port or the name…
    What am I doing wrong???
    Thanks in advance

    Reply
  • December 7, 2015 at 7:09 pm
    Ryan

    What is the work around when a site is already running on port 80?

    “The directory C:\inetpub\wwwroot\wss\VirtualDirectories\80 is already being used by another IIS Web Site. Choose a different root directory for your new Web application.”

    Reply
    • December 11, 2015 at 7:50 am
      Vlad Catrinescu

      is it a site other than the default website? Is it a SharePoint Site?

      Reply
      • December 14, 2015 at 2:27 pm
        Ryan

        It’s not a SharePoint site. It is an IIS site that redirects to the HTTPS SharePoint site.

      • June 30, 2016 at 5:04 pm
        Leo

        I have the same issue as Ryan, but in my case, it is a sharepoint site what I have running in port 80 with a host header. It was initially created without a host header, but then I needed to change its default zone with a public url to be able to access it from outside my network. Please let me know if is there any workaround you can think of. It will be greatly appreciated.
        Thanks

  • December 14, 2015 at 8:30 am
    Sanket

    I already have default web application on port 80 without Host header after configuring SharePoint with multiple site collections. Also I have two more WebApplication on port 80 with Host Header.

    Now I am not able to create web application on port 80 as one web application is already in place. Can I use any other web application and do I have to delete default web site from IIS from all SharePoint Servers.

    Please help and can I have step by step guide to configure APP model for SahrePoint Farm.

    Reply
  • December 14, 2015 at 9:04 am
    Sanket

    I already have default web application on port 80 without Host header after configuring SharePoint with multiple site collections. Also I have two more WebApplication on port 80 with Host Header.

    Now I am not able to create web application on port 80 without host header as one web application is already in place. Can I use any other port for web application and do I have to delete default web site from IIS from all SharePoint Servers.

    Note : When I configured Sharepoint All my services were started including App management Service. Also App Management Service Application were already created.So I have only Configured subscription service application.

    Please help and can I have step by step guide to configure APP model for SahrePoint Farm.

    Reply
  • April 19, 2016 at 10:44 am
    Niyaz

    Vlad

    I’m facing “Page cannot be displayed” after downloaded the app from SharePoint app Catalogue site. Can you please help me to figure it out?

    Niyaz

    Reply
  • May 20, 2016 at 12:25 am
    AR

    Hey Vlad. Great post ! Will this work same even for the SSL ? Do we have to create a blank website on port 443 instead of 80?

    Reply
    • May 28, 2016 at 4:36 am
      Vlad Catrinescu

      Yes, for SSL you need to create that blank root Web App on 443! Make sure to also add your Certificate on your binding.

      Reply
  • August 10, 2017 at 10:12 am
    Umair

    Hi. Your second tip helped me with my issues thank you! However, there is one issue still. When I’m in the app web and using the app. The back link in the top left doesn’t work. If I click on it, it doesn’t take me back to the host web. Instead it keeps me in the app web and shows me a “Sorry, this site hasn’t been shared with you.” message.

    Reply
  • December 15, 2017 at 2:56 am
    Carter

    Hi, Vlad,
    I was caught in error 2 as your post. I setup a testing environment with everything in one machine, it works great.
    But I still got the issues on my 2 WFEs work in NLB mode. Do you think there might be some issues with my hardware NLB settings? E.g. do you think I should add the app URL in NLB, too?

    Reply

Leave a Reply

Top Learning Resources

15 49.0138 8.38624 1 0 4000 1 https://vladtalkstech.com 300 1