Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 917
  • Last Modified:

SharePoint Migration from one SBS server to another failed

Problem: Unable to migrate SharePoint from one SBS 2003 server to another
Original Server: SBS 2003 Standard.  Server name: abcserver01.  AD: abccompany.local
New Server: SBS 2003 Standard. Server name: abcserver01. AD: abccompany.local
Used the osql commands to detach the following from the old server:
"      STS_Config.mdf
"      STS_Config_log.ldf
"      STS_abcserver01_1.mdf
"      STS_abcserver01_1_log.ldf
These files were copied from old server to new.
Used the osql command to detach the default mdf & ldf files on the new server.   Used the osql command to attach the old mdf & ldf files.

The new SBS server was restarted.  When opening http://companyweb on the new SBS, we get the following error message:

The Web site that is referenced here is not in the configuration database.

What should I do next?

Thanks!



0
pegarris
Asked:
pegarris
  • 6
  • 6
1 Solution
 
Robbie_LeggettCommented:
Go into the central admin pages and make sure the correct config db is set. You may need to specify it again.

:-)
0
 
pegarrisAuthor Commented:
Robbie,

Are you referring to the configdb.aspx file under c:\program files\common files\microsoft shared\web server extensions\60\template\admin\1033?  Do I need to copy that file from the old SBS to the new SBS?

I also checked under http:\\127.0.0.1:8081\configdb.aspx.
Database Server: SERVER1\SharePoint
SQL Server database name: STS_Config

Thanks!
0
 
Robbie_LeggettCommented:
No. You need to go to SharePoint Central Admin, then server configuration. Choose set configuration database server and enter the new details in the boxes. Tick connect to existing configuration database. That should reconnect you to the config database on the new server.

Then, from within central admin, server configuration, choose set default content database server. Enter the new information in the box.

Then, from within central admin, choose configure virtual server settings. On the next page, choose your virtual server. On the next page, under virtual server management, select manage content databases. Select add a content database if it's not already listed, and add the content database you migrated. You should then be good to go.

:-)
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
pegarrisAuthor Commented:
SharePoint Central Admin, then server configuration. Choose set configuration database server and enter the new details in the boxes.

Dataserver: SERVER1\SharePoint
SQL Server database name: STS_Config

 Tick connect to existing configuration database. That should reconnect you to the config database on the new server.

Checked the box Connect to existing configuration
then click on OK

Then, from within central admin, server configuration, choose set default content database server. Enter the new information in the box.

Database server: server1\SharePoint
then click on OK

Then, from within central admin, choose configure virtual server settings. On the next page, choose your virtual server.

companyweb

On the next page, under virtual server management, select manage content databases. Select add a content database (There is no existing entry) if it's not already listed, and add the content database you migrated.

Database Information  - Specify database server settings
      Database server: server1\sharepoint
      Database name: STS_SERVER1_1
Database Capacity Settings
      Number of sites before a warning event is generated: 9
      Maximum number of sites that can be created in this database: 10
Click on OK

Windows SharePoint Services Error
The database schema is too old to perform this operation in this SharePoint cluster.  Please upgrade the database and try again.

What went wrong  here?
0
 
Robbie_LeggettCommented:
0
 
pegarrisAuthor Commented:
Installed the patch.  Now when I tried to save the settings in SharePoint Central Admin by clicking OK.  The page the sits there.
0
 
pegarrisAuthor Commented:
Fixed that.  Now I get "A database with given name already exists on the specified database server."
0
 
Robbie_LeggettCommented:
If a file exists in the SQL db directory with the same name this is a problem, even if SQL doesn't have it attached.
0
 
pegarrisAuthor Commented:
Do I just delete "STS_Server1_1.mdf" from c:\program files\microsoft SQL Server\MSSQL$Sharepoint\data?
0
 
Robbie_LeggettCommented:
Move it to another location rather than deleting it.

:-)
0
 
pegarrisAuthor Commented:
I moved it to another location, restarted the server and still got the same error.
0
 
Robbie_LeggettCommented:
Try to get WSS to "refresh" itself by pointing the content database server to a new machine, except provide the existing data tier name.  Then during its switch to the "new" data tier, it may refresh its list of databases and you'll be able to see the STS_Config database.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now