Would it be possible for you to go to table sf_scheduled_tasks (for both database) and remove all tasks that you will see there (mark the row and delete it) if there are such rows? Furthermore, open the sf_site_sync_log_entry (for both databases) and delete the rows there. Then you need to recycle the application pools of the sites.
After that you need to republish all items: Page Templates, Pages, News items, Events, Blog Posts, List items, Content Items, Images, Documents, Taxonomies
You could publish them by code.
For example to publish all images use:
LibrariesManager manager = LibrariesManager.GetManager();
var images = manager.GetImages().Where(i => i.ApprovalWorkflowState ==
&& i.Status == ContentLifecycleStatus.Master).ToList();
Place the code inside a web form and execute it in the browser. Make sure that you are logged in the backend before executing the code.
To publish all documents:
var libraries = manager.GetDocumentLibraries();
var documents = manager.GetDocuments().Where(d => d.Status == ContentLifecycleStatus.Master && d.Parent == library).ToList();
var pageManager = PageManager.GetManager();
var getPage = pageManager.GetPageNodes().Where(p => p.ApprovalWorkflowState ==
var master = pageManager.PagesLifecycle.Edit(page.Page);
Note that the synchronization is one way, you could synch from Staging to Production, but once you have synchronized from Staging to Production, you should not synch from Production to Staging, because you might encountered problems with the synchronization after that.
We support only sync from A to B and the key set in A should be smaller than the number set on B. These special keys are introduced and described in our documentation.
Please make sure that you entered administrators credentials in the first site and you are not logged in the second site.
In the meantime what would you suggest is the best way to sync data back from production?
We have module builder modules for custom data collection that we would like to sync back to staging, then dev, etc... so that we can have the current data in all environments for testing and reporting on the collected data.
Could we program scheduled tasks that safely move data from production server back to other servers?
Any ideas are greatly appreciated
The only "solution" (as bad as it is) that I am aware of is to copy the database down to local and then use something like the script earlier in this thread republish all of the content so the IDs are no longer the same. Note, I have not tried this, and it is horribly manual-intensive.
This is a significant area Sitefinity could improve, and there is no GOOD workaround that we have found. I emailed support, and their answer was basically "WON'T FIX". Seeing as many other similar CMSes offer a two-way sync, it should be at least in the backlog as a to-do item, IMO.