Loading...
Quick Links

Corrupted tasks – Mark on track not working

Home Forums Discussion Corrupted tasks – Mark on track not working

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #412153 Reply

    On some tasks,the progress line inside their Gantt bars Mark on Track doesn’t advance the progress line, leaving an incomplete part in the past. Inserting a line and copy/pasting to it the name, duration, predecessor and successor provides a task that Mark on Track correctly advances the progress line to the Status date. Many tasks work correctly. We don’t know which tasks are corrupted until we are doing updating. Is there a way to cure this problem so that tasks don’t get corrupted? If not, is there an easy way to fix a corrupted task?
    A few weeks ago, the schedule had an excess number of external dependencies, far above the maximum recommended in Eric Uyttewaal’s new book, “Program Forecasting.” Task corruptions were occurring randomly. Now we’re down to 2 external dependencies, but random task corruptions continue to occur.

    #412154 Reply

    Hi Oliver, any chance you can put up an example?
    What version of MSP are you using?
    What version of Windows, Linux, or Apple iOS are you using?

    I’m happy to dig in to figure it out. I’ve used a lot of external dependencies (specifically in a Master Schedule set up) and have not ever seen this before.

    Mike

    #412155 Reply

    Mike, thanks. Please email me so I can reply attaching a sample file. I’ve copy/pasted the corrupted task to a blank schedule where Mark on Track fails to advance the progress line to the Status date. An inserted task works fine. ogilders@sbcglobal.net

    #412157 Reply

    More interesting:
    1. I made the sample file by copy/pasting the “corrupted task” to a new, blank schedule. Mark on Track also failed to have an effect in the sample schedule. On the next line of the sample schedule, I made a task with similar Actual Start and Duration. Mark on Track correctly advanced the progress line to the Status date. The environment has Project 2016 Pro.

    2. I copied the “corrupted task,” went to another environment with Project 2010 Pro and pasted it in a new, blank schedule. The 22 Duration task appeared with a 12 workday bar followed by a dotted line out to the 22nd workday. Progress appeared through day 7, leaving 5 workdays incomplete on the shortened bar. Mark on Track had no effect. My experience is that a task that has a dotted line following the Gantt Bar is a corrupted task.

    3. I copy/pasted the sample file to an email and sent it to myself on another machine that also has Project 2016 Pro. The “corrupted task” updated correctly with Mark on Track. So, I may have a cure.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Corrupted tasks – Mark on track not working
Your information:




9 + 1 =