Limit to the number of Tasks that will display in the Resource Ass

[Jason]

Hi,

We are having a problem with the Resource Assignemnts view. We are using
MSP 2007 in a multi server enviroment. We are loading projects into PWA with
generic resources assigned to them and then using the Resource Center and the
"View Assignments" view to see what resources have what assignments so the
filed can assign actual resources to the tasks. This has been working well
until recently.

We are now over 20,000 resource assignments and some Generic resources have
over 4,000 assignments. The view is breaking for us when we are trying to
display somewhere between 2,200 and 2,500 assignments. The error we get is:

"Either this resource has no assignments to display, you do not have
permissions to view this resource's assignments, or another user has deleted
the selected resource."

Yet we know this is not the case becuase to reach the 2,500 number we need
to combine multiple resources in the view (except with the one that has
4,000). If we run the view for each one individually they work just fine and
as long as the combination stay under about 2,200 assignments it works.

Does anyone know of a limit on this view? Is there a limit on the Web part
that is displaying the data? Is there a way to change this limit? Memory
limit?

Any help or suggestions are appreciated.

Thanks
Jason

 

[Jack Dahlgren]

Microsoft is not that great about publishing limits so I can't find it on the
web, but I'm pretty sure there is a maximum amount of time allowed for a
single resource. It may be this problem you are running up against. You might
consider breaking down some of your generic resources to a lower level of
detail to avoid the large number of assignments.

Frankly speaking, a view with 4000 assignments in it sounds almost
incomprehensible to me.

-Jack Dahlgren

 

[Jason]

Thanks Jack,

Yes, the view is very overwhelming. What we have done is gone to a system
where each task has only one resource on it so the tasks get very detailed
and numerous. As a result the number of tasks assigned to this particular
generic, an admin position with about 6 people in the pool, is a lot. Going
forward it won't be too bad, just a lot now as we try to bring close to 1,000
projects up online.

We were also thinking about a time out issue of some kind but could not
figure out how to test it and could not find anyone else out there that is
had this same problem. Then again, I don't think many systems have 2,000+
assignments to one resource.

Thanks
Jason

 

[Jack Dahlgren]

What sort of business are you in that you have 1000 projects going at once?
How large are your projects? How many tasks each?

-Jack Dahlgren

 

[Jason]

Consulting, Design and Construction.

Lots of short cycle projects. Task count (with summaries) ranges from 150
on the low side to over 900 on the larger longer jobs. We do a lot of work
in the retail sector so there are lots of locations to work on. What is
driving the task count is the level of detail we are going to, most tasks are
less than 8 hours of work.

 

[Jack Dahlgren]

I am wondering whether Project is the best tool for the job if you have 1000
projects with an average of 500 tasks each and they mostly less than 8 hours.

I avoid creating schedules with tasks less than 8 hours. Maintaining them
and updating them is too expensive for the benefit received.

-Jack Dahlgren

 

[Jason]

Thanks Jack for the help. We have discovered that there is a Hotfix out to
address this problem. KB Article Number(s): 953476

Thanks
Jason