No calculations can be performed error

[AlexM]

Hello all,

I have a project that is gives the following error when being opened:

'No calculations can be performed now.

There is a circular relationship in task 136 End of Quarter if
"FY09_Q1_CENTRAL.Published". The successors of this task refer back to
this task or its predecessors, causing a circular reference.

To remove the link that is causing the circular reference, select the
two tasks that are cauasing the circular link, and then click Unlink
Tasks on the Standard toolbad.'

After clicking OK to this error the task gantt chart opens with none
of the tasks showing. This prevents managers from managing any of the
tasks in the project. However when looking at resource view of
assignments I can see all the tasks, or even viewing the project on
Project Web Access.

The task the error is referring to is the last task in the project,
and is unassigned. It is not linked to any other tasks nor are any
other tasks linked to it.

Any ideas on this situation?


-Alex M.

 

[Paul Conroy]

If it's a member of a master project, disassociate this relationship. Try and
republish

If that doesn't work or is not the case, save the plan out to an XML file,
delete the project from project server and then re-import from the xml file.

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com

 

[Dale Howard [MVP]]

AlexM --

I can tell you that much of the time, circular reference errors are caused
by setting task dependencies on summary tasks. And I can also tell you that
much of the time, the error message that Microsoft Project gives you is
totally bogus, failing to point out the real culprit that is causing the
circular reference error. To determine if a task dependency on a summary
task is causing the error, you might try the following:

1. Display the Gantt Chart view with the Entry table applied.
2. Pull the split bar to the far right so you can see the Resource Names
column.
3. Right-click on the Resource Names column header and click the Insert
Column item on the shortcut menu.
4. In the Column Definition dialog, select the Successors column and then
click the OK button.
5. On the Formatting toolbar, click the Filter pick list and select the
Summary Tasks filter.
6. Examine the Predecessors and Successors column for task dependencies,
and remove them from each summary task.

When you remove the task dependency that is causing the circular reference
error, Microsoft Project will recalculate the project successfully without
error. At this point, you will probably have to determine how to reset task
dependencies in the project so that you don't set dependencies on summary
tasks. Just an additional thought. Hope this helps.

 

[AlexM]

AlexM --

I can tell you that much of the time, circular reference errors are caused
by setting task dependencies on summary tasks.  And I can also tell you that
much of the time, the error message that Microsoft Project gives you is
totally bogus, failing to point out the real culprit that is causing the
circular reference error.  To determine if a task dependency on a summary
task is causing the error, you might try the following:

1.  Display the Gantt Chart view with the Entry table applied.
2.  Pull the split bar to the far right so you can see the Resource Names
column.
3.  Right-click on the Resource Names column header and click the Insert
Column item on the shortcut menu.
4.  In the Column Definition dialog, select the Successors column and then
click the OK button.
5.  On the Formatting toolbar, click the Filter pick list and select the
Summary Tasks filter.
6.  Examine the Predecessors and Successors column for task dependencies,
and remove them from each summary task.

When you remove the task dependency that is causing the circular reference
error, Microsoft Project will recalculate the project successfully without
error.  At this point, you will probably have to determine how to reset task
dependencies in the project so that you don't set dependencies on summary
tasks.  Just an additional thought.  Hope this helps.
















- Show quoted text -

Thanks guys, I will have my users try out your suggestions and report
back here with an update.

 

[Gary L. Chefetz [MVP]]

Alex:

Before trying to open this plan, set calculation to manual in the Project
Client from Tools > Options > Calculation tab.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

AlexM --

I can tell you that much of the time, circular reference errors are caused
by setting task dependencies on summary tasks. And I can also tell you
that
much of the time, the error message that Microsoft Project gives you is
totally bogus, failing to point out the real culprit that is causing the
circular reference error. To determine if a task dependency on a summary
task is causing the error, you might try the following:

1. Display the Gantt Chart view with the Entry table applied.
2. Pull the split bar to the far right so you can see the Resource Names
column.
3. Right-click on the Resource Names column header and click the Insert
Column item on the shortcut menu.
4. In the Column Definition dialog, select the Successors column and then
click the OK button.
5. On the Formatting toolbar, click the Filter pick list and select the
Summary Tasks filter.
6. Examine the Predecessors and Successors column for task dependencies,
and remove them from each summary task.

When you remove the task dependency that is causing the circular reference
error, Microsoft Project will recalculate the project successfully without
error. At this point, you will probably have to determine how to reset
task
dependencies in the project so that you don't set dependencies on summary
tasks. Just an additional thought. Hope this helps.
















- Show quoted text -

Thanks guys, I will have my users try out your suggestions and report
back here with an update.