I’d be interested in taking a look at your file to confirm that this was the case for you. This can result in truncated documents that are corrupted. Unfortunately, we have seen occasional instances where last data InDesign has asked the OS file system to write out to disk before the network connection is lost never actually gets written out. Under most circumstances, this is exactly what happens and the work is saved. In this situation, the expectation is that a subsequent recovery will get you back to a recent version of your document. When this happens, because InDesign has lost access to the document, it will shut down in an attempt to maintain the integrity of the document. I suspect the network connection dropped out on you while you were editing the document. If you'd like a copy of the INX file, please send your email address to me at and I'll reply with the INX file as an attachment. I recommend running some disk utilities on your harddisk as a precaution.Īlthough I believe you have already recovered the file, I was also able to recover it by tweaking things in my development environment and then exporting the file to INX. Occasionally, this problem can be caused by a bad file transfer or a bug in file backup software. Typically, this is a bad sector on your harddisk, but it could also be a faulty thumbdrive. Some of your data failed this test, which indicates that there was faulty media somewhere in your workflow.

When InDesign later reads that same data from the disk, it verifies that the data is good by recalculating the checksum and confirming that we get the same number. Instead, it was caused outside of InDesign, probably by faulty hardware.Įvery time InDesign writes data to the hard disk, we calculate and record a checksum for that data. After further investigation, I can now conclude that your corruption was actually not caused by the Save As bug.

Pdf2id 4.5 forum