When you use standard hostname given to the address of the loopback network interface, “localhost”, as URL to access the SharePoint Site Settings page of any sub sites for example: http://localhost/subsite1/_layouts/settings.aspx, a blank page will be displayed and the following entries will be logged in the SharePoint ULS:
- 01/29/2011 18:43:04.10 | w3wp.exe | (0x1CB4) | 0x1DDC | SharePoint Foundation | Logging Correlation Data | Name=Request (GET:http://<<SERVERNAME>>:80/<<SUBSITE>>/_layouts/settings.aspx)
- 01/29/2011 18:43:04.11 | w3wp.exe | (0x1CB4) | 0x1DDC | SharePoint Foundation | Monitoring | Leaving Monitored Scope (Request (GET:http://<<SERVERNAME>>:80/<<SUBSITE>>/_layouts/settings.aspx)). Execution Time=1.96949915988322
- 01/29/2011 18:43:04.11 | w3wp.exe | (0x1CB4) | 0x1F24 | SharePoint Foundation | Configuration | Alternate access mappings have not been configured. Users or services are accessing the site http://<<SERVERNAME>> with the URL http://localhost. This may cause incorrect links to be stored or returned to users. If this is expected, add the URL http://localhost as an AAM response URL. For more information, see: http://go.microsoft.com/fwlink/?LinkId=114854"/>
To fix this issue, all you need to do is to configure Alternate Access Mappings (AAM) by adding internal URLs “http://localhost” to the default zone as shown in screenshot below:
3 comments:
to people who had hard time finding Alternate Access Mappings (AAM) page like me:
- Central Administrator -> Application Management -> Web Applications -> Configure AAM -> Add Internal URLS
Thanks alot..
THanks Alot
Post a Comment