Corrupt Tasks Work Around

[Shawn Everingham]

I think there is a post running around here that discusses corrupt tasks in
MSPS 2007.

I want to share my ongoing issue as an administrator and don't know all the
implications of how we are "working around" the corrupted tasks.

So, here goes....

Firstly, A task is orginated and resources are applied. Two weeks or
sometime after actuals are applied, another resource is added to the task.
The project is saved and published. The resource that was added to the task
that had existing work, that resource complains of not being able to get to
"my tasks". Sure enough, a query that was posted here that reveals corrupt
tasks in MSPS 2007, shows that the task is indeed corrupt, yet only for the
added resource.

So...my fix is to create a duplicate task, remove the offending resource
from the corrupt task, and add them to the duplicated task, saving and
publishing the project. Is this the correct work around to be used?

Another similar situation involves a corrupt task in which the cause of the
corruption of the task is unknown. The task has original resources assigned
to it, with actuals applied. I have been successful in copying the task and
pasting it below the original task and then deleting the original task.
Problem is, actual work seems to get lost. Is there a way to keep actual work
in this situation? thanks!

--Technology, like art, is a soaring stretch of our imagination...Daniel
Bell. 1919

 

[Jonathan Sofer]

Can you be more specific as to what you mean exactly when you state that
"The resource that was added to the task that had existing work, that
resource complains of not being able to get to "my tasks"."?

I am interested because I have seen others with issues importing their
timesheet hours into their "My Tasks" lists and wondered if this is what you
were referring to.

Jonathan

 

[Shawn Everingham]

Ok...you have a task that was the original task, created at the project
conception and a known resource was added to that task. The project got
started. Work was done and applied to that "original" task. So the original
task has actual work. Now, all of a sudden, we add someone else to the
"original" task, in MS Project. Now...save and publish. I find the task for
the person added, is corrupt and they can't view my tasks page. So...I create
a duplicate task, just insert a line and retype the name of the task, set the
duration and type of work etc. add the new resource to that task, remove them
from the original task is the fix.

Hope that helps.

I still have a question about a corrupt task that has a resource with
applied work. What if the task gets corrupted? how do I fix? I thought I was
successful at just copying the task, inserting a line below it, and pasting
the exact same task below it, deleting the original task that got corrupted
(for what reason the corruption happens in this case I don't know). The
problem is with this technique, you loose the actual work that was applied
before the task got corrupt.

What's the solution? Thanks!

 

[Jonathan Sofer]

I found a previous response by Rod Gill and Dale Howard, both MVPs to this
same issue. Maybe this will be useful for you. It confirms this is a bug
and that it has not been fixed in SP1. There is a SQL query you can use to
identify the corrupted assignments and workarounds for this issue.

http://groups.google.com.au/group/m...st&q=corrupt+task+assignment#f0efa268dee052a8

Jonathan