Unexpected leveling behavior in Project 2003

[Aleksey Dmitriyev]

I have a problem with Leveling. I use Project 2003 Pro and Project Server
2003. The leveling works as expected when I do this:
1) Open Project 2003 Pro in local mode (not connected to the server)
2) Create a blank project and add three tasks T1, T2, T3, and then assign
resource R1 to work on these tasks. The MS Project levels them as expected.
(Auto Leveling, Standard)
3) Save the project in P1.mpp file

However if I close the Project 2003 Pro and then open it again connecting to
the project server, the behavior is different.
1) Open Project 2003 Pro connected to the Project server 2003
2) Open P1.mpp file I had saved before
3) Resources are releveled with gaps now, 2 days gaps between T1, T2, and
T3. THERE ARE NO OTHER TASKS ASSIGNED TO THE RESOURCES, THEY ARE AVAILABLE
4) Trying to clear the leveling and relevel again does not help. In fact
nothing helps.
5) If I save the P1.mpp file, I cannot get back to correct leveling even if
I close MS Project and then open it again in Local mode.

The same leveling behavior exists when I try to level projects on the
Project Server.

Has anyone seen this problem? How to do the leveling w/o gaps? Why Project
Server causes this changes in the leveling behavior?

--Aleksey

 

[Aleksey Dmitriyev]

I still have this problem. Let me try to explain it again. I have Project
Server 2003 (Enterprise mode). There is a project plan stored on that server
and 4 project managers who use MS Project 2003 on their PC's to work on the
project plan stored on the server. Project manager R. can successfully
level project plan using MS Project 2003 from his PC. When the same project
manager R. tried to level project plan connecting from another PC, it did
not level project properly, it left gaps in the resources schedule. The
other project managers get the same incorrect leveling when they try to
level the project. SO, the only working combination at this moment when
Project manager R. uses MS Project installed on his laptop. We cannot figure
out the difference in the configuration or settings that introduce this
behavior. What could it be?

--Aleksey

 

[Gary L. Chefetz \(MVP\)]

Aleksey:

This is most readily explained by differences in leveling settings between
the various machines.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-

 

[Aleksey Dmitriyev]

This would be too easy. The leveling settings are exactly the same on all
machines. I guess we need to compare all settings...

 

[Aleksey Dmitriyev]

It appears the problem was fixed in this patch:
http://support.microsoft.com/?kbid=832887

One of the machines had it installed, but another did not. However, the
About dialog box did not show the difference in version number :-(

--Aleksey

 

[Gary L. Chefetz \(MVP\)]

Yes indeed, patch management is not an MS stronghold. The only way to tell
is the file dates.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-