Answered by:
Subsite getting 404 error

Question
-
My SP2010 main site is up and running. I have created new web application and site collection for BLOB storage. I am trying to link this BLOB subsite from main site but getting 404 error http://<machinename> ----- working or http://AAM ----- working or http://AAM/sites/BLOBStore ----- working http://<machinename>/sites/BLOBStore ----- NOT working getting 404 errorFriday, March 4, 2011 8:44 PM
Answers
-
Found solution after finding this warning in log
Alternate access mappings have not been configured. Users or services are accessing the site http://AAM with the URL http://<machinename>. This may cause incorrect links to be stored or returned to users. If this is expected, add the URL http://<machinename> as an AAM response URL. For more information, see: http://go.microsoft.com/fwlink/?LinkId=114854"/>
So edited Alternate access mappings for http://AAM
1. Set <machinename> as default
2. Set http://AAM as Intranet
Now it is working fine.... :)
- Marked as answer by YECMOSS Monday, March 7, 2011 7:45 PM
Monday, March 7, 2011 7:45 PM
All replies
-
Did you put your machine name (and port number) in one of the AAM spots (like default or extranet)?
-SharePointNinjaFriday, March 4, 2011 9:05 PM -
Yes I tried that option before http://<machinename>:80/sites/BLOBStore ----- NOT working getting same 404 error... :(Monday, March 7, 2011 5:50 PM
-
Hi Moss_hr,
have you tried http://<Machinename>/sites/BlobStore/_layouts/viewlsts.aspx or http://<Machinename>/sites/BlobStore/_layouts/settings.aspx if a new site collection is created those sites should be accessible anyway.
It might can happen that you don't have a welcome page set or the redirection to the default.aspx doesn't work.
Hope this suggestions work.
Kind regards
Stefan
http://www.n8d.at/blog
twitter: n8design
Microsoft Community Contributor 2011
MCTS - SharePoint / WSS Configuration and DevelopmentMonday, March 7, 2011 7:40 PM -
Found solution after finding this warning in log
Alternate access mappings have not been configured. Users or services are accessing the site http://AAM with the URL http://<machinename>. This may cause incorrect links to be stored or returned to users. If this is expected, add the URL http://<machinename> as an AAM response URL. For more information, see: http://go.microsoft.com/fwlink/?LinkId=114854"/>
So edited Alternate access mappings for http://AAM
1. Set <machinename> as default
2. Set http://AAM as Intranet
Now it is working fine.... :)
- Marked as answer by YECMOSS Monday, March 7, 2011 7:45 PM
Monday, March 7, 2011 7:45 PM