This looks tricky as stsadm - backup/restore is much more robust than stsadm import. In most cases when we had issue with export-import -- backup/restore has worked well.
Can you do one quick test to validate if it's the data in site causing the issue by creating a new OOTB site collection and just put it 1-2 documents and items and see if that works. On Tue, Nov 8, 2011 at 6:06 PM, Chris Howell <cjhow...@gmail.com> wrote: > Hi, > > Sorry for the delay in replying. > > - Yes, both farms are 64-bit. > - Both are in the same domain. > - Yes, path to log files is the same in both. > - Both farms are based on Server 2003 so no UAC > > I've also checked regional settings in every area that I can think of and > they are the same (Australian English). > > Moving content still fails if I try export from old and import to new. > Puzzled as to why this log date is showing US format though: > > [11/8/2011 3:58:48 PM]: Start Time: 11/8/2011 3:58:48 PM. > [11/8/2011 3:58:48 PM]: Progress: Initializing Import. > [11/8/2011 3:58:59 PM]: Progress: Starting content import. > [11/8/2011 3:58:59 PM]: Progress: De-Serializing Objects to Database. > [11/8/2011 3:58:59 PM]: FatalError: The ' > http://www.w3.org/2001/XMLSchema:attribute' element is not supported in > this context. > at System.Xml.Schema.XmlSchemaSet.InternalValidationCallback(Object > sender, ValidationEventArgs e) > at System.Xml.Schema.XmlSchemaSet.ParseSchema(String targetNamespace, > XmlReader reader) > at System.Xml.Schema.XmlSchemaSet.Add(String targetNamespace, String > schemaUri) > at Microsoft.SharePoint.Deployment.SPImport.CreateXmlReader(FileStream > fs, String schemaNamespace, String schemaFile) > at > Microsoft.SharePoint.Deployment.SPImport.GetNextManifestFile(XmlReaderAndStream > reader) > at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() > at Microsoft.SharePoint.Deployment.SPImport.Run() > > > On 3 November 2011 09:02, Paul Noone <paul.no...@ceosyd.catholic.edu.au>wrote: > >> Hi Chris,**** >> >> ** ** >> >> I have never managed to get clean content deployment setup between two >> apps in different domains, or with different configurations. A few things >> you could check:**** >> >> ** ** >> >> Are both farms running 64-bit OS?**** >> >> Are they in the same domain?**** >> >> Are the log file paths the same in both farms?**** >> >> Have you tried turning off UAC on the destination farm?**** >> >> ** ** >> >> ** ** >> >> *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On >> Behalf Of *Chris Howell >> *Sent:* Wednesday, 2 November 2011 4:32 PM >> *To:* ozMOSS >> *Subject:* Re: MOSS 2007 Content Deployment Problems**** >> >> ** ** >> >> Hi,**** >> >> ** ** >> >> Just an update. I made some progress by running: " psconfig -cmd upgrade >> -inplace b2b -wait" on the host where the pending upgrade was flagged. >> This completed and then Content Deployment started working.**** >> >> ** ** >> >> Now gets to the point where the Content Deployment job exports to the new >> server. Job then fails with:**** >> >> ** ** >> >> "Content deployment job 'Remote import job for job with sourceID = >> d5f5cedd-cc28-40b5-8dd9-c5f905f54e7b' failed.The exception thrown was >> 'System.IO.IOException' : 'The process cannot access the file >> 'Manifest.xml' because it is being used by another process.'"**** >> >> ** ** >> >> Chris**** >> >> On 2 November 2011 15:39, Chris Howell <cjhow...@gmail.com> wrote:**** >> >> Hi,**** >> >> ** ** >> >> Can anyone help with some Content Deployment issues I'm experiencing?**** >> >> ** ** >> >> I'm trying to move content between two DEV instances of MOSS. Both >> servers report that they are build 12.0.0.6421.**** >> >> ** ** >> >> I have tried the following and have issues at every point:**** >> >> ** ** >> >> *1. Content deployment from CA on current host pushing to new host***** >> >> Job is permanently stuck in a state of "Preparing"**** >> >> ** ** >> >> *2. Exporting/Importing site using Chris O'Brien's SharePoint Content >> Deployment Wizard***** >> >> Exports successfully from host. No errors or warnings.**** >> >> ** ** >> >> Error on import on new host: "System.IO.IOException: The process cannot >> access the file 'Manifest.xml' because it is being used by another >> process." shown in GUI**** >> >> ** ** >> >> Error in log:**** >> >> ** ** >> >> "[11/2/2011 3:31:10 PM]: FatalError: The ' >> http://www.w3.org/2001/XMLSchema:attribute' element is not supported in >> this context.**** >> >> at System.Xml.Schema.XmlSchemaSet.InternalValidationCallback(Object >> sender, ValidationEventArgs e)**** >> >> at System.Xml.Schema.XmlSchemaSet.ParseSchema(String targetNamespace, >> XmlReader reader)**** >> >> at System.Xml.Schema.XmlSchemaSet.Add(String targetNamespace, String >> schemaUri)**** >> >> at Microsoft.SharePoint.Deployment.SPImport.CreateXmlReader(FileStream >> fs, String schemaNamespace, String schemaFile)**** >> >> at >> Microsoft.SharePoint.Deployment.SPImport.GetNextManifestFile(XmlReaderAndStream >> reader)**** >> >> at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()**** >> >> at Microsoft.SharePoint.Deployment.SPImport.Run()"**** >> >> ** ** >> >> *3. Restore from CMP file***** >> >> Have tried STSADM Restore of files. Returns error:**** >> >> ** ** >> >> "Your backup is from a different version of Windows SharePoint Services >> and cannot be restored to a server running the current version. The backup >> file should be**** >> >> restored to a server with version '1178817357.0.25229151.0' or later."** >> ** >> >> ** ** >> >> I can find no information on what version this is meant to be.**** >> >> ** ** >> >> I've exhausted all the things I've come across before or can find. I've >> run preupgradecheck on the current host and that reports "*Failed : >> Pending upgrade operation detected in this farm*". There has been no >> upgrade attempted that I'm aware of and I've run the config wizard again >> with it completing successfully.**** >> >> ** ** >> >> Any help would be greatly appreciated.**** >> >> ** ** >> >> Cheers,**** >> >> ** ** >> >> Chris**** >> >> ** ** >> >> _______________________________________________ >> ozmoss mailing list >> ozmoss@ozmoss.com >> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss >> >> > > _______________________________________________ > ozmoss mailing list > ozmoss@ozmoss.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss > >
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
