Project shutting down when linking to a resource pool

Home Forums Discussion Forum Project shutting down when linking to a resource pool

Viewing 2 reply threads
  • Author
    Posts
    • #4986
      Has anyone had a problem with MSP2010 locking up and rebooting when you have linked a project to a resource pool then attempting to save the project file.
      I have a template I created in a prior version of project that I have used for years linking it to a resource pool.
      I first saved both the resource pool and template as 2010. When I opened the template and pool, selected to share resources from my pool then tried to save project locks up and shuts down.
      I then recreated the resource pool and attempted to share resources again with template to only have it reboot again.
      My template is a very involved template and I would prefer to not have to recreate it.
      Has anyone had this kind of problem and if so were you able to resolve it?
    • #6415
      First off, make sure you have installed SP1 and the June Cumulative Update (both free downloads from MSDN).
      Templates shouldn’t be attached to pools as their resources get added to teh pool workload. After saving a copy of teh template PMs should only then connect to teh pool, but preferably only after they have edited the schedule so resource usage matches what your resource managers/management/team leaders tell them what resource availability they can have. This avoids garbage data in!
    • #6828

      I repeat:

      First off, make sure you have installed SP1 and the June Cumulative Update (both free downloads from MSDN).
      Templates shouldn’t be attached to pools as their resources get added to teh pool workload. After saving a copy of teh template PMs should only then connect to teh pool, but preferably only after they have edited the schedule so resource usage matches what your resource managers/management/team leaders tell them what resource availability they can have. This avoids garbage data in!
      Linking to resource pools is inherently risky. Every time anyone renames, moves or over-writes any linked file, the file corruption dice are rolled.
      It is most likely that any problems are file corruptions so unlink all files, save as to new files then create a new, blank resource pool and re-attach project files.
Viewing 2 reply threads
  • You must be logged in to reply to this topic.