URGENT: can't open a file from yesterday

[ewindels]

Windows 7, Finale 25.4

When i try to open this file, which I created yesterday (by giving an existing file a new name), I get the following messages:

Error opening file "Cello Sonata I New Template v8.musx": -55
Cannot delete folder "C:\Users\Ed\AppData\Local\Temp\FIN939C.tmp\presets"

I'm loathe to have to recall and recreate yesterday's developments on this document. Any suggestions appreciated.

[BuonTempi]

1. Are other files unaffected?
2. What happens if you try to delete the folder it can't delete?

(You've got a backup, so you can delete anything, right?)

[motet]

In Preferences, pick a different temp folder, preferably one you create just for this purpose.

[ewindels]

1. Are other files unaffected?
2. What happens if you try to delete the folder it can't delete?

(You've got a backup, so you can delete anything, right?)

Buontempi, I don't believe any other files are affected. I don't think I have a backup on this: I went in to the backup folder for Finale in my C drive, but I also can't open the document from there.

[ewindels]

In Preferences, pick a different temp folder, preferably one you create just for this purpose.

Motet, where should the new temp folder be located? If this is occurring by default via the program, I'm not sure where is safer to locate it.

[motet]

Make a folder My Documents\FinaleTemp or something like that. Nothing unsafe about it.

[ewindels]

In the meantime, is that document unsalvageable?

[motet]

You won't know until you try that very simple change.

[N Grossingink]

In the meantime, is that document unsalvageable?

If you can locate this temp file, try to open it. If it opens, do a "save as". This worked for me once, but I'm on a Mac so things are likely different in your case. You could also try shutting down the computer and restarting, then trying to open your original file or the temp.

N.

[motet]

My impression is that the file has been saved, but now it can't be opened; that's what my advice is based on.

[zuill]

I would call this file a loss and would create a new and unique folder for temp files. Do not share this file with any other version of Finale on the same machine. Have a separate folder for temp files from each version of finale. Make sure Preferences points to this unique folder. And, clean it out often. Finale leaves temp files after most sessions. A later session might try to access a temp file from an earlier version, and this confuses finale. There's enough bloat in the program that one should avoid all possibility of instability. This is one step. Don't delete the Crash Reports folder. This might be needed in reporting any crash issues to MakeMusic.

Zuill

[ewindels]

Thanks, guys. I have reported the issue to Makemusic. Apparently it's a known problem specific to Windows 7, several other people have had the same thing happen.

[zuill]

I've never has this problem. I have several versions of Finale installed on Windows 7, on 2 different computers. Using the temp folder solution for many years, I hope to never have this problem. Finale has had a longstanding problem with temp files and I intend to keep Finale at bay in the best way possible.

Zuill

[motet]

Cannot delete folder "C:\Users\Ed\AppData\Local\Temp\FIN939C.tmp\presets"

I find that folder (or is it a file?) name interesting. I've never seen Finale create a folder inside the temp directory--only files (with the exception of those crash reports). FIN939C.tmp appears to be a folder, and if the error message is to be believed, presets is a folder within the folder.

The AppData stuff has different file ownership and permissions from a folder you create yourself. Perhaps rare or unusual circumstances call for the need for a sub-folder in the temp folder and Finale is running afoul of the baroque Windows file permissions either when creating or deleting such a folder in that system directory. It would be interesting to know if the folder in ewindels's error message actually exists when the error message occurs.

[ewindels]

Motet, that folder does not exist. Interesting, although this is way over my head in terms of Windows' labyrinthine process.

[ewindels]

Well, folks, I re-input the changes from yesterday in the last iteration of the document, saved it to a new location with the new backup and temp folders created... and I'm getting the same problem. The new document won't open. Exact same error messages. Which suggests to me that the v7 iteration is corrupt... but there are significant developments between that and the v6 document. Or maybe it's now the whole series. Any suggestions? Start from complete scratch? This would involve weeks of work.

[motet]

Sorry to hear that. Certainly report it to MM, but if you want to attach your file here we can see of someone else can open it.

[ewindels]

Motet, hear you go. Fingers crossed. Otherwise I've got three sleepless nights ahead of me. But appreciate the offer.

[motet]

Oops--no attachment. Once you've browsed, you need to click "Add the file."

[ewindels]

I'm just realizing the file never attached because it's too big. I'm loathe to add it to my dropbox account if it's corrupted, and i'm not aware if there's another method of attaching oversize files.

As it is, I've spent the last three nights recreating it and the other problem document from scratch, so it's kind of a moot point. MM has still provided no solution, other than three days after the fact to send me a roll back on the update. I give up.

[Ralph L Bowers Jr]

Maybe it's covered under this release by MM today?


"Problem Opening Finale Files Saved in Version 25.4

July 7, 2017 | by Michael Johnson


Problem Opening Finale Files We’ve received a few reports of a very isolated problem that is new to Finale v25.4. Certain files, that have been previously saved in Finale v25.4, cannot subsequently be re-opened. We want to make you aware of this issue, clarify the scope of the problem, and tell you how you can avoid it.

Details

The problem only occurs in Finale v25.4 and requires the use of an external file. Typically this is a percussion map, although an embedded graphic, an audio file, or other file types could also be part of the equation.

For the problem to occur, the file names of these external files must contain one or more of a few special characters, including the ampersand, angle brackets, apostrophe, and quotes.

The problem can be completely avoided by not using “&, “, ‘, <, and >” characters in these file names. For example, we recommend naming your percussion map “Brushes and Mallets” instead of “Brushes & Mallets.”

When the problem does occur, the file will appear to save properly but will produce one or more error messages when you try to reopen it (and it will not open). Specific error messages are listed in this related knowledge base article.

What Do I Do?

You can completely avoid the problem by not using the characters listed above in your file names.

If you do encounter this problem, please submit a case here and attach your file. We can repair the file for you, so it can be reopened, and we can help those who prefer to roll back to v25.3 until a fix has been released to the public.

Working on a solution is our top priority. We hope to share it soon.

Should I Not Update to v25.4?

If you don’t use the above-mentioned characters in your file names, you will not encounter the problem. Because v25.4 solves issues that impact more users, it will remain available while we finalize a solution.

In the meantime, thank you for your patience. If you have additional questions, please let us know via the case system."

[ewindels]

Hi Ralph,

Per my earlier post, to the best of my knowledge, my file had none of these elements or components in them. I've pointed that out to Make Music, who have declined to respond. They sent me a "fixed" file which also didn't open, with the same error messages.

They say they're offering a rollback to 25.3 but I have not found anyone yet who's gotten that. They didn't offer it to me. And I'm way too behind on my work schedule to risk anything further with 25.

[motet]

They sent me a "fixed" file which also didn't open, with the same error messages.

Presumably they tried it, so that would suggest a problem with your set-up (not that you're to blame!).

[ewindels]

Quite possibly, motet. But short of one of them flying out here and doing a diagnostic on my computer, I don't know what to do. Let me also strongly point out that I was not the only one affected by this.

And I'm worn out by the issue. 25 and any future updates are a done issue for me. Whatever it's shortcomings, 2014.5 didn't corrupt my documents.

[BuonTempi]

don't think I have a backup on this: I went in to the backup folder for Finale in my C drive, but I also can't open the document from there.

And I'm worn out by the issue. 25 and any future updates are a done issue for me. Whatever it's shortcomings, 2014.5 didn't corrupt my documents.

Admittedly, this is a serious and concerning bug. However, rather than shunning all future versions of Finale, your reaction should really be to get a full backup system in place. Not Finale's so-called "backup", which just makes another copy of the latest version, but a complete, automated system than provides snapshots of all files on your disk made or modified today, yesterday, last week, last month, etc.

Issues of this size are rare, though not unique, in Finale -- and indeed other software. To write off all future versions of Finale is misguided. Things go wrong: storage volumes fails, laptops get stolen, things catch fire, and yes, apps contain fatal bugs.

Backups containing earlier versions of Finale files (and files of other apps) have saved my bacon plenty of times. Files without backups are waiting to be lost.