A circular reference exists - Error

[binaryboyz]

When a file is created with Project 2007 and the file is saved down to the
2003 file format there is an issue with the file becoming corrupted no matter
which version of the application opens the file and saves the changes.

The following issues occur:
- Upon opening the file the error "A circular reference exists"
- After opening the file tasks the missing (blank spaces) or the sequence of
the tasks has been changed.

Thanks

 

[JulieS]

Hello binaryboyz,

I cannot reproduce what you report. I suggest double checking the
service packs installed to both Project 2007 and Project 2003.
Project 2007 is up to SP-1 as well as an Infrastructure Update
released in July 2008.

The circular reference needs to be resolved in your project file.
Check for links on summary tasks.

Does the problem occur only with one file or all files?

I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional
information about Microsoft Project

 

[binaryboyz]

Hi JulieS,

This problem occur with all files. Updates are okay. Is there any important
update that I need to check.
I found one KB article: http://support.microsoft.com/kb/169729, i did not
try but i dont know whether it is useful or not.


binaryboyz

 

[JulieS]

Hi,

So, you have both SP-1 and the Infrastructure Update installed to
Project 2007? Again, I cannot reproduce and as it occurs with all
files, I have to assume there is something amiss with the
installation. Although I hate to recommend a re-install, if you are
confident that the installations are up to date, I suggest trying an
uninstall and reinstall. Perhaps if you could try a fresh install
on a test machine and try to reproduce the error that might help.

Julie

 

[binaryboyz]

Hi JulieS,

The behavior of MS Project 2007 is not consistent.

1. If the file is saved in 2003 format (default), it creates the
problem of circular reference. Tasks disappear and get jumbled up. This
happens only if you have MS Project 2007. If it is 2003, nothing happens.

2. If the file is saved in 2007 version, it gets jumbled up when
someone with 2003 opens it. But this again is not consistent and happens only
under certain conditions which we have not been able to identify.


Thanks,
binaryboyz

 

[JulieS]

Are you up to date on the service pack and infrastructure update for
Project 2007?

Julie

 

[binaryboyz]

Hi JulieS,

Service pack is okay, how do I check Infrastructure update for Project 2007?


Thanks,
binaryboyz

 

[JulieS]

See http://support.microsoft.com/kb/951547

At the bottom of the article is information on release and date for
several files if the IU is applied.

Julie

 

[gumnaam]

Hi JulieS,

The behavior of MS Project 2007 is not consistent.

1. If the file is saved in 2003 format (default), it creates the
problem of circular reference. Tasks disappear and get jumbled up.
This
happens only if you have MS Project 2007. If it is 2003, nothing
happens.

2. If the file is saved in 2007 version, it gets jumbled up when
someone with 2003 opens it. But this again is not consistent and
happens only
under certain conditions which we have not been able to identify.


Thanks,
binaryboyz

I have the exact same issue and you have best identified it. I don't
have any solutions yet? I have noticed that it happens only after I
change linkages.

Any ideas?

 

[JulieS]

"gumnaam" wrote in message news:[email protected]...

I have the exact same issue and you have best identified it. I
don't
have any solutions yet? I have noticed that it happens only after
I
change linkages.

Any ideas?

Gumnaam,

Do you have SP-1 and the Infrastructure update installed? Circular
references are usually created when there are links on summary
tasks. Do you have summary task links?

Julie

 

[Dean C]

What you are describing is a perfect example of a corrupt file. Prior Project
2007 sp2, Project 2003 files opened and saved in Project 2007 had an expected
life of about a month before they became corrupt. Service Pack 2 is supposed
to resolve this problem. You may have an excellent file to test whether sp2
does what it is supposed to do. Before you install sp2, if you have archived
a copy of the file you are now using that is corrupted, open the 2003 file in
2007 save, close and reopen about thirty times. I anticipate that at some
time during those thirty tries, you will start seeing a circular relationship
that doesn't exist, or you will get a file not found error: both indicating
corruption. If you are successful in re-corrupting your file, install sp2 and
repeat the test. If you can't corrupt the file, then sp2 solved your problem.
If not copy your UID to a text field, click the upper left corner to select
all, open a new file which will be of Project 2007 origin and paste, resolve
any issues associated with the change in UID and never reopen this file in
Project 2007 after it has been saved using Project 2003. At least once a
week, immediately after opening any Project file, click the save button to
debloat it and avoid a different source for corruption.

Let us know if you test.

 

[the1kaz]

What you are describing is a perfect example of a corrupt file. Prior Project
2007 sp2, Project 2003 files opened and saved in Project 2007 had an expected
life of about a month before they became corrupt. Service Pack 2 is supposed
to resolve this problem. You may have an excellent file to test whether sp2
does what it is supposed to do. Before you install sp2, if you have archived
a copy of the file you are now using that is corrupted, open the 2003 file in
2007 save, close and reopen about thirty times. I anticipate that at some
time during those thirty tries, you will start seeing a circular relationship
that doesn't exist, or you will get a file not found error: both indicating
corruption. If you are successful in re-corrupting your file, install sp2 and
repeat the test. If you can't corrupt the file, then sp2 solved your problem.
If not copy your UID to a text field, click the upper left corner to select
all, open a new file which will be of Project 2007 origin and paste, resolve
any issues associated with the change in UID and never reopen this file in
Project 2007 after it has been saved using Project 2003. At least once a
week, immediately after opening any Project file, click the save button to
debloat it and avoid a different source for corruption.

Let us know if you test.

 

[the1kaz]

This problem is exactly what I have been experiencing. I won't save my 2007
files as 2003 again, but I would like to recover one fairly large file that
has been corrupted. I didn't understand your suggestion. What is a UID?
Where do I find it to copy it?

Thanks