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 🙂
This is a nice post. I mean you could probably add in an AAM to get to the web app on another name but to me this is so unnecessary for what you are trying to achieve. Thanks for sharing…
https://uaetechnician.ae/dubai-handyman-service
Hi Henry
Again, thanks for the afvices. I think that you are right about, I just should have created the DNS record.
I think what I am seeking and what you are suggesting is this approach http://thuansoldier.net/?p=1323 . It is for SP10 but besides I am using Claims now in SP13 I dont think there are any other differences.
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.
Hey
I will look at your answers. It must be something simple, and I think that it maybe is to simple for you ;).
Yep, my web-app has the same name as the app-server, so maybe it could be something with that.
My mission is to have one name for the web-app that is generel for all servers and clients, so insted http://appserver or http://appserver.domain.com, http://sharepoint.domain.com.
So I think that I have to make a DNS entry sharepoint.domain.com, and then AAM it. I am though not sure on alle the steps in this process.
So is the web app the same name as the app server as I think this is why localhost works for you on the app server and not the web server. If I have understood you correctly?
Also do you need to hit the site on localhost? As if I do this in an environment from a web server and the web app has a host header of say portal it just presents me with the IIS 8 splash screen which is what I would expect and is probably being presented by the default site in IIS. Although I appreciate you do not get this.
Can I also recommend that you take a look at Host Name Site Collections as this may be a route you would like to go.
