This is killing me! We are running in to several issues trying to restore our SharePoint site. It does not seem to matter what route we take there are errors to be had. We have tried to create a totally new SP site and then copy everything over, tried to totally rebuild and restore, evendeleted the entire site and restore and still get these same errors.Sorry for the wall of text, but we are desperate.Suggestions are welcome! Errors: Default Web Site In process 11/6/2009 8:52 AM Object Default Web Site failed in event OnRestore. For more information, see the error log located in the backup directory. ArgumentException: The IIS Web Site you have selected is in use by SharePoint. You must select another port or hostname. WSS_Content_dc1e6a846492448c8accee54288550fe In process 11/6/2009 8:52 AM Object WSS_Content_dc1e6a846492448c8accee54288550fe failed in event OnRestore. For more information, see the error log located in the backup directory. SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) SharePoint - 80 In process 11/6/2009 8:52 AM Object SharePoint - 80 failed in event OnRestore. For more information, see the error log located in the backup directory. ArgumentException: The IIS Web Site you have selected is in use by SharePoint. You must select another port or hostname. WSS_Content In process 11/6/2009 8:52 AM Object WSS_Content failed in event OnRestore. For more information, see the error log located in the backup directory. SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) WSS_Administration In process 11/6/2009 8:52 AM Web Application 11/6/2009 8:52 AM SharePoint_AdminContent_f270d20a-6503-44a3-9f8c-12706cc93ef7 11/6/2009 8:52 AM SharedServices1 In process 11/6/2009 8:52 AM Object SharedServices1 failed in event OnRestore. For more information, see the error log located in the backup directory. SPDuplicateObjectException: An object of the type Microsoft.Office.Server.Administration.SharedResourceProvider named "SharedServices1" already exists under the parent Microsoft.SharePoint.Administration.SPFarm named "SharePoint_Config_5351b8d3-ceb6-4d45-9b54-c05caa999896". Rename your object or delete the existing object. SharePoint - 16533 In process 11/6/2009 8:52 AM Object SharePoint - 16533 failed in event OnRestore. For more information, see the error log located in the backup directory. InvalidOperationException: This operation uses the SharePoint Administration service (spadmin), which could not be contacted. If the service is stopped or disabled, start it and try the operation again. SharedServicesContent_b0551085-ce24-4e95-9e6f-2bf98521a342 In process 11/6/2009 8:52 AM Object SharedServicesContent_b0551085-ce24-4e95-9e6f-2bf98521a342 failed in event OnRestore. For more information, see the error log located in the backup directory. SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) SharedServices1_DB_a7d608c0-ef8d-4d46-8e18-533c6af098be In process 11/6/2009 8:52 AM Object SharedServices1_DB_a7d608c0-ef8d-4d46-8e18-533c6af098be failed in event OnRestore. For more information, see the error log located in the backup directory. SqlException: Directory lookup for the file "c:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\12\Data\MSSQL.1\MSSQL\DATA\SharedServices1_DB_a7d608c0-ef8d-4d46-8e18-533c6af098be.mdf" failed with the operating system error 3(The system cannot find the path specified.). File 'SharedServices1_DB_a7d608c0-ef8d-4d46-8e18-533c6af098be' cannot be restored to 'c:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\12\Data\MSSQL.1\MSSQL\DATA\SharedServices1_DB_a7d608c0-ef8d-4d46-8e18-533c6af098be.mdf'. Use WITH MOVE to identify a valid location for the file. Directory lookup for the file "c:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\12\Data\MSSQL.1\MSSQL\DATA\SharedServices1_DB_a7d608c0-ef8d-4d46-8e18-533c6af098be_log.LDF" failed with the operating system error 3(The system cannot find the path specified.). File 'SharedServices1_DB_a7d608c0-ef8d-4d46-8e18-533c6af098be_log' cannot be restored to 'c:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\12\Data\MSSQL.1\MSSQL\DATA\SharedServices1_DB_a7d608c0-ef8d-4d46-8e18-533c6af098be_log.LDF'. Use WITH MOVE to identify a valid location for the file. Problems were identified while planning for the RESTORE statement. Previous messages provide details. RESTORE DATABASE is terminating abnormally. UserProfileApplication In process 11/6/2009 8:53 AM SessionStateSharedApplication In process 11/6/2009 8:52 AM Shared Search Index In process 11/6/2009 8:53 AM SharedServices1_Search_DB_5da02afa-9034-4a2b-aeb9-c7b947717ff6 In process 11/6/2009 8:52 AM Global Search Settings In process 11/6/2009 8:53 AM Windows SharePoint Services Help Search In process 11/6/2009 8:53 AM Search instance In process 11/6/2009 8:53 AM WSS_Search_SERVERNAME_101daf388bfa4f2880687f5229dd0ef2 In process 11/6/2009 8:52 AM

Hi, I am sorry for your situation, but let us start a new trial I suppose your are working on the same SQL DB server using the same SharePoint Servers Create Web App on new Server Central Admin->Application Management->Create or extend Web App->Create New Web App. Associate the old DB with the new Web App Central Admin->Application Management-> SharePoint Web Application Management->Content Databases-> Remove Content Database from your new web app. Now use STSADM to add the old DB to this new web app c:\program files\common files\microsoft shared\web server extentions\12\bin on new server is where you can find the STSADM. run this command from there. stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver Run ISSRESET from command promptBest Regards, Ammar MCT

Hi, From the following error, this is a known issue with SharePoint in that it isn't able to create the host header values in IIS during the restore process. In the event there are multiple host header web apps on the same port the first one will restore the subsequent web apps will fail. Object Default Web Site failed in event OnRestore. For more information, see the error log located in the backup directory. ArgumentException: The IIS Web Site you have selected is in use by SharePoint. You must select another port or hostname. From the following error, it seems that the connection between SQL and SharePoint server has problem. You need to double check the connection. For example, permission, firewall. Object SharedServicesContent_b0551085-ce24-4e95-9e6f-2bf98521a342 failed in event OnRestore. For more information, see the error log located in the backup directory. SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) For both of the errors above, you can try the following suggestions: First, create the Web application that has the host header binding. Then restore the content database only. Finally, attach the content database to the Web application by using the Stsadm addcontentdb operation. For more information, see Addcontentdb: Stsadm operation (Office SharePoint Server). For more information about A host header associated with a Web application is not restored correctly issue, please refer to the following article: Troubleshooting backup and recovery (Office SharePoint Server 2007) http://technet.microsoft.com/en-us/library/cc263025.aspx Hope this helps. Rock WangRock Wang MSFT

I followed the steps as you sais to create a new web application and attach the DB with stsadm cmd, but when I am trying to login to the web application eg: http://dmz01:8080/default.aspx it asks for login, after login in with administrator it gives me an error Go back to site Error An unexpected error has occurred. Troubleshoot issues with Windows SharePoint Services. So how can I access the default.aspx for the application.