Hello,I am setting up our content deployment and have run into unusual errors. Through central admin I created the paths and an incremental job, which runs every hour.I set up a test group of users who have site owner access on the first server and read only for the second. The users make their changes and several of the jobs run successfully. Eventually a job will fail and I get these errors: Save Conflict Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes. at Microsoft.SharePoint.Library.SPRequest.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bMigration, Boolean bPublish) at Microsoft.SharePoint.SPListItem.AddOrUpdateItem(Boolean bAdd, Boolean bSystem, Boolean bPreserveItemVersion, Boolean bNoVersion, Boolean bMigration, Boolean bPublish, Boolean bCheckOut, Boolean bCheckin, Guid newGuidOnAdd, Int32& ulID, Object& objAttachmentNames, Object& objAttachmentContents, Boolean suppressAfterEvents) at Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, Boolean suppressAfterEvents) at Microsoft.SharePoint.SPListItem.MigrationAddOrUpdate(Boolean bAddNew, Boolean bIsPublish, Guid newGuidOnAdd, Boolean bNoVersion, Boolean suppressAfterEvents) at Microsoft.SharePoint.Deployment.ListItemSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector) 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 serializationStream) at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream) at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader) at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() at Microsoft.SharePoint.Deployment.SPImport.Run() Failed import operation for Content Deployment job 'Remote import job for job with sourceID = 2b95edb6-d8fb-4b4d-bdc1-c957d3c5e37b'. Exception was: 'Microsoft.SharePoint.SPException: Save Conflict Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes. ---> System.Runtime.InteropServices.COMException (0x81020037): Save Conflict Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes. at Microsoft.SharePoint.Library.SPRequestInternalClass.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarPrope Once this error appears, none of the jobs will work again. This error also appears in the sharepoint logs. I have tried to determine what could cause this error, and have deleted the second servers site collection and started over several times. Each time things are running smoothly for a few job runs, but eventually the error presents itself again.Any help resolving this issue would be greatly appreciated. We would like to use content deployment in a stage to production scenario.Thanks.

I retried to set things up and I have a little bit more information from the logs.On the first server I see the log that shows the export starting / ending, and there are no errors logged. 01/16/2008 14:05:05.90 OWSTIMER.EXE (0x2420) 0x0F98 Windows SharePoint Services Upgrade 0 High Starting Export. 01/16/2008 14:05:50.33 OWSTIMER.EXE (0x2420) 0x0F98 Windows SharePoint Services Upgrade 0 High Export Completed.On the second server the import starts and then the log shows several errors and then the exception I reported earlier. 01/16/2008 14:06:04.62 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services Upgrade 0 High Initializing Import. 01/16/2008 14:06:06.15 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services Upgrade 0 High Starting content import. 01/16/2008 14:06:06.26 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:06.35 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:06.41 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:06.44 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:07.15 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:08.29 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:08.65 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:09.18 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:09.66 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 72lp Medium Creating directory SitesList/Sites(1904761978) 01/16/2008 14:06:09.96 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:10.37 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002 01/16/2008 14:06:10.58 OWSTIMER.EXE (0x1344) 0x0D34 Windows SharePoint Services General 8e2s Medium Unknown SPRequest error occurred. More information: 0x80070002I haven't seen much information online that could point me into the right direction. If this helps shed any light on the situation I would be very grateful.

Not Yet. I am researching the problem and I think the error has to deal with the timer and interop services. I am looking into scheduling things on my own and using stsadm export and import commands.

I have a similar error right now. I've found in the past that the smallest item discrepancy between production and authoring might cause this - but have a real hard time finding the specific enough log to remedy it. In other words, if I've done so much as inadvertently checked out a page in production (deployment target) it'll cause the deployment to fail or time out. This time, however, I've got a slightly different error than before that seems to match up with yours: Save Conflict Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes. ...interested in your findings... ~jake

I had to open a ticket with Microsoft to hopefully shed some light. So far we haven't made any type of progress on fixing the issue.I have tried using the stsadm commands to get the export and import to work, and even though the job failed with that error. The stsadm commands work perfectly. However, I'm not sure how to get the same exact settings that we get in the job definition. Role based security and deploying usernames. These options don't seem to be part of the stsadm commands.So while Microsoft tries to get things to work with the job, I'm thinkin gthe proper path might be to schedule things on my own.

Were you able to resolve this? I am experiencing the same issue.

I am also getting the same error now. Have you got in sucess in fixing this issue???

We have this same issue, no solutions yet, waited for last one and half year, no luck with MOSS SP1 either. Full deployment is only solution we have, but never deletes list items or pages from destination server. If alerts are used in sites, survery's ..etc..are used in production sites, export and import will overwrite all, so that solution is not feasible.

Not sure if it will fix your issues but Microsoft is now making available a content deployment QFE pack which addresses something like 60+ CD issues. I'd recommend calling them and see if it fixes your problems. Also - make sure that your target server is effectively read-only.

Is there anything know to this if it solved the problem? We ran into this problem as well Kind regards, Gabriel.

We're running into this problem now. C'mon MS, what's the solution?

Redeployment is only option for solve the issue or you can delete the old data base and create new data base and attached backup .