Microsoft Knowledge Base Email Alertz

(107508) - When Microsoft Project encounters a circular relationship in a project field, you will receive the following error message Circular relationship in task number and the following message will appear in the status bar of the project: Circular:project...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 107508 - Last Review: September 18, 2011 - Revision: 5.0

PRJ: Circular Relationship Error

This article was previously published under Q107508

On This Page

SYMPTOMS

When Microsoft Project encounters a circular relationship in a project field, you will receive the following error message
Circular relationship in task <number>
and the following message will appear in the status bar of the project:
Circular:<project filename>[task number]
When these error messages appear, Microsoft Project will not calculate the project.

CAUSE

Three situations in which you may receive a circular relationship error message are:
  • When you make a summary task a predecessor or successor to one of its subordinate tasks.

    -or-

  • When you link a series of tasks, such that a predecessor or successor task links back to itself.

    -or-

  • When you create a series of predecessor or successor relationships of summary tasks and subtasks that indirectly points back to itself.

    NOTE: Summary tasks can not have predecessors or successors in Microsoft Project Windows version 1.0 and Microsoft Project for the Macintosh version 1.1

WORKAROUND

To work around these circular reference problems, follow the appropriate procedure below.
  • If you make a summary task a predecessor or successor to one of its subordinate tasks, you must delete the link to resolve the circular reference. A subtask cannot be a successor to its own summary task.

  • If you link a series of tasks, such that a predecessor or successor task links back to itself or if you create a series of predecessor or successor relationships of summary tasks and subtasks that indirectly points back to itself. To resolve the conflict, follow the successor paths of the task referred to in the message. One of the paths will lead back to the task referenced in the message.

MORE INFORMATION

Steps to Reproduce the Problems

To make a summary task a predecessor or successor to one of its subordinate tasks:

  1. From the View menu, choose Task Entry.
  2. From the File menu, choose New.
  3. Enter 10 tasks in the Gantt Chart.
  4. Select tasks 2-6 and choose the demote button to make them subtasks of task ID1.
  5. Select tasks 8-10 and choose the demote button to make them subtasks of task 7.
  6. Select task 1 in the Gantt Chart.
  7. Select the Task Form.
  8. From the Format menu, select Predecessors and Successors.
  9. To make task 2 a successor to task 1: in the Task Form, in the ID column for Successors, type 2 and press the RETURN key twice.
This will generate the error message
Circular relationship in task 2.
To resolve this conflict, delete the link. A subtask cannot be a successor to its own summary task.

To link a series of tasks such that a predecessor or successor task links back to itself:

  1. Select the Name column in the Gantt Chart. This will highlight all the tasks in the Gantt chart.
  2. On the toolbar, click the Unlink button.
  3. Select tasks 2-5 and click the Link button on the toolbar.
  4. Select task 5 in the Gantt Chart.
  5. Select the Task Form.
  6. In the Task Form, type in 2 in the Id column for Successors and press RETURN twice. This makes task 2 a successor to task 5.
This will generate the error
Circular relationship in task 3.
To resolve the conflict, follow the successor paths of the task referred to in the message. One of the paths will lead back to the task referenced in the message.

To create a series of predecessor or successor relationships of summary tasks and subtasks that indirectly points back to itself:

  1. Select the field title, Name, in the Gantt Chart. This will highlight all the tasks in the Gantt Chart.
  2. From the Tool bar, click the Unlink icon.
  3. Highlight Task ID 8 in the Gantt Chart.
  4. Select the Task Form.
  5. In the Task Form, type in 3 in the Id column for Successors and press return twice. This makes Task ID 3 a successor to Task ID 8.
  6. Highlight Task ID 1 in the Gantt Chart.
  7. Select the Task Form.
  8. In the Task Form, type in 7 in the Id column for Successors and press return twice. This makes Task ID 7 a successor to Task ID 1.
This will generate the error
Circular relationship in task 1.
To resolve this conflict, follow the successor paths of the task referred to in the message. One of the paths will lead back to the task referenced in the message. If the path does not lead back to the referenced task, check the summary tasks for predecessors or successors for possible conflict such as a subtask in the successor summary is pointing back to a subtask in the predecessor summary.

APPLIES TO
  • Microsoft Project 2000 Standard Edition
  • Microsoft Project 1.0 Standard Edition
  • Microsoft Project 3.0 Standard Edition
  • Microsoft Project 4.0 Standard Edition
  • Microsoft Project 3.0 for Macintosh
  • Microsoft Project 98 Standard Edition
Keywords: 
kberrmsg kbprb kbusage KB107508
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Mitch Mueller - Mitch.Mueller NOSPAM-AT-NOSPAM LMCO.Com Report As Irrelevant  
Written: 2/24/2006 10:41 AM
When using MSProject2002 with a Master Project, the tool does not appear to display the task number of the task causing the problem. I see no trivial way to identify the tasks involved with the loop as they are looped across subprojects. The only solution is to delete links, and then slowly add them back to detect the loop.

Anonymous User Report As Irrelevant  
Written: 2/23/2007 1:39 AM
But this should state how to detect the circular link. We all know what it means, but how do you discover the rouge link in a big project (> 2000 tasks with multiple sub-projects)?