Migrate WSS 2.0 site to WSS 3.0 - billdebu

24-Nov-06 01:45:01
I have two different servers with old version on one and new version on the
other. I want to copy over my WSS 2 sites/content to the new WSS 3 server. So
far have tried smigrate.exe. This fails to restore to the WSS 3 server.
-------------------------------------------
24 Nov 2006 12:36:06 -0600      ERROR (possibly fatal):
ERROR:  327747 Server error: The operation failed because an unexpected
error oc
curred. (Result Code: 0x81071e57)
-------------------------------------------
Have done backup/copy with frontpage 2003 before but doubt that will work
with new WSS 3 server.
Will Sharepoint designer work to do this?
Or is stsadm.exe my best bet?
button
 
 

Migrate WSS 2.0 site to WSS 3.0 - billdebu

24-Nov-06 01:50:02
stsadm not working because I am trying to get at sites that are not top-level 
sites.
button
 

Migrate WSS 2.0 site to WSS 3.0 - Mike Walsh

24-Nov-06 03:10:28
smigrate won't work. It isn't available for WSS v3.

The only way MS have given us to move only part of WSS v2 installations is
to first upgrade the whole installation to v3 (in site; or saving a database
and using that for the new installation) and then use v3 tools to extract
part of the installation to transfer it to another v3 installation.

Mike Walsh
WSS FAQ www.wssfaq.com / wss.collutions.com
button
 

Migrate WSS 2.0 site to WSS 3.0 - billdebu

24-Nov-06 04:25:01
Thanks Mike, I was proceeding this way and then the darn WSS 2 server just
would not take the inplace upgrade to WSS 3. Went through some info on using
the preupgradescan tool but never did find the darn prescanconfig.xml file to
use with it. So, that was a wash for today. Didn't have the energy to plug
away at the error log.
It would be a real shame if there is no tool released for doing this. Seems
it will be pretty common scenario. IMHO
button
 

Migrate WSS 2.0 site to WSS 3.0 - Mike Walsh

25-Nov-06 03:10:55
I'm hoping for some third-party tools.

MS seem pretty determined to make us go the 'upgrade in place or to another
server via a database backup' route.

If it's any consolation (it isn't for me) I asked for something similar to
smigrate to move lists a long time before the beta moved to public beta
status.

I suppose there's a technical reason I don't know about why they didn't
continue with the smigrate route that worked so well from STS to WSS 2.0.

As I said, all we can do is wait and hope. I've had little success with the
upgrade in place option either so I'm going to try the db backup method
next.

Mike Walsh
WSS FAQ www.wssfaq.com / wss.collutions.com
button
 

Migrate WSS 2.0 site to WSS 3.0 - Steve Chen

11-Jan-07 10:25:08
Hi there,



I have the same error by tryin migrate a saved sitecollection from WSS v2 into a runnin WSS v3. Seems to me that there is no way by now to handle this with the MS Boarding tools.



One solution for you about the "prescan-Problem" is, forget the XML-file and take the command just with "preupgradescan /all" and it'll work ;-)



For the other thing, take a second server with a copy of your sharepoint(WSSv2) and do the implace upgrade there. after that you'll be able to migrate with stsadm.exe (located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12) all subsites etc. to your new WSSv3.



so far, greets and good luck, Steve
button
 
Seeing accepted meeting workspace requests in Attendees list