1 person found this helpful
i get the same issues.
for the second error, i have to have another person that can open the file make me a legacy file, than it opens fine.
We get file stream via out company IT, and i have opened tickets about this. they also point to indesign as the source of the issue.
Well, I don't represent Adobe, and wouldn't broach all the technical details involved, but in simple terms:
In order to continue functioning properly, InDesign has, and needs to maintain, a particular "relationship" with a given open file. Opening files across a local network has often been found to threaten that relationship in various ways, so it stands to reason that opening files across an Internet connection (a considerably more fragile connection than a LAN) would also pose various file-integrity threats.
Even with the stoutest connection possible, Google File Stream is far too young for anyone to presume that every application they run should run well with it as the file source.
I strongly suspect the current solution to your problem will be to stop trying to work across your File Stream connection.
Just strange that our global team has been working this way for a few months now. This issue only became a problem as of last week. Before then, working fine with no issues.
. . . our global team has been working this way for a few months now. This issue only became a problem as of last week. Before then, working fine with no issues.
I can't say whether anyone from Adobe will see this thread and get involved, but if they do, that could be an important fact for them to consider. Any other facts and details you can post might help too.