First, can you "Save As..." or export XML to save as much of your work as you can?

Second, create a special folder for temporary Finale files. (I put a FinaleTmpFiles on my Documents Folder.) I can use it to accept my temporary files and clean it out of files that Finale does not delete automatically when one closes the program. Some experienced users recommend separate temp folders for different versions of Finale (2014.5 and v25, for example).

That's my best advice. Hope it all works out for you.

I've had the same issue, on MacOSX 10.13.6 (High Sierra) with Finale 25.5.0.259. I had a look through the files in the entire filesystem, and found the Finale temporary files, which I gather it uses to save the file (by copying to the permanent location, I would guess). There was no file named EnigmaTemp<long-number-in-error-message>. There was one named EnigmaTemp<long-number>.dragclip, and several files named NfTemp<various-long-numbers>, but none of the long numbers matched the one in the error message. 

My best guess is that this temporary file was removed or cleaned up by applications unknown, which would explain the error message: the file system simply couldn't find the temporary file. Maybe this is a bug in the Finale software, or maybe it's in MacOSX. There was no recourse but to quit Finale and lose the work I'd done (fortunately not much). The only advice I can offer (to myself as well) is save early, save often. 

This is a continuing problem on both the Windows and Mac platforms, and a very serious one. I can't believe the Finale team has been unable to fix it. People are losing their work, folks.

J Adrian Verkouteren indeed offers a work-around above. He or she should have added that one will need to periodically clean out the mess of .tmp files that Finale will make there.

Other software developers have no problem using the system temporary folders. Finale is likely not locking the temp files and the system is coming along and deleting them while Finale is running, leading to disaster. This is not rocket science--it's Software 101. I suggest MakeMusic either send their programmers to get some training, invest in a good reference book, or hire a competent consultant to fix the bug.

>Finale - Error occurred. ID = -2< is a Mac OS message saying that a directory cannot be written to. There are many reasons including that it cannot be found. 

Are your application and work files on your boot drive? If the answer is No, the usual culprit is that the files are sitting on an external, your system went to sleep and can’t find the path on waking up. This includes files sitting in Dropbox, BTW. When that’s the case, there’s really nothing for MakeMusic to “fix”

My problem is that I can't even open up the music at all. 

It would help us to know what version of Finale you are using and what operating system (and version) your computer uses. Otherwise, we have almost nothing to go on.

A while back, I upgraded a version on my Mac, which writes to a different file system - I installed the updated OS on a new SSD, leaving the previous system intact. When I opened a file last edited before the upgrade, Finale was trying to use the previous temp folder on a disk that was no longer writable. Changing the folder as in the first post fixed the problem.

This is an old thread, but unfortunately, the problem has not been solved.  My work-around is this: Create a new file with the same orchestration.  On the corrupt file, select all and copy.  On the new file, select a measure stack and edit menu>insert the clipboard. Then delete the blank measures from the original. This will copy all data including time signature and key changes.  It takes a couple of minutes and no work is lost.  Still very annoying, though.  I agree with the earlier comment that this is poor programming not to lock the temp files.

When this happens, I export as musicxml, and on import it comes in as you had left it. You can save-as over the locked file. (After manually setting the temp file location, I have determined in my case these now-very-rare lockouts happen on files left open overnight or longer, and i suspect my OS locked the file, not Finale.)

This is an old thread, but unfortunately, the problem has not been solved. 

 

I agree with the earlier comment that this is poor programming not to lock the temp files.

No. It hasn’t been solved for Office, Adobe, Digital Performer and many other app users either. In nearly all instances, the work files are not on the System drive in the Default location. Communication errors pop up OS errors.