MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Upgrade or Migrate - WSS V3 site collection to MOSS 2007

  Asked By: Carlos    Date: Apr 23    Category: MOSS    Views: 8055

I have been given a taks of looking into the feasibility of Moving / Upgrading
/ Migrating the present WSS V3.0 sites/site collection to the latest version of
MOSS 2007.
I was wondering if there is any standard procedure in place to this so that I do
not miss out on any data in the WSS server. I need all the workflows, document
versions, user groups (if possible) etc to be up and running on MOSS 2007.

I looked into couple of articles on the internet and found some info to use
STSADM export/import. But this did not solve the purpose.
I ran the following command: ...\12\BIN>stsadm.exe -o export -url <individual
site http://servername/foo> -filename C:\_backup.bak -includeusersecurity
-versions 4 [this saves all the document versions] to EXPORT the complete site
along with its data from the WSS V3 box.

On the MOSS 2007 installed server, i ran the following command after already
creating a subsite. ...\12\BIN>STSADM.EXE -o import url <the newly created site>
-updateversions 1.
But after running this i get a Fatal error. The error details:
FatalError: Could not find Feature PawnContactsList.
n(SPRequirementObject reqObj)
Object reqObj)
at Microsoft.SharePoint.Deployment.SPImport.VerifyRequirements()
at Microsoft.SharePoint.Deployment.SPImport.Run()
Progress: Import Completed.
Finish Time: 3/25/2008 12:56:11 PM.
Completed with 0 warnings.
Completed with 1 errors.

Does anyone know what is causing this error?



4 Answers Found

Answer #1    Answered By: Delilah Mcpherson     Answered On: Apr 23

After some research on the internet and on my own, i was able to port/migrate my
WSS 3.0 individual sites to MOSS 2007. Hope this will help someone who is
looking into similar solution or facing issues.
Though the usersecurity properties were not copied to the destination, I could
live with it. I used the famous "stsadm.exe" to export individual sites. Then
use the same exe to import to the destination.

The commands that i used are:

Site Export: stsadm -o export -url <source URL to export> -filename <local or
network share file name to be created> -includeusersecurity -versions 4

Site Import: stsadm -o import -url <destination URL> -filename <*.bak or *.*
file saved using export parameter> -updateversions 1

I was able to successfully import 4 sites which had an average size of 400 MB
and with some customizations [features, webparts etc]. But, when i tried to
import a site  which was like ~3GB, i had some issues. I was able to resolve
couple of issues which showed up initially about features present in source and
not present in destination.
So, the problem which was repeating multiple times while importing was
something related to a Data Sheet View list. This list has nearly 4000 rows. The
export was fine as the exe just dumps the data. Importing complained with the
following error:

FatalError: The element 'WebPart' in namespace 'urn:deployment-manifest-schema'
has invalid child element 'OpenApplicationExtension' in namespace
'urn:deployment-manifest-schema'. List of possible elements expected: 'Script,
PagedRowset, PagedClientCallbackRowset, PagedRecurrenceRowset, ViewFields,
ViewData, Query, RowLimit, RowLimitExceeded, Toolbar, Formats, Aggregations,
ViewStyle, View
Body, ViewEmpty, ViewFooter, ViewHeader, ViewBidiHeader, GroupByFooter,
GroupByHeader, CalendarViewStyles, ListFormBody' in namespace
eventHandler, Object sender, XmlSchemaValidationException e, XmlSeverityType
name, ValidationState context, ValidationEventHandler eventHandler, Object
sender, String sourceUri, Int32 lineNo, Int32 linePos, Boolean getParticles)
elementName, Boolean& invalidElementInContext)
at System.Xml.Schema.XmlSchemaValidator.ValidateElement(String localName,
String namespaceUri,
XmlSchemaInfo schemaInfo, String xsiType, String xsiNil, String
xsiSchemaLocation, String xsiNoNamespaceSchemaLocation)
at System.Xml.XsdValidatingReader.ProcessElementEvent()
at System.Xml.XsdValidatingReader.ProcessReaderEvent()
at System.Xml.XsdValidatingReader.Read()
at System.Xml.XmlWriter.WriteNode(XmlReader reader, Boolean defattr)
at System.Xml.XmlReader.ReadOuterXml()
at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType,
Boolean isChildObject)
at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type
objectType, Boolean isChildObject, DeploymentObject envelope)
at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream
at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream
at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
at Microsoft.SharePoint.Deployment.SPImport.Run()
Progress: Import Completed.
Finish Time: 4/2/2008 11:02:52 AM.
Completed with 2 warnings.
Completed with 1 errors.

If anyone knows what this type of error means and how to recitify - please let
me know.

Answer #2    Answered By: Gobinda Navalagi     Answered On: Apr 23

A list of with 4000 items in the root is going to be a problem. 2000 is
normally the limit people try to stick to. If you remove that web part
are you able to restore the web? Then you can just add the web part
back after it's imported.

Answer #3    Answered By: Rose Silva     Answered On: Apr 23

The error that is shown is not with a webpart. its with a list.
is there a way to remove only this list while taking a backup?
And later when its restored, adding it back will all that i need.

Answer #4    Answered By: Maegan Ellison     Answered On: Apr 23

You might have to use a third party solution to migrate  the list over.
Metalogix and Avepoint both make very good products.

Didn't find what you were looking for? Find more on Upgrade or Migrate - WSS V3 site collection to MOSS 2007 Or get search suggestion and latest updates.