Master Project Issues

[R23]

All,
I inserted all projects into one master project (70,000+ tasks). I saved
and published the master. All progressed smoothly up until it was about 2/3
of the way complete and stopped. Then the archive process started to
complicate matters. There were 2 jobs being queued that I canceled this
morning. I tried to republish the master and received no response from the
server – nothing in the queue. It was as if I never selected File/Publish.
I restarted the event and queue services with no change. I then deleted all
the archived projects and rebooted the server again with no change. I am now
in the process of updating the external links in the subprojects (did not do
this previously). I will then try to save and publish the master again. Net
Net: when I perform a File-Save-File-Publish, the system does not even show
the percent complete. HELP!!!!

 

[Mark Everett | PMP]

All,
I inserted all projects into one master project (70,000+ tasks).  I saved
and published the master.  All progressed smoothly up until it was about2/3
of the way complete and stopped.  Then the archive process started to
complicate matters.  There were 2 jobs being queued that I canceled this
morning.  I tried to republish the master and received no response from the
server – nothing in the queue.  It was as if I never selected File/Publish.  
I restarted the event and queue services with no change.  I then deletedall
the archived projects and rebooted the server again with no change.  I am now
in the process of updating the external links in the subprojects (did not do
this previously).  I will then try to save and publish the master again. Net
Net: when I perform a File-Save-File-Publish, the system does not even show
the percent complete.  HELP!!!!

Just curious, but how many project make up the Master Project? Also,
what is the business reason to roll all the projects up in a project
schedule? If it's to collect high level status, I think a Hammock
would work better and would certainly have fewer tasks.

Best Regards,
Mark Everett
www.catapultsystems.com