Bim 360 Failed To Open Document

[Renita Lukins]

Was the project was Workshared? ( i.e. Worksets enabled, a Central File on the Server and Local copies saved on the C: drive. -Find the computer that you last worked on, and find the last local copy on the C: drive, and see if you can open it.

When I tried to open the backup versions of the file which are saved as a slightly different name as I changed the file name at some point today it isn't showing the "failed to open document" but instead is saying the location name of file then "file not found Please verify the correct name was given" do you think this could have something to do with the file corrupting?

-Make sure you know and understand the difference between a Workset enabled/Central File/Local copy Revit project, and a single-user/standalone Revit project. This is critical for learning how to work in teams in Revit.

Thanks @walt.farrell, the issue of course is that things like this make Publisher 2.0 almost unusable, you spend hours, days, weeks creating a Publisher Document and all of a sudden you are locked out of it with zero way to retrieve your work...

This is exactly what I am facing, and it gives me the same error on Windows, Mac and iPad OS. I am crippled by this. I tried to revert back to V1 and of course that didn't work either (which I guess should be expected).

I have tested this issue with several different cloud drives too. Once problems began with a file, however, it made no difference if I transferred it to my iPad manually or not. I hope my .apub files are not damaged.

I have just had this problem occurs on the latest version 2.0.4. I'm locked out of a file with the same error message. I'm using a windows machine and the file was stored on our local server now it is on my local drive.

I have solved this problem on my computer. I had the same exact problem as all of those above. I observed that when I double-clicked my Affinity Publisher files and got the "failed to open" alert, if I went to the "Affinity Publisher" menu and chose "About," it said I was running v.1.XXX of Affinity Publisher. That is interesting because I do not have that version on my active Big Sur boot partition, only V.2.04, with which I created the files being opened only hours before the dreaded "failed to open" alert. If I quit the v.1 it said was open, and opened V.2 directly, then File>open my files, they opened right up. Then I did "get info" on the files themselves and changed the "Open with" box to Affinity Publisher 2 (Affinity Publisher (1) was already the default) and chose "Change all". That solved my problem across all of my files.

Afterwards, I searched for a copy of V. 1 and found it on a different partition that serves as a Mojave dual boot. Somehow, my file (on the active Big Sur partition) created only hours before by V. 2.04 on that partition, when launched from finder, opened V.1 on an inactive and different partition. Weird!

Having your documents associated with the wrong version can happen even without separate partitions - I've had it happen with afdesign files multiple times. I just want to point out that this thread is about a bug in Publisher where it shows the 'later version' error even though the document was saved from v2.0.4.

I am experiencing this problem today with Affinity Designer 2, a file that was working fine at the beginning of the week (opening and closing no issues) and yet today when I open it I get the failed to open error message 'The file includes features from a later version of Affinity'.

If you're in a rush and can't wait for a reply from Serif, you might consider installing the 2.1 beta and trying to open it with that. Or consider uploading the file here so one of us can try it in the beta.

There were two linked resources within the file which I was unaware of but these were picked up and located, not sure if that was causing the issue in 2.0.4 because other files used and created during the same time open fine, one of the files also has a linked resource stored in the same way. The file and resources are both stored within OneDrive.

I have also downloaded the beta version as recommended by someone else and - yes it opened my file! BUT it won't let me export it and crashes every time I try so I don't trust that either to look after my work and allow me to do what I need to. This isn't helpful at all and I was really enjoying using Affinity Publisher 2...

Failed to open file [C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\iDataAgent\FileSystemAgent\2\6344\SysStateColInc.cvf] for output. Check that the file is not in use by another program. The open attempt returned error [The operation completed successfully. (ERROR_SUCCESS.0), First attempt to delete failed, checking attributes for retry attempt, File=[\\?\C:\Program Files\Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\iDataAgent\FileSystemAgent\2\6344\SysStateColInc.cvf], AccessedBy=[C:\Program Files\Commvault\ContentStore\Base\CLBackup.exe (69372)] (W32.0)].

So it looks like the scan process is attempting to access the Job Results at the same time the client backup process is. Are there multiple backups running on this machine at the same time? Is there a clbackup process still running if you shut down the commvault services on the client? If there is a hung process then that would cause this issue.

My indesign acts a bit weird with some pdf files. If I want to insert a pdf file I get following error: "failed to open the pdf file". It works on another computer so I really don't know what the problem could be. This is what I've already tried:

Try opening the PDF files in Acrobat and ascertain that there is no protections applied to the PDF file. Look under Document Properties => Security. If there are any restrictions, you will likely have problems placing the PDF into an InDesign documents. You would need to remove such protections.

I got the same failue message. And i cannot use Shotcut anymore, i.e. I cannot start it, being newly intalled without any project.

I think it is caused by the before done update to the most recent macOS. Any idea?

I was able to open the mlt file with notepad++. I made a copy and changed a few of the resource files to just the file name rather than the path.

From this:

To this:

When I did this shotcut prompted me to find the files. I directed shotcut to the files successfully (green check marks) but then I got the same failed to open error message.

Good find! I have seen a problem like this years ago with metadata embedded in the media files, and there was a fix for it. In this case, this is bad text data is coming from the text box in the Properties panel of Shotcut. I will have to add some filtering there now to prevent this problem. Instead of deleting the whole ... block, you could have simply deleted the lines with the offending characters. Thank you for finding it and reporting it.

Hmm, that worries me. Did you view the log or open these .mlt files to look for a similar problem? I will review all the changes from 18.08.01 to 18.08.11 to see if there is a possible reason, but it will be easier to find steps to reproduce.

Hey yall, I am trying to open up my ArcPro project but it says that is has "Failed to open Project" I read elsewhere that going through your files and opening up the MXD file there solves this problem, this was for 2.1.2 -pro-questions/arcgis-pro-2-1-2-fail-to-open-project-error/td-p/... - but instead I get -

I have checked my updates and it says that it is the current version, I have even closed the app and reopened it, along as restarting my computer. I have not found anyone else with this problem as of recent. Hoping someone can please please please PLEASE help.

The error message is inaccurate in this case. Although there is no documented solution (from Esri) for this particular issue yet, a few workarounds attempted by people are given below (Please take backup before proceeding).

Before this error I was getting the error "REL/Relocation.h(548): failed to open file" but I uninstalled and reinstalled the engine fixes and SKSE libraries. After doing that and relaunching I get the error I mentioned above. Do you guys know what I could have done wrong? I'm really new to messing with mods so it's probably something I did wrong... I've made sure all plugins are enabled and all mods are installed with their masters except for the ones below because I can't find the appropriate mod that goes with it so maybe that could also be the issue. I'm pretty sure I have "Blues Skyrim" but the creator renamed it so that's why MO2 is detecting it as missing. Idk if that's the case with the other ones though.

3a8082e126