If you only use the Resource Pool for reporting, then consider recording a macro to create a new Consolidated schedule each week by inserting all projects with teh Link option OFF. Then re-link all projects to it (once they too are in 2010 format). At the least I would disconnect all projects from the resource pool, then create a new, blank, pool file in Project 2010 format Personally I would swap to a solution that eliminates those links altogether, but then I can use VBA, databases etc to do this. 1000 ModStamp:4b8e2648ġ30 schedules with many interconnecting tasks and a resource pool is one massive amount of DLE links that as you're aware causes a lot of corruption. Here are the first three line of the errorĪppName: winproj.exe AppVer. All MPPs and resource poolĪnd just to add a bonus problem :-) I had msproject (blank) opened up to see the exact version and SP information - so I could write in this question - and it crashed :-) this time no files were open. On a given day - 40-60 project plans are updated (by 5 different PMs).
We have about 130-140 project plans (on average each project plan has 40-50 tasks)- with 20% of them having interdependency with other projcets. Then opened up all sharer files one by one and 'save as' 2010 (default format) - Actually wrote 1000 (32-bit)įor migrating from 2007 to 2010 - I first saved the resource pool (by opening the 2007 version in 2010 and 'save as' default 2010 format.
#Pool corruption in file area reddit professional
We are using MS Project 2010 Professional Edition version. In some instances external predecessors appeared where they were not even supposed to be (and yes IĬhecked it wasn't a typo by one of our PMs - there were multiple instances and with different PMs) - What's happening? Please help.!!!!
My question is - Are we doing something wrong? or is there an issue with 2010?Ģ. Unrelevant or wrong predecessors appearing in project plans - Recently we identified wrong external predecessors appearing in project tasks. Problem was with the plan and we quickly took care of it by restoring Just today resource pool and one of the project plan crashed thrice. However since our move to 2010, resource pool corruption is like a fortnightly event (if not weekly) - Although we have been efficient in terms of addressing this issue (frequent backup and restore, or identifing a bloatedįile that's causign the corruption and replacing with a most recent backup) - but this is really troubling. Resource Pool Corruption - the frequency of file bloating, resource pool corruption is almost quadrupled since we migrated to MSP 2010 - I am used to resource pool corrupting once in 2-3 months and used to regenerate it and take up all precautionary measuresĪs identifed on mvps website. We are facing some strange issues with MSP 2010 since we migrated from MSP 2007 to MSP 2010.