none
Move WSS 3.0 RTM to WSS 3.0 sp2 RRS feed

  • Question

  • Hi

    I need to move an old WSS 3.0 RTM (12.0.0.4518) installation to another server preferable WSS 3.0 SP2 as a start
    It's a small internal 6 users WSS site

    I have tried backup/restore to no avail:
    Due to error "Access to table dbo.EventCache is blocked because the signature is not valid"
    Full log added below

    Is it not possible to move from SQL Server 2005 to Windows Internal Database?
    New test site is 12.0.0.6690

    Thanks in advance  /Peter

    [9/25/2016 11:27:14 AM]: Verbose: Using directory: <local_path>\spbr0000\.
    [9/25/2016 11:27:14 AM]: Verbose: Starting OnPreRestore event.
    [9/25/2016 11:27:14 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:27:15 AM]: Verbose: Adding Windows SharePoint Services Web Application to Restore list.
    [9/25/2016 11:27:15 AM]: Verbose: Adding <remote_site> to Restore list.
    [9/25/2016 11:27:15 AM]: Verbose: Adding WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227 to Restore list.
    [9/25/2016 11:27:15 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services-webprogram.
    [9/25/2016 11:27:15 AM]: Verbose: Found 0 item(s).
    [9/25/2016 11:27:15 AM]: Error: Backup component Farm\Windows SharePoint Services-webprogram could not be found.
    [9/25/2016 11:27:21 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services Web Application.
    [9/25/2016 11:27:21 AM]: Verbose: Found 1 item(s).
    [9/25/2016 11:28:29 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services Web Application.
    [9/25/2016 11:28:29 AM]: Verbose: Found 1 item(s).
    [9/25/2016 11:28:31 AM]: Verbose: Using directory: <local_path>\spbr0000\.
    [9/25/2016 11:28:31 AM]: Verbose: Starting OnPreRestore event.
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Initializing SPPersistedObject State
    [9/25/2016 11:28:32 AM]: Verbose: Adding Windows SharePoint Services Web Application to Restore list.
    [9/25/2016 11:28:32 AM]: Verbose: Adding <remote_site> to Restore list.
    [9/25/2016 11:28:32 AM]: Verbose: Adding WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227 to Restore list.
    [9/25/2016 11:28:32 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services-webprogram.
    [9/25/2016 11:28:32 AM]: Verbose: Found 0 item(s).
    [9/25/2016 11:28:32 AM]: Error: Backup component Farm\Windows SharePoint Services-webprogram could not be found.
    [9/25/2016 11:28:32 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services Web Application.
    [9/25/2016 11:28:32 AM]: Verbose: Found 1 item(s).
    [9/26/2016 10:58:39 AM]: Verbose: Using directory: <local_path>\spbr0000\.
    [9/26/2016 10:58:39 AM]: Verbose: Starting OnPreRestore event.
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:58:39 AM]: Verbose: Adding Windows SharePoint Services Web Application to Restore list.
    [9/26/2016 10:58:39 AM]: Verbose: Adding <remote_site> to Restore list.
    [9/26/2016 10:58:39 AM]: Verbose: Adding WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227 to Restore list.
    [9/26/2016 10:58:39 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services-webprogram.
    [9/26/2016 10:58:39 AM]: Verbose: Found 0 item(s).
    [9/26/2016 10:58:39 AM]: Error: Backup component Farm\Windows SharePoint Services-webprogram could not be found.
    [9/26/2016 10:58:42 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services Web Application.
    [9/26/2016 10:58:42 AM]: Verbose: Found 1 item(s).
    [9/26/2016 10:59:26 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services Web Application.
    [9/26/2016 10:59:26 AM]: Verbose: Found 1 item(s).
    [9/26/2016 10:59:31 AM]: Verbose: Using directory: <local_path>\spbr0000\.
    [9/26/2016 10:59:31 AM]: Verbose: Starting OnPreRestore event.
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Adding Windows SharePoint Services Web Application to Restore list.
    [9/26/2016 10:59:31 AM]: Verbose: Adding <remote_site> to Restore list.
    [9/26/2016 10:59:31 AM]: Verbose: Adding WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227 to Restore list.
    [9/26/2016 10:59:31 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services-webprogram.
    [9/26/2016 10:59:31 AM]: Verbose: Found 0 item(s).
    [9/26/2016 10:59:31 AM]: Error: Backup component Farm\Windows SharePoint Services-webprogram could not be found.
    [9/26/2016 10:59:31 AM]: Verbose: Using directory: <local_path>\spbr0000\.
    [9/26/2016 10:59:31 AM]: Verbose: Starting OnPreRestore event.
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Initializing SPPersistedObject State
    [9/26/2016 10:59:31 AM]: Verbose: Adding Windows SharePoint Services Web Application to Restore list.
    [9/26/2016 10:59:31 AM]: Verbose: Adding <remote_site> to Restore list.
    [9/26/2016 10:59:31 AM]: Verbose: Adding WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227 to Restore list.
    [9/26/2016 10:59:31 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services-webprogram.
    [9/26/2016 10:59:31 AM]: Verbose: Found 0 item(s).
    [9/26/2016 10:59:31 AM]: Error: Backup component Farm\Windows SharePoint Services-webprogram could not be found.
    [9/26/2016 10:59:31 AM]: Verbose: Searching for item: Farm\Windows SharePoint Services Web Application.
    [9/26/2016 10:59:31 AM]: Verbose: Found 1 item(s).
    [9/26/2016 10:59:32 AM]: Verbose: The backup/restore process included the following objects:
    [9/26/2016 10:59:32 AM]:     *Farm\
            *[SharePoint_Config]\
            Windows SharePoint Services Web Application\
                <remote_site>\
                    WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227\
            *[WSS_Administration]\
                *[Web Application]\
                    *[SharePoint_AdminContent_5372f09a-5b1e-4227-a6cf-59455f7b07fb]\
            *Windows SharePoint Services-søgning\
                *[Search instance]\
                    *[WSS_Search_bzdkkol01_25573003aa204246b4e7b51b96c03421]\
    
    [9/26/2016 10:59:32 AM]: Verbose: Adding Windows SharePoint Services Web Application to Restore list.
    [9/26/2016 10:59:32 AM]: Verbose: Adding <remote_site> to Restore list.
    [9/26/2016 10:59:32 AM]: Verbose: Adding WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227 to Restore list.
    [9/26/2016 10:59:42 AM]: Progress: Starting Restore.
    [9/26/2016 10:59:42 AM]: Start Time: 9/26/2016 10:59:42 AM.
    [9/26/2016 10:59:42 AM]: Verbose: Requested by <ID>-F2FCGTNFDP\Administrator.
    [9/26/2016 10:59:42 AM]: Verbose: Backup/Restore Settings:
    	Restore
    	Backup Method: Full
    	Top Component: Farm\Windows SharePoint Services Web Application
    	Directory: <local_path>
    	Progress updated: 5
    [9/26/2016 10:59:42 AM]: 	Restore Method: New
    	Backup ID: cf3777c6-4bb2-4cd9-8b20-74fb5050c2d9
    	Preserve content database change log: False
    
    [9/26/2016 10:59:42 AM]: Verbose: Starting OnRestore event.
    [9/26/2016 10:59:42 AM]: Verbose: Starting object: Windows SharePoint Services Web Application.
    [9/26/2016 10:59:42 AM]: Progress: [Windows SharePoint Services Web Application] 50 percent complete.
    [9/26/2016 10:59:42 AM]: Verbose: Current object: Test2 (previous name: <remote_site>).
    [9/26/2016 10:59:42 AM]: Verbose: [<remote_site>] Trying to connect to Web application http://<ID>-f2fcgtnfdp:810/.
    [9/26/2016 10:59:42 AM]: Verbose: [Test2] Creating a new Web application.
    [9/26/2016 10:59:53 AM]: Verbose: [Test2] Provisioning a new Web application.
    [9/26/2016 11:00:00 AM]: Progress: [Test2] 50 percent complete.
    [9/26/2016 11:00:00 AM]: Verbose: Starting object: WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227.
    [9/26/2016 11:00:00 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL Server Connection String: Data Source=<ID>-F2FCGTNFDP\Microsoft##SSEE;Initial Catalog=WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227;Integrated Security=True.
    [9/26/2016 11:00:00 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL command started at: 9/26/2016 11:00:00 AM. This command may take a while to complete and without notification.
    [9/26/2016 11:00:00 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL Server Command: 
    IF EXISTS ( SELECT * FROM master..sysdatabases WHERE has_dbaccess(name)=1 AND name=@db_name )
    BEGIN
        SELECT 1 as ErrorCode
    END
    ELSE
    BEGIN RESTORE DATABASE [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] FROM DISK=@db_location WITH STATS=5, FILE=1, MOVE @db_OldName TO @db_NewFile, MOVE @db_OldLogName TO @db_NewLogFile, NOREWIND, NOUNLOAD, RECOVERY
    END
    
    	@db_location=<local_path>\spbr0000\0000000C.bak, @db_OldName=WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227, @db_NewFile=C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227.mdf, @db_OldLogName=WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227_log, @db_NewLogFile=C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227_log.ldf, @db_name=WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227
    [9/26/2016 11:00:00 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL command timeout is set to 16.67 hours.
    [9/26/2016 11:01:20 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 5 percent complete.
    [9/26/2016 11:02:40 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 10 percent complete.
    [9/26/2016 11:03:41 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 15 percent complete.
    [9/26/2016 11:04:08 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 20 percent complete.
    [9/26/2016 11:04:34 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 25 percent complete.
    [9/26/2016 11:05:54 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 30 percent complete.
    [9/26/2016 11:07:05 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 35 percent complete.
    [9/26/2016 11:08:13 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 40 percent complete.
    [9/26/2016 11:09:17 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 45 percent complete.
    [9/26/2016 11:10:44 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 50 percent complete.
    [9/26/2016 11:11:50 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 55 percent complete.
    [9/26/2016 11:12:06 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 60 percent complete.
    [9/26/2016 11:12:24 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 65 percent complete.
    [9/26/2016 11:12:44 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 70 percent complete.
    [9/26/2016 11:13:02 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 75 percent complete.
    [9/26/2016 11:13:15 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 80 percent complete.
    [9/26/2016 11:13:29 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 85 percent complete.
    [9/26/2016 11:13:42 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 90 percent complete.
    [9/26/2016 11:13:59 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 95 percent complete.
    [9/26/2016 11:14:12 AM]: Progress: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] 100 percent complete.
    [9/26/2016 11:14:12 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL Server Message: Processed 365264 pages for database 'WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227', file 'WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227' on file 1.
    [9/26/2016 11:14:12 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL Server Message: Processed 3 pages for database 'WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227', file 'WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227_log' on file 1.
    [9/26/2016 11:14:36 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL Server Message: RESTORE DATABASE successfully processed 365267 pages in 854.402 seconds (3.502 MB/sec).
    [9/26/2016 11:14:36 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL command completed at: 9/26/2016 11:14:36 AM.
    [9/26/2016 11:14:37 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] Verifying that the database restoration is complete.
    [9/26/2016 11:14:37 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL Server Command: USE [master]
                            SELECT status FROM master..sysdatabases WHERE name=@db_name
    	@db_name=WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227
    [9/26/2016 11:14:37 AM]: Debug: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] Database status is 65536.
    [9/26/2016 11:14:37 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] SQL Server Command: SELECT TOP 1 1 FROM [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227]..sysobjects
    [9/26/2016 11:14:37 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] Database restoration has been verified.
    [9/26/2016 11:14:37 AM]: Verbose: Starting OnPostRestore event.
    [9/26/2016 11:14:37 AM]: Verbose: Starting object: Windows SharePoint Services Web Application.
    [9/26/2016 11:14:37 AM]: Progress: [Windows SharePoint Services Web Application] 100 percent complete.
    [9/26/2016 11:14:37 AM]: Verbose: Current object: Test2 (previous name: <remote_site>).
    [9/26/2016 11:14:37 AM]: Progress: [Test2] 100 percent complete.
    [9/26/2016 11:14:37 AM]: Verbose: Starting object: WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227.
    [9/26/2016 11:14:37 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] Trying to attach to web application url: http://<ID>-f2fcgtnfdp:810/
    [9/26/2016 11:14:37 AM]: Verbose: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] Attaching database
    [9/26/2016 11:14:37 AM]: Warning: [WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227] Content database failed to be added to SharePoint, please try and detach the original database then re-attach this database.
    [9/26/2016 11:14:38 AM]: Error: Object WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227 failed in event OnPostRestore. For more information, see the error log located in the backup directory.
    	SqlException: Access to table dbo.EventCache is blocked because the signature is not valid.
    Access to table dbo.TimerLock is blocked because the signature is not valid.
    [9/26/2016 11:14:38 AM]: Debug:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command)
       at Microsoft.SharePoint.Administration.SPContentDatabase.FlushChangeLog(String strDatabaseServer, String strDatabaseName, String strDatabaseUsername, String strDatabasePassword)
       at Microsoft.SharePoint.Administration.SPContentDatabase.OnPostRestore(Object sender, SPRestoreInformation args)
    [9/26/2016 11:14:38 AM]: Verbose: Notifying third parties that the restore completed.
    [9/26/2016 11:14:38 AM]: Verbose: The IIS Web Site has been extended.  You may need to use iisreset.exe to restart IIS before your site becomes accessible.
    [9/26/2016 11:14:38 AM]: Finish Time: 9/26/2016 11:14:38 AM.
    [9/26/2016 11:14:38 AM]: Progress: Completed with errors and warnings, please refer to the log file for details.
    [9/26/2016 11:14:38 AM]: Verbose: The backup/restore process included the following objects:
    [9/26/2016 11:14:38 AM]:     *Farm\
            *[SharePoint_Config]\
            Windows SharePoint Services Web Application\
                Test2\
                    *WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227\
            *[WSS_Administration]\
                *[Web Application]\
                    *[SharePoint_AdminContent_5372f09a-5b1e-4227-a6cf-59455f7b07fb]\
            *Windows SharePoint Services-søgning\
                *[Search instance]\
                    *[WSS_Search_bzdkkol01_25573003aa204246b4e7b51b96c03421]\
    
    [9/26/2016 11:14:38 AM]: Completed with 1 warnings.
    [9/26/2016 11:14:38 AM]: Completed with 2 errors.
    [9/26/2016 11:14:41 AM]: Restore failed for Object WSS_Content_d6862c6764e74bf6aaf94d9ce3e85227 failed in event OnPostRestore. For more information, see the error log located in the backup directory.
    [9/26/2016 11:14:41 AM]: -------------------------------------------------


    Monday, September 26, 2016 9:36 AM

All replies

  • Hi Peter,

    You might be best served looking for a quick win here due to the age of the technology you're using.  Is your WSS RTM site still up and functional?  Or is the content databases accesible?

    My thinking is that an express product, such as Metalogix Content migrator might be worth looking it.  It'll save the issues of infrastructure and lets you move your content directly.


    Steven Andrews
    SharePoint Business Analyst: LiveNation Entertainment
    Blog: baron72.wordpress.com
    Twitter: Follow @backpackerd00d
    My Wiki Articles: CodePlex Corner Series
    Please remember to mark your question as "answered" if this solves (or helps) your problem.

    Monday, September 26, 2016 9:53 AM
    Answerer
  • Metalogix Content Migrator does not mention WSS 3.0 would it be equivalent to WS 2003?
    The old site is up and running

    Thanks  /Peter

    Monday, September 26, 2016 10:56 AM
  • WSS 3.0 is the free part of SharePoint 2003, SPS was built on top of it so for your purposes it should be fine.  I've used it twice for SharePoint 2003 migrations.  It needs some extra bits installed on the server as it doesn't have a feature model that later versions of SP use, but that aside, it should be pretty simple.

    Steven Andrews
    SharePoint Business Analyst: LiveNation Entertainment
    Blog: baron72.wordpress.com
    Twitter: Follow @backpackerd00d
    My Wiki Articles: CodePlex Corner Series
    Please remember to mark your question as "answered" if this solves (or helps) your problem.

    Monday, September 26, 2016 11:39 AM
    Answerer
  • Please have a look at this Technet article that you can follow to move your content and configuration databases to a new server. Make sure you follow the section "Move all databases to a different database server".


    https://support.microsoft.com/en-us/kb/894164


    Here is a list of Content Migration Tools for SharePoint:
    http://www.topsharepoint.com/content-migration-tools-for-sharepoint

    Hope this helps!


    A comprehensive solution to migrate to-and-from SharePoint and Office 365 along with File Servers, Exchange/Office 365 Public Folders, Google Drive and OneDrive Business to SharePoint Online/On-premise migration.

    Tuesday, September 27, 2016 7:00 AM
  • Thanks

    I have a WSS 3.0 RTM installation, the suggested article is for SharePoint Portal Server 2003 
    I have shortly scanned the article, there's a lot of differences between the products

    Tuesday, September 27, 2016 9:47 AM