How to move SharePoint sites.

How to move SharePoint Sites from Windows Server 2003 Virtual Machine to Windows Server 2008 Virtual Machine.
LVL 5
ncomperAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

chops_ukCommented:
I've done it with backup and restore, but had to tweak the versions of sharepoint on the different machines to get it working.
this may help: http://support.microsoft.com/kb/278061 
0
chops_ukCommented:
STSADM has worked before in a similar situation:
http://blog.henryong.com/2007/07/12/moving-sharepoint-sites-using-stsadm/ 
0
ncomperAuthor Commented:
Hi Chops uk,

I got the WSS3.0 installed sucessfully on the Windows 2008 server Virtual Machine. And have got a new sharepoint site created. I tried restoring the backup of the sharepoint site to the new sharepoint site. This got failed.

Next I tried with osql utility to change the DB.

I tried to detach the new sharepoint site DB and attach the existing DB to the new sharepoint site.

The machine name is for eg: MSWSS01

On executing the below command:

osql -E -S %computername%\MICROSOFT##SSEE

am getting the below error

[SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance
Specified [xFFFFFFFF].
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused by
the fact that under the default settings SQL Server does not allow remote
connections.

The above error indicates that the instance does not exist.

Here when I look for sql instances installed on the machine on executing the command

osql -L

it lists the instance as:

<XYZ>\MICROSOFT##SSEE


The <XYZ> is the name of the domain to which the machine belongs to.

But here the computer name (for eg: MSWSS01) differs from the above listed instance <XYZ>.

Any ideas/thoughts/solutions please.

Thanks
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

chops_ukCommented:
thanks ncomper.. do you have the embedded edition (i.e. ##ssee)?
I've had problems before with sql express, but I think that just required prefixing the instance MSSQLEXPRESS if I recall correctly.

Also, your osql command shows the variable %computername% - are you using this or explicitly specifying MSQSS01?

0
ncomperAuthor Commented:
Hi chops uk,

Thanks...

I tried both, the one that comes along with WSS 3.0 and also have tried SQL Express Edition.

OSQL utility is not recognized with the version of SQL that comes embedded with WSS 3.0

So have tried installing SQL Express Edition

With OSQL I tried using the variable like "%computername%\MICROSOFT##SSEE" initially, It showed the below error:

[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL
Server [1326].
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused by
the fact that under the default settings SQL Server does not allow remote
connections.

Also have tried manually mentioning the machine name like "MSWSS01\MICROSOFT##SSEE".

[SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance
Specified [xFFFFFFFF].
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused by
the fact that under the default settings SQL Server does not allow remote
connections.

from the above errors, it indicates that the remote connections are blocked. I tried changing the configuration under SQL Server Surface area configuration. But the updated settings doesn't take effect. It remains the same default setting "Local connections only".


Thanks
0
ncomperAuthor Commented:
Hi Chops uk,

I tried export and import of the SharePoint site using STSADM tool, from the comment you have given earlier:

"STSADM has worked before in a similar situation:
http://blog.henryong.com/2007/07/12/moving-sharepoint-sites-using-stsadm/ "


The steps I followed:
1] On the new server, got the WSS 3.0 installed.
2] And have created one new SharePoint site.
3] Got the exported files from the old server.
4] And tried importing the files on the new server. (see below the result of executing the command)

------------------------------------ -------------------------------------- ------------------------------------
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>stsa
dm -o import -url http://MSWSS01:40421/ -filename c:\angelbkp\angelbkp.cmp -inc
ludeusersecurity

Start Time: 3/31/2010 8:33:43 PM.
Progress: Initializing Import.
FatalError: The specified user SBSPMS04\Administrator could not be found.
   at Microsoft.SharePoint.Deployment.DeploymentStreamingContext..ctor(ObjectMan
ager objectManager, DataFileManager fileManager, ViewFormsList viewForms)
   at Microsoft.SharePoint.Deployment.ImportStreamingContext..ctor(ImportObjectM
anager objectManager, ImportDataFileManager importFileManager, SPImportSettings
importSettings, ViewFormsList viewList)
   at Microsoft.SharePoint.Deployment.ImportObjectManager..ctor(SPDeployment dep
loymentDriver, SPSite site, SPImportSettings importSettings, ImportDataFileManag
er dataFileManager, ViewFormsList viewForms)
   at Microsoft.SharePoint.Deployment.SPImport.InitializeImport()
   at Microsoft.SharePoint.Deployment.SPImport.Run()
Progress: Import Completed.
Finish Time: 3/31/2010 8:33:43 PM.
Completed with 0 warnings.
Completed with 1 errors.

Log file generated:
        c:\angelbkp\angelbkp.cmp.import.log

The specified user MSWSS01\Administrator could not be found.
------------------------------------ -------------------------------------- ------------------------------------

Hope the above last line tells that the "MSWSS01\Administrator" is not an user on the SharePoint site.

I could able to see the SharePoint site which has been imported functioning on the new server,  but it has the same URL as it was having with the old server.

The new SharePoint site which was created prior to importing the SharePoint site was not affected and is the same.

Now the issue am having is that, The SharePoint site has been imported on to the new server. I could see the site functioning. But I cant see the site listed on the central administration and also could not able to locate the DB on the drives of the imported site.

Any thoughts/ideas/solutions please...

Basically am not aware how the import and export works.

Thanks
0
ncomperAuthor Commented:
Hi Experts,

Have done a fresh install of the pre-requisites and WSS 3.0

And I could able to make it using the SQLCMD command instead of the OSQL.


Thanks
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.