Hello Everything was going so well. I used the following Technet articles and still encountered some issues. http://technet.microsoft.com/en-us/library/cc288664%28office.12%29.aspx http://technet.microsoft.com/en-us/library/cc512723.aspx http://technet.microsoft.com/en-us/library/cc288072%28office.12%29.aspx Scenario: single server farm Source: Win2003 SP2/SQL 2005/WSS3 SP2/Configuration and Content DBs in SQL/one application/site/site collection (url is server name: http://server3) Destination: Win2008 R2 SP1/SQL 2008 R2/WSS3 SP2/(want to change url to http://sharepoint.mydomain.com) Server and SQL hosts 3rd party application that has Sharepoint integration Goal: simply migrate existing site to new server Result: Destination server is up and running with clean SQL instance. 3rd part application and DB running fine. SQL connections to source server fine. WSS 3 installed using default locations with no errors. Configuration wizard ran with no errors. WSS Administrative site fully functional and configured same as source. default database is SQL 2008 instance. Web application created with desired URL. No site collection created. Using same AD accounts for service accounts, SQL, DB and local directory security 1) Copied the the Sharepoint MDF and LDF files to destination. Attached using our Coastal_Content DB. When connecting to application to content db - alert that database requires ugrade- to use stsadm utility to attach. Stop SP services, run the addcontentdb command and get "Upgrade completed with errors." the upgrade log is clean until: [SPManager] [ERROR] [9/20/2011 11:45:08 AM]: Upgrade [SPContentDatabase Name=Coastal_Content Parent=SPDatabaseServiceInstance] failed. [SPManager] [ERROR] [9/20/2011 11:45:08 AM]: There is already an object named 'Docs' in the database. [SPManager] [ERROR] [9/20/2011 11:45:08 AM]: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) 2) Backed up the source SP site and restored to destination server no errors DB is correct size - but site will not come up = 404 error. Checked permissions and authorizations and cannot find anything out of whack 3) In SQL 2008 imported source DB into destination DB using the Enable identity insert option. Encounter several alerts and cautions but import succeeds. again site does not come up - authentication fails 4) changed Alternate Access Mappings - When I connect using Http://localhost wants public URL, when using public URL wants Local host. So first things first = almost all of the information i can find online points to larger issues. mine appears to be something smaller or something I missed. it has to be something simple, but my brain is fried.

Hello Swinfos, Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support. Thanks, Wayne Fan TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com.

Hello, So, what I understand is you did 2 changes. 1) Changed SharePoint Site URL from http://server3 to http://sharepoint.mydomain.com 2) Moved all SharePoint databases to new SQL Server 3) Moved SharePoint Servers to new servers with 2008 R2 OS I have a few questions / suggestions - 1) Did you move ALL SharePoint databases including the configuration database or did you create a new config db (asking as you report Central Admin is working) 2) Have you created SQL aliases on ALL SharePoint Servers. SQL Alias should be created with old SQL Server instance name and should be pointing to new SQL Server and hence make sure all the DB connection from SharePoint Servers are reaching to new SQL (and not old SQL) 3) "database requires upgrade" message will not show up unless a SharePoint binary update was installed earlier and PSCONFIG was pending. That was detected and hence you had to attach using stsadm -o attach 4) What is the main problem you are facing now? 404 error?Alternate access mappings? 5) 404 error basically tells you that the path or directory of the site is not reachable. Can you turn call stack to true and custom errors off on the web.config of the web app the site resides. Doing that we would be able to see more descriptive message 6) Can you run the sharepoint configuration wizard (PSCONFIG) on all SharePoint Servers again and test 7) For a request to reach to SharePoint Server, you need to ensure IP address for sharepoint.mydomain.com is pointing to SharePoint Server/Load Balancer so that request reaches to the server; ensure a correct host header is present so that request is routed to correct web application in IIS and correct Alternate Access Mapping so SharePoint knows that it needs to respond when a request comes at http://sharepoint.mydomain.com 8) If you have doubts about AAM, please provide the current configuration of AAMPlease remember to click 'Mark as Answer' on the post that helps you or click 'Unmark as Answer' if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Nishant Shah Microsoft Online Community Support