RE: [OzMOSS] MOSS Content deployment Errors
Thanks David. Looks like a real gotcha. Will give it a go and see how I go. Cheers, Aaron From: SEARLE,David Sent: Wednesday, 7 May 2008 10:49 AM To: 'listserver@ozMOSS.com' Subject: RE: [OzMOSS] MOSS Content deployment Errors Hi Aaron, Going through the same pain here with Content Deplyment. I have found the series of articles written by Stefan Grossner really helpful, especially this one: http://blogs.technet.com/stefan_gossner/archive/2008/04/11/deep-dive-into-the-sharepoint-content-deployment-and-migration-api-part-6.aspx Note: number 3) about creating a real blank site collection instead of using the Blank Template, i use his approach and works well. Also point 5) about not activating custom features on the destination web application is a gotchya too. Good luck, Dave From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Saikovski Sent: Tuesday, 6 May 2008 3:44 PM To: listserver@ozMOSS.com Subject: [OzMOSS] MOSS Content deployment Errors Dear All, I am having a fun time trying to get content deployment working between a staging and production server and was wondering if anyone else has found any gotchas or potential settings I have missed getting this working. I performed the following steps: 1. On the destination server farm, create an empty site collection based on the Blank Site template to receive the initial deployment job. 2. On the destination farm, on the Content Deployment Settings page in Office SharePoint Server 2007 Central Administration, configure the farm to accept incoming deployment jobs, assign a front-end server as the import server to manage incoming deployment jobs, and specify whether or not to require encryption on the connection between the source and destination farms. 3. On the source farm, on the Content Deployment Settings page, assign a front-end server as the export server to manage outgoing deployment jobs. 4. On the source farm, on the Manage Content Deployment Paths and Jobs page in Office SharePoint Server 2007 Central Administration, create one or more deployment paths. 5. On the source farm, on the Manage Content Deployment Paths and Jobs page, create one or more deployment jobs for each path. 6. Run the initial deployment job to initiate the content on the destination farm. 7. If the path does not deploy all security information, then on the destination farm, create the initial set of users, roles, and permissions on content and sites. From this article: http://technet2.microsoft.com/Office/f/?en-us/library/edcdacca-8013-460e-95a0-d2b83b6cc7ef1033.mspx and also followed this one: http://technet.microsoft.com/en-us/library/cc261732.aspx The content deploy job runs and the .cab files get created and sent up to the production server no worries. The error I keep getting is that the list ‘/contact’ exists and cannot be overwritten during import. This is weird, especially in light of the fact that I have created a blank site collection to do the initial deployment drop. I have even tried to do an export and import to get the server all setup with master pages etc and I get an even stranger error when trying to do a deploy. I have heard of problems with this technology but didn’t figure it would be this troublesome. I am using domain admin service accounts to perform the deploy so I don’t think this is a security issue. Do tools like Tzunami and Echo get around this? Any thoughts would be appreciated. Anything obvious I should be checking for? I have checked the event logs etc and they aren’t very helpful. Cheers, Aaron Aaron Saikovski Senior Solutions Specialist – Information Worker Groove MVP M: +61 (0) 410 480 971 P: 02 9448 7300 F: 02 9475 0417 A: Level 21, 8-20 Napier Street, North Sydney NSW 2060 E: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] W: www.sdm.com.au http://www.sdm.com.au/ strategic data management Consult ♦ Develop ♦ Integrate ♦ Deliver Microsoft Application Infrastructure Development Partner of the Year 2007 Business Performance Management l Business Consulting l Customer Relationship Management Enterprise Project Management l Information Worker l Systems Integration This email and any files transmitted with it are confidential and are only for the use of the person to whom they are addressed. If you are not the intended recipient you have received this email in error and are requested to delete it immediately. Any opinion expressed in this e-mail may not necessarily be that of Strategic Data Management Pty Ltd. Please consider the environment before printing this email. ;3I'ڞ˱mkɲzˁrKˊ؞˱mrfnW Notice: The information contained in this email message and any attached files may be confidential information, and may also be the subject of legal
RE: [OzMOSS] MOSS Content deployment Errors
I had huge fun (not) with the import/export API trying to do something similar but in code. I’ve NOT used the Content Deployment Manage/Settings pages, but these are the thing I found out using the API directly: Usually inconsistencies in the two structures were causing me problems. If that doesn’t seem to be the case, other things to look at: The import/export classes have a logfilelocation property – I presume you have looked at those logs, (but might just be the same as the job report)? The classes have a large number of options – things like ExcludeDependencies on the export and RetainObjectIdentity on the import may be tripping you up. You can break up the export/import manually to test things in code– maybe try the list on its own to see what happens? You can also use STSADM to test things, although many of the properties aren’t available (probably STSDEV has these). Make sure you are up to date with patches/releases in source and destination, and I also seem to remember there is a hotfix to do with content deploy if appropriate. Hope something here helps. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Saikovski Sent: Tuesday, 6 May 2008 1:44 PM To: listserver@ozMOSS.com Subject: [OzMOSS] MOSS Content deployment Errors Dear All, I am having a fun time trying to get content deployment working between a staging and production server and was wondering if anyone else has found any gotchas or potential settings I have missed getting this working. I performed the following steps: 1. On the destination server farm, create an empty site collection based on the Blank Site template to receive the initial deployment job. 2. On the destination farm, on the Content Deployment Settings page in Office SharePoint Server 2007 Central Administration, configure the farm to accept incoming deployment jobs, assign a front-end server as the import server to manage incoming deployment jobs, and specify whether or not to require encryption on the connection between the source and destination farms. 3. On the source farm, on the Content Deployment Settings page, assign a front-end server as the export server to manage outgoing deployment jobs. 4. On the source farm, on the Manage Content Deployment Paths and Jobs page in Office SharePoint Server 2007 Central Administration, create one or more deployment paths. 5. On the source farm, on the Manage Content Deployment Paths and Jobs page, create one or more deployment jobs for each path. 6. Run the initial deployment job to initiate the content on the destination farm. 7. If the path does not deploy all security information, then on the destination farm, create the initial set of users, roles, and permissions on content and sites. From this article: http://technet2.microsoft.com/Office/f/?en-us/library/edcdacca-8013-460e-95a0-d2b83b6cc7ef1033.mspx and also followed this one: http://technet.microsoft.com/en-us/library/cc261732.aspx The content deploy job runs and the .cab files get created and sent up to the production server no worries. The error I keep getting is that the list ‘/contact’ exists and cannot be overwritten during import. This is weird, especially in light of the fact that I have created a blank site collection to do the initial deployment drop. I have even tried to do an export and import to get the server all setup with master pages etc and I get an even stranger error when trying to do a deploy. I have heard of problems with this technology but didn’t figure it would be this troublesome. I am using domain admin service accounts to perform the deploy so I don’t think this is a security issue. Do tools like Tzunami and Echo get around this? Any thoughts would be appreciated. Anything obvious I should be checking for? I have checked the event logs etc and they aren’t very helpful. Cheers, Aaron Aaron Saikovski Senior Solutions Specialist – Information Worker Groove MVP M: +61 (0) 410 480 971 P: 02 9448 7300 F: 02 9475 0417 A: Level 21, 8-20 Napier Street, North Sydney NSW 2060 E: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] W: www.sdm.com.au http://www.sdm.com.au/ strategic data management Consult ♦ Develop ♦ Integrate ♦ Deliver Microsoft Application Infrastructure Development Partner of the Year 2007 Business Performance Management l Business Consulting l Customer Relationship Management Enterprise Project Management l Information Worker l Systems Integration This email and any files transmitted with it are confidential and are only for the use of the person to whom they are addressed. If you are not the intended recipient you have received this email in error and are requested to delete it immediately. Any opinion expressed in this e-mail may not necessarily be that of Strategic Data Management Pty Ltd. Please
