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
Test the app, and if not abble, delete default web site ........................................................
Now, we have to delete the Default Web Site from IIS!
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!
Comments
Post a Comment