locked
Migrated Sites from SharePoint 2010 to SharePoint 2013 Displaying HTTP 404 RRS feed

  • Question

  • Hi All,

    In my environment i have 5 servers (3 application & 2 WFE servers) and i have mounted the DB's from SharePoint 2010 to SharePoint 2013. After doing this activity i am not able to open the sites, it is displaying http 404 error. Can anyone tell me how to access the sites without creating the hostheader. Also do i need to add any record in hostfile ? Please guide me.

    Error Log:
    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"/>


    Thanks & Regards,
    Sankar
    Tuesday, November 24, 2015 7:44 AM

Answers

  • For testing i'm going to assume you're doing everything from WFE1.

    You will need to create a web application to match your web applications in the 2010 environment. This should be in addition to the central admin web application, which should not be modified.

    Once you have created your new web application, which we'll assume is on nearly the same URL as one of the old sites (eg. http://portal-new.domain.com) you can attach the databases to that web application. Do this one at a time, starting with the database that holds the root site collection.

    Once the database is attached you should check in central admin to see that you have a new site collection associated with that web application

    Then you should configure the hosts file on WFE1 to point to WFE2's IP address for the web application (eg http://portal-new.domain.com). This will let you confirm that the web application works and the sites work. These should look almost identical to the old ones.

    AAMs are not interesting/useful at this point. Ignore them.

    • Proposed as answer by Sara Fan Tuesday, December 8, 2015 2:20 AM
    • Marked as answer by Sara Fan Wednesday, December 9, 2015 7:31 AM
    Tuesday, November 24, 2015 11:04 AM
  • Upgrade on-premise sites from SP2010 to SP2013: problems and solutions

    You may also take help from this Step by Step guide to Migrate from SharePoint 2010 to SharePoint 2013
    http://www.lepide.com/blog/step-by-step-guide-to-migrate-from-sharepoint-2010-to-sharepoint-2013/

    Going to a Site Collection homepage gives a 404
    http://sharepoint.stackexchange.com/questions/26568/going-to-a-site-collection-homepage-gives-a-404

    Sharepoint 2013 - 404 Not Found while accessing site collection

    Troublshooting a 404 error related to moving a content database
    http://sharepointjack.com/2014/troublshooting-a-404-error-related-to-moving-a-content-database/

    Hope this helps!


    Easily migrate anything from Office 365, File Servers, Public Folders, OneDrive and SharePoint to SharePoint Online easily with Lepide SharePoint Migrator.

    • Proposed as answer by Sara Fan Tuesday, December 8, 2015 2:20 AM
    • Marked as answer by Sara Fan Wednesday, December 9, 2015 7:31 AM
    Wednesday, November 25, 2015 6:40 AM

All replies

  • Are you using http://servername or http://portal.domain.com on your old 2010 farm? Are you planning on using the same URL or a new URL for 2013?

    This guide is pretty good for the overall 2010 -> 2013 upgrade process, although it doesn't go into the details on lots of it. How far through this process are you?

    http://en.share-gate.com/blog/step-by-step-upgrade-sharepoint-2010-database-to-sharepoint-2013

    Tuesday, November 24, 2015 10:09 AM
  • Hi Alex,

    Thanks for your reply.
    I am using different URL(Ex: http://portal.domain.com) for production environment. This is my production test cycle and i have created a web application and mounted the db's. Here the web application url is central admin application server name. PFB for more details.
    AppServer1 - Central Admin
    AppServer2 - SharePoint Services
    AppServer3 - SharePoint Services
    WFE1 - For web applications (Not configured NLB and host headers)
    WFE2 - For web applications (Not configured NLB and host headers)

    Web application URL: http://AppServer1 (All the DB's are mounted to this web application and the sites are not opening in any of the servers)

    Logs are showing Alternate access mappings have not been configured.

    Please guide me on this issue.

    Thanks & Regards,

    Sankar

    Tuesday, November 24, 2015 10:41 AM
  • For testing i'm going to assume you're doing everything from WFE1.

    You will need to create a web application to match your web applications in the 2010 environment. This should be in addition to the central admin web application, which should not be modified.

    Once you have created your new web application, which we'll assume is on nearly the same URL as one of the old sites (eg. http://portal-new.domain.com) you can attach the databases to that web application. Do this one at a time, starting with the database that holds the root site collection.

    Once the database is attached you should check in central admin to see that you have a new site collection associated with that web application

    Then you should configure the hosts file on WFE1 to point to WFE2's IP address for the web application (eg http://portal-new.domain.com). This will let you confirm that the web application works and the sites work. These should look almost identical to the old ones.

    AAMs are not interesting/useful at this point. Ignore them.

    • Proposed as answer by Sara Fan Tuesday, December 8, 2015 2:20 AM
    • Marked as answer by Sara Fan Wednesday, December 9, 2015 7:31 AM
    Tuesday, November 24, 2015 11:04 AM
  • Upgrade on-premise sites from SP2010 to SP2013: problems and solutions

    You may also take help from this Step by Step guide to Migrate from SharePoint 2010 to SharePoint 2013
    http://www.lepide.com/blog/step-by-step-guide-to-migrate-from-sharepoint-2010-to-sharepoint-2013/

    Going to a Site Collection homepage gives a 404
    http://sharepoint.stackexchange.com/questions/26568/going-to-a-site-collection-homepage-gives-a-404

    Sharepoint 2013 - 404 Not Found while accessing site collection

    Troublshooting a 404 error related to moving a content database
    http://sharepointjack.com/2014/troublshooting-a-404-error-related-to-moving-a-content-database/

    Hope this helps!


    Easily migrate anything from Office 365, File Servers, Public Folders, OneDrive and SharePoint to SharePoint Online easily with Lepide SharePoint Migrator.

    • Proposed as answer by Sara Fan Tuesday, December 8, 2015 2:20 AM
    • Marked as answer by Sara Fan Wednesday, December 9, 2015 7:31 AM
    Wednesday, November 25, 2015 6:40 AM