Leveling Changes work hours from 2 hrs to 14,944

[Barb K]

I have a project that was created in 2007 Project Pro and saved locally. I
imported the project onto the Enterprise server. Now I want to do some
updates. I retrieved the project from the enterprise server and have all of
my work hours. All tasks have the same resource on all of them. There are
many tasks that start on the same day. When I level the resources I have one
task that was 2 hrs of work is now 14,944 hours and one other that was 8 hrs
is now 73,119 hrs. I have not had this problem with projects that were
created and saved directly on the enterprise server.

Has anyone encountered this problem?

 

[Mike Glen]

Hi Barb,

Try posting on the server newsgroup. Please see FAQ Item: 24. Project
Newsgroups. FAQs, companion products and other useful Project information
can be seen at this web address: http://project.mvps.org/faqs.htm

Mike Glen
Project MVP

 

[Steve]

Hi: I'm seeing a similar behavior in 2007 Project Pro, but w/o Enterprise
server. When I manually level my project, I get some tasks in which the work
is recalculated from xx hours to yy,yyy hours. This must be a bug (right?).
I'm new to leveling, but I thought that task work should always remain the
same and it's the duration that may change?

-Steve

 

[Mike Glen]

Hi Steve,

Welcome to this Microsoft Project newsgroup

Have you installed SR1? Incidentally, all levelling does is to delay tasks
until the resources are available - nothing else.

FAQs, companion products and other useful Project information can be seen at
this web address: http://project.mvps.org/faqs.htm

Hope this helps - please let us know how you get on

Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for Project Tutorials

 

[Steve]

Mike, I have not applied SR1, but I did look at the speadsheet of fixed
problems for SR1 and there was no mention of resolved levelling issues. I'll
install SR1 anyway and see if it helps. If that doesn't work, I'll also try
the procedure for fixing a potentially corrupt project file.

Yes, I'm aware that all leveling should do is set the leveling delay (and I
believe also the assignment delay if splitting assignments is checked) field
when overallocations are detected. That's why I was surprised that work was
being recalculated at all. Thanks for the response.

-Steve

 

[Mike Glen]

You're welcome, Steve Let us know how you get on.

Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for Project Tutorials

 

[Steve]

I installed SP1, but it unfortunately did not fix the problem. Neither did
saving the file to XML and reimporting it. What did work is to delete the
offending tasks (the ones where the work was being erroneously recalculated
by the leveling engine) and then recreate those tasks. After I did that, I
re-leveled and it appeared to work. Hopefully, this will not crop up again.

-Steve

 

[Mike Glen]

Thank you, Steve, for the feedback. Glad you got it fixed now.

Mike Glen
Project MVP