I have saved a file without other backup, when i open it again, errors occur, the error message is " Unexpected end of file has occurred. The following elements are not closed: worksheet. line 5515, position 13".

It's there a way to recover?163 Severn Street Alteration.sm (550 KiB) downloaded 42 time(s).

Wrote

I have saved a file without other backup

There is no file, simply ! Same error message.
Unless the document is trivial like 2*3 ,,, ln(2)
it is good practice to save the same document as Copy
in the same directory ... save as the work progresses.
So, on bad luck like crash, infinite loop ...
you don't lose the last save working part of the project.

Cheers ... Jean

Wrote

Wrote

I have saved a file without other backup

There is no file, simply ! Same error message.
Unless the document is trivial like 2*3 ,,, ln(2)
it is good practice to save the same document as Copy
in the same directory ... save as the work progresses.
So, on bad luck like crash, infinite loop ...
you don't lose the last save working part of the project.

Cheers ... Jean

I have a cloud backup, and it's autosave. So I could not open either of them

Was easy to fix, just close the tag, seems that just the last line hasn't been saved.

163%20Severn%20Street%20Alteration_Kr.sm (550 KiB) downloaded 45 time(s).

Edit:

I did the fix in a text editor but you could have used Insert> Development Tools> SMath File Recovery
(Development tools plugin must be installed).

This allows you to select the corrupt file and tries to save a recovered version. This can be opened then. In the present case this works, I just tried.

Related improvement introduced in build 7005: when SMath Studio detects similar errors it now shows the following message:



Program shows only available content if user presses OK.

Wrote

corrupted files

... is an expression we used in Mathsoft Collaboratory.
As an example, MCD 14 saved as MCD 11 had corrupted many
files opened back MCD 11. Typical was sending some regions
at the extremes low/right of immense number of white pages.
Easy to recover by backspace/patience under background.
From version to version Smath looks inconsistent with the
most disastrous "root element missing", i.e: gone for ever.
There were those long discussions about big/small numbers
from incompatible situations "Symbolic".
IMHO, Smath crashing has no answer.