We are having InCopy stories that generate errors that I cannot find much information about online. This happens in CS4 and CS5 documents. We have no documents that originated in CS5.5 so I don't know if InCopy CS5.5 will CAUSE the issue, but I know that CS5 files opened in CS 5.5 have seen this issue manifest. Files that are functioning normally at check-in will just open next time with one of these two errors. No crash or strange behavior before suddenly the error appears. We can have dozens of stories in a document (or hundreds) and one will corrupt in this manner. An hour, a day, a week, maybe a month later, another file will die. There seems to be no discrenable pattern.
The errors are "Not Well Formed" and "Junk After Document Element." I can open the .icml files in a text editor and find and (usually) fix the problem, but wonder how the files are corrupting? The "junk after document element" files will have a complete duplicate of the content of the file starting immediatley following the </document> tag. It is as though instead of writing just the changes to the file when checked in, InCopy appends a whole new document, beginning with the <?xml version="1.0" encoding="UTF-8" standalone="yes"?> tag.
The "not well formed" files appear almost the same, but instead of the document starting over after the </document> tag, it will have a copy of itself inserted willy-nilly in the middle of the file. This one is much harder to fix…
Has anyone else seen anything like this?
Primarily CS5
Mac OS 10.6.8
Files stored AFP on Windows Servers with ExtremeZ/IP