Project Risk Analysis Software and Project Risk Management Software Forum

We’re evaluating RiskyProject and have run into an issue with the MSP add in. After installing RiskyProject, Microsoft Project’s scheduling engine appears to stop working correctly. All dependencies are ignored and tasks become locked to the project start date.

After some testing, I found that each time you press Run in RiskyProject, MSP automatically turns off Auto Calculate. This prevents the risked schedule from opening properly in MSP.

“Each time you press run it turns off auto calculate in MSP.” “Dependencies have been disregarded and all tasks are locked to the project start.”
Is this expected behavior? Is there something I may be missing in the setup? Also, is it possible to toggle to the Lite version?

Thanks

Thanks for the detailed description. We tested this on our machines and did not see the same behavior, but it may be related to differences in MSP versions or environment configuration.

Based on information available from Microsoft’s forums, MSP may automatically disable auto calculation when an add in modifies tasks, resources, or fields. This is done to prevent the scheduling engine from entering an unstable state.

Here is the relevant explanation:

“MSP’s scheduling engine recalculates dependencies, constraints, resource leveling, and calendars. If an add in modifies tasks, resources, or fields, MSP may attempt to recalc mid operation, causing re entrant COM calls, inconsistent state, corrupted undo stacks, or deadlocks in the scheduling engine. To avoid this, MSP switches to Manual mode while the add in runs.”
RiskyProject interacts with MSP’s task data during simulation, so MSP may switch to Manual mode as a protective measure. After the add in completes, you may need to manually re enable Auto Calculate in MSP.