Some conditions, such as having tasks that are pending change approval in CollabNet TeamForge and Microsoft Project, cause synchronization to fail.
If you have tasks that are pending change approval in CollabNet TeamForge , you will receive warnings during synchronization. Address any pending change requests, then try your synchronization again.
If you have a task that has either no start or no end date, and one or more dependencies, you will receive warnings that you're unable to synchronize. Add the missing date or remove the dependencies, then try your synchronization again.
Milestones with either predecessor or successor dependencies on other milestones or on regular tasks will cause synchronization errors. To remove these errors, remove the milestone dependencies in your Microsoft Project plan, then try your synchronization again.
All dependencies must be task-to-task. Predecessor or successor dependencies between a task and a task folder, a task and a critical or milestone task, or any combination thereof, will cause synchronization errors. To remove these errors, remove all non task-to-task dependencies, then try your synchronization again.
All dependencies must be finish-to-start. Microsoft Project supports other types of dependencies, such as start-to-start; however, these are not supported by CollabNet TeamForge and will cause synchronization errors. To remove these errors, remove all non finish-to-start dependencies, then try your synchronization again.
A Microsoft Project journal file is created automatically with each Microsoft Project file that you synchronize with CollabNet TeamForge Enterprise Edition 4.4 and later versions. If this file is missing, you will receive synchronization errors or data loss. To remove these errors, locate the journal file and copy it into the same directory where your Microsoft Project file is saved.