RE: MOSS 2007 Content Deployment Problems
Yeah, it's starting to sound like a site level dependency. Try a full backup/restore job to an empty site. You might then be able to perform standard deployment jobs. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Ajay Sent: Tuesday, 8 November 2011 5:01 PM To: ozMOSS Subject: Re: MOSS 2007 Content Deployment Problems 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.commailto: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.aumailto: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.commailto:ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.commailto: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.commailto: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
RE: Import error - guidance on troubleshooting please.
Yikes. :\ From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Mike MOSSuMS Stringfellow Sent: Tuesday, 8 November 2011 4:28 PM To: ozmoss@ozmoss.com Subject: RE: Import error - guidance on troubleshooting please. Ok - it looks like this actual 2010 install is FUBAR, as the import works fine on my dev environment and there are a variety of error in the logs, including this from nasty from SQL when importing the list: Unknown SQL Exception 206 occurred. Additional error information from SQL Server is included below. Operand type clash: datetime is incompatible with uniqueidentifier A re-run of the config wizard, and a repair, both gave this message (WEBCONFIG.ACCSRV.XML file is identical to one on my 'nilla dev sp2010): An exception of type System.IO.InvalidDataException was thrown. Additional exception information: The web configuration file, C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\config\WEBCONFIG.ACCSRV.XML, does not have element configuration/configSections/sectionGroup[@name='SharePoint'] or it is invalid. Next steps will be a reboot and then a complete reinstall, unless there are some other ideas? From: mike_stringfel...@hotmail.com To: ozmoss@ozmoss.com Subject: RE: Import error - guidance on troubleshooting please. Date: Tue, 8 Nov 2011 10:06:39 +0800 Many thanks for your help Paul and Matthew Definately sounds like we are all thinking the same way as I've checked those things. Pach level was fine as it's been moved to the same farm - however missing feature references etc in the content, as it originally came from 2007 and was then upgraded, is a distinct possibility. We've also tried without identity, security, versions and dependecies - same darn com error. It's an RTM 2010, so I'm just investigating if there have been any import/export/content migration fixes making SP1 + Oct CU worthwhile - none i can see so far. However, if there is some sort of server issue an upgrade may be worthwhile. The GL command didn't help, as it does exactly the same stuff under the skin, so threw the same unhelpfull error. I'll have a look at the Chris O'Brian content migration wizard next. From: paul.no...@ceosyd.catholic.edu.au To: ozmoss@ozmoss.com Date: Tue, 8 Nov 2011 09:16:22 +1100 Subject: RE: Import error - guidance on troubleshooting please. I'd start by ditching dependencies and security on the export and see if it will import OK. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Mike MOSSuMS Stringfellow Sent: Monday, 7 November 2011 6:10 PM To: ozmoss@ozmoss.com Subject: Import error - guidance on troubleshooting please. Any advice on the quickest way to trouble-shoot the below error when importing a list that was exported from a different farm? Are the ULS logs the place to start, or does the import show all the info available to stdout? Or does anyone recommend a tool or technique that gives generally better rsults/insights that the standard import/export - e.g. gl-exportlist and gl-importlist? In anticipation, thanks for your help! export-spweb -IDENTITY http://OldSiteURLhttp://oldsiteurl/ -ITEMURL OldListURL -PATH c:\temp\export.cmp -FORCE -INCLUDEUSERSECURITY -INCLUDEVERSIONS 4 import-spweb -IDENTITY https://NewSiteURLhttps://newsiteurl/ -PATH c:\temp\export.cmp -FORCE -INCLUDEUSERSECURITY -UPDATEVERSIONS OVERWRITE -VERBOSE [7/11/2011 10:29:14 AM] [List] [ListName] Progress: Importing [7/11/2011 10:29:14 AM] [List] [ListName] ExtendedVerbose: Creating [7/11/2011 10:29:14 AM] [List] [ER.BusinessUnits] Error: An unexpected error has occurred. [7/11/2011 10:29:14 AM] [List] [ER.BusinessUnits] Debug:at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) at Microsoft.SharePoint.Library.SPRequest.CreateListOnImport(String bstrUrl, Guid pguidListId, String bstrTitle, String bstrDescription, Int32 lTemplateID, String bstrFeatureId, Guid guidRootFolderId, Int64 llFlags, Int32 iVersion, Int32 iAuthor, String bstrFields, String bstrContentTypes, String bstrImageUrl, String bstrEventSinkAssembly, String bstrEventSinkClass, String bstrEventSinkData, Guid guidDocTemplateId, String bstrViews, String bstrForms, Boolean bCompressedSchema, DateTime dtTimeCreated) at Microsoft.SharePoint.Deployment.ListSerializer.CreateList(SPWeb parentWeb, Dictionary`2 listMetaData, Boolean usingPublicSchema) at Microsoft.SharePoint.Deployment.ListSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector) at Microsoft.SharePoint.Deployment.XmlFormatter.CallSetObjectData(Object obj, SerializationInfo objectData, ISerializationSurrogate surrogate, ISurrogateSelector selector) [7/11/2011 10:29:14 AM] FatalError: An unexpected error has occurred. [7/11/2011 10:29:14 AM] Debug:at
Issue using a Template with a Document Content Type
Hi, We have created a content type that inherits from Document and the only additional configuration is to provide an Excel file for a template. After adding this content type to a Doc Library, when a user creates a new file, they are immediately promted to 'Save As' the excel file into the folder at /site/doclibrary/Forms/ContentTypeName as 'SDS_Template1.xls' before the new spreadsheet is opened for editing. Note: name of the file uploaded as the template is 'SDS_Template.xls'. Once the file is either saved or the save request is cancelled, the user can edit the new instance of the excel spread and when saved it placed the editied file in the /site/doclibrary/ location as expected, with a default filename of 'SDS_Template1.xls'. The issue only occurs for a specific excel spreadsheet, i.e. if the content type is updated to use a different spreadsheet for the template, then the user is not prompted to save the file into the content type folder each time a new item is created. -has anyone seen or resolved this issue before? I guess it is something specific about the Excel template that was provided to me... but not sure what to look for. regards, Ricky Elias Software Consultant P: 07 3221 2858 M: 0420 275 002 F: 07 3221 3812 A: Podium Level 1, 320 Turbot Street, Brisbane QLD 4000 E: ricky.el...@dws.com.aumailto:jason.si...@dws.com.au W: www.dws.com.auhttp://www.dws.com.au/ DWS ADVANCED BUSINESS SOLUTIONS ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Issue using a Template with a Document Content Type - Solution
Thanks Paul, Have now found the setting in the workbook that does cause the issue. In the xls provided, a checkbox was selected at MenuToolsShare Workbook'Allow changes by more than one user at the same time. This also allows workbook merging'. De-selecting this checkbox has resolved the issue. The organisation is using MOSS and Excel 2003 - so this issue may have been resolved in later versions. regards, Ricky Elias Software Consultant P: 07 3221 2858 M: 0420 275 002 F: 07 3221 3812 A: Podium Level 1, 320 Turbot Street, Brisbane QLD 4000 E: ricky.el...@dws.com.aumailto:jason.si...@dws.com.au W: www.dws.com.auhttp://www.dws.com.au/ DWS ADVANCED BUSINESS SOLUTIONS [X] From: ozmoss-boun...@ozmoss.com [ozmoss-boun...@ozmoss.com] on behalf of Paul Noone [paul.no...@ceosyd.catholic.edu.au] Sent: Wednesday, 9 November 2011 2:47 PM To: ozMOSS Subject: RE: Issue using a Template with a Document Content Type Did you apply the template through the UI at the site collection Content Type level? Have you tried resaving it out as an XLS file with a different name and uploading it again? Could it have been saved as the wrong file type with a macro hidden away in it? From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Ricky Elias Sent: Wednesday, 9 November 2011 3:33 PM To: ozmoss@ozmoss.com Subject: Issue using a Template with a Document Content Type Hi, We have created a content type that inherits from Document and the only additional configuration is to provide an Excel file for a template. After adding this content type to a Doc Library, when a user creates a new file, they are immediately promted to 'Save As' the excel file into the folder at /site/doclibrary/Forms/ContentTypeName as 'SDS_Template1.xls' before the new spreadsheet is opened for editing. Note: name of the file uploaded as the template is 'SDS_Template.xls'. Once the file is either saved or the save request is cancelled, the user can edit the new instance of the excel spread and when saved it placed the editied file in the /site/doclibrary/ location as expected, with a default filename of 'SDS_Template1.xls'. The issue only occurs for a specific excel spreadsheet, i.e. if the content type is updated to use a different spreadsheet for the template, then the user is not prompted to save the file into the content type folder each time a new item is created. -has anyone seen or resolved this issue before? I guess it is something specific about the Excel template that was provided to me... but not sure what to look for. regards, Ricky Elias Software Consultant P: 07 3221 2858 M: 0420 275 002 F: 07 3221 3812 A: Podium Level 1, 320 Turbot Street, Brisbane QLD 4000 E: ricky.el...@dws.com.aumailto:jason.si...@dws.com.au W: www.dws.com.auhttp://www.dws.com.au/ DWS ADVANCED BUSINESS SOLUTIONS ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
