Error Opening InDesign File After Transferring from Server to Local Machine

[Christopher3440329747o5]

I do not know why I am getting this message. I have never seen this before in all the years I've been using Adobe apps.

I had some files on my server. I copied them to a transfer drive. I then copied them to my production machine. I do not have my server mounted to my production machine. 

I open a InDesign file and this is what I get.

I am current on all apps and OS.

 TIA

<Title renamed by MOD>

[Christopher3440329747o5]

Oh now I also got this message.

 

[Robert at ID-Tasker]

What is the size of the file - in kB / MB? 

[Christopher3440329747o5]

200mb

[Robert at ID-Tasker]

Have you unmounted / ejected your transfer drive from OS or just disconnected the cable? 

[Christopher3440329747o5]

I have tried everything to get it to work. All the normal trouble shooting.

[Robert at ID-Tasker]

No. I mean when you copied from server to your transport drive - have you just disconnected the cable - or selected appropriate option from the OS to flush the cache first? 

[Christopher3440329747o5]

I didn't flush the cache but yes I disconnected. 

No one but me has access to these files. The files were given to me but there is no hidden files in the folder or the temp file InDesign makes when you open a doc. 

I do not know how to flush the cache. I was going to reinstall InDesign as a last option.

[Robert at ID-Tasker]

There is no point reinstalling InDesign. 

Most likely - you've disconnected the cable to soon - and copy of your file is incomplete / corrupted. 

Please confirm platform and OS version. 

[Christopher3440329747o5]

The file isn't Incomplete. The file opens just with those errors. I click ok on the dialog box and the same messages keep opening. I am current on the OS and InDesign like my initial post says. 

[Robert at ID-Tasker]

You never said if it's PC or Mac... 

[Christopher3440329747o5]

It's a Mac - doesn't my screen shot give it away?

[Christopher3440329747o5]

Oh what do you f@ckin know. I went down to 19.3 and NO ERROR! Wow Adobe sucks!

[leo.r]

Oh what do you f@ckin know. I went down to 19.3 and NO ERROR! Wow Adobe sucks!

By @Christopher3440329747o5

Yes, the errors you experience look like a problem that was introduced on either 19.4 or 19.5. (Or was allegedly fixed in 19.5?) Frankly, I lost track of the exact history of this particular set of errors, but it's been discussed on the forum quite a few times. I don't have the exact links right now, but try to search the forum for these errors; you may find more info.