Hello
I am having a APP server and a WFE server. On the APP server i have my CA and all the services that I need. On the WFE I only have the Web appliction and the distributed cache services running.
All my servers are virtual.
I have logged in to the APP server, created an Web-app, and I now can access the Web-app via http//appserver, and from outside the server via http://appserver.domain (trough AAM).
When i login to my WFE server, and browse to the IIS, and the find the Web-app under sites, and browse it, I am getting a error,
“Sorry something went wrong – file not found”.
The ULS log says:
“Cannot finde lookup info for request uri http://localhost/…
AAM have not been config. Users or service are accessing the site http://Appserver/ with the url http://localhost…
… add the http://localhost as an AAM response url”
If there is a logical solution to this, i would like some steps, or guidlines in how to get it working, and learn from it. If the solution is AAM then I would love a simple guide to where in the AAM to put, and what to put in.
And maybe it is something really simple that I am overlooking. Google was not a great help.
Thanks 🙂
Hi,
I think when you are doing localhost on your app server it basically becomes appserver, which matches your web app host header and therefore loads correctly. Whereas when you do localhost on your web server it processes it as the name of the web server, which is not that of which is associated with the web app.
I mean you could probably add in an AAM to get to the web app on another name but to me this is so unecessay for what you are trying to achieve.
Regardless of what the server names are you should have just created a web app with a host header of SharePoint and then an A record within DNS resolving SharePoint to the IP address of the web server. Is this not possible?
If you are looking to utilse the new host name sit collections then you would configure the web app differently.