thorn-ecoc Posted June 13, 2017 Share Posted June 13, 2017 Out of nowhere I'm getting "An ID conflict occurred during IO" when I use undo. ............using Version 8 Show Detail tab shows C:\p4sync\dev\Releases\18\chief\CACommon\IDManager\Manageable.cpp(113): Warning #272032333 "An ID conflict occurred during IO. This is potentially serious and could result in data loss." I've tried saving as a different file name, but don't know what else to try to get message to stop. 1 Link to comment Share on other sites More sharing options...
DavidJPotter Posted June 14, 2017 Share Posted June 14, 2017 Saving as is a good way to protect yourself but merely making copies of corrupted files is all that does, it "fixes" nothing. I have not seen such an error message since version 7 or 8 so I doubt any here will know anything useful in terms of specifics. Generally speaking such errors come from poor end user habits based upon a perfunctory actual knowledge of Chief Architect software and its proper use. I am not saying this as a put down at all, but rather merely stating facts based upon helping newer users is what I have specialized in for over twenty years. Knowing what to do is far superior to merely guessing and hoping for a livable outcome. Competence is your only real protection from error messages, when you follow established procedures you rarely see them and when you don't that is almost all one sees. Version 8 is an antique application, it still of course works as it was originally designed to do so but it is still an antique that was designed for an antique operating system and hardware. DJP Link to comment Share on other sites More sharing options...
glennw Posted June 14, 2017 Share Posted June 14, 2017 Your signature says you are using X8, not 8 as per your message. I would contact tech support with a problem like that. Link to comment Share on other sites More sharing options...
Chopsaw Posted June 14, 2017 Share Posted June 14, 2017 Did you shut down and reboot and then try opening the save as file? If that does not work look for a recent auto save file. Link to comment Share on other sites More sharing options...
thorn-ecoc Posted June 15, 2017 Author Share Posted June 15, 2017 Well, the error simply vanished. Kept popping up for about an hour at every undo, then stopped. And yes, I've only been using CA daily for 22 years. I'm sure it is "from poor end user habits based upon a perfunctory actual knowledge of Chief Architect software and its proper use" I did fail to add an X ..I am using version X8. (Been to busy to even install X9) Link to comment Share on other sites More sharing options...
ballaia Posted July 5, 2017 Share Posted July 5, 2017 I just saw the same error for the first time as well. Perhaps there are unkept drawing errors as we're trying to be creative and not trying to build correctly all the time. Did CA help you pinpoint the problem and give solution? We've migrated to X9 and it's dramatically better. Performance is 2x to 3x better in speed and build ease. The only comment I have is that I wished we used it earlier. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now