Tried to open .sesx file, discovered it was empty.

[FranzPattison]

I recently tried to open an old multitrack file only to find it was empty.  I opened up the file in notepad and I found that all the parts of the file that refer to the files used in the project, were missing.  This is very odd because when I saved the file, they were actual functioning files with no data missing.  Not only this, but the automatic Audition backups were also empty.  I don't know what kind of bug has destroyed some of my old project file but it sucks to have to redo the whole project.

I tried to attach one of the sesx files but it would'n't let me

[Rag and Bone]

I don't know how this happened. Hopefully someone more knowledgeable than I am will chime in.

I'll just ask a few question in case the answers give anyone a clue:

What do you find in the strings of the file that begin "<file absolutePath" or " <audioClip", or are those strings missing?

Are the dates on the backup files reasonable?

And can you gives us details of your system as well?

[SuiteSpot]

What generally happens in this case is that there has been some "issue" - usually a local one eg a crash or system reboot or (insert whatever...). Then what happens is that when you (not necessarily you) open the session and a message pops up saying (and I don't recall exactly) something like there is an existing 'previous' file or session and do you want to continue or delete it.
Now this is where you do two crucial things...

1. Backup the sesx file you are attempting open as well as any and all automatic backups

2. You answer 'delete' - yes this is counter-intuitive but to continue is where it all can turn to custard as the state of that 'previous' session is unknown and in some sort of nether region of memory and while continuing 'looks' like all is well it generally is not and this is where the session can get corrupted and eventially all of your backups.
This may or may not be your circumstance so YMMV but it is certainly a situation that has reared its ugly head in the past.
The lesson here - if you are working on a session that is of some importance (and aren't they all?)  then back it up (locally and remotely but not cloud related) before and after you work on it (with different names obviously!) and do NOT rely on anyone else including Adobe (not because you can't trust Adobe to do so but this way you can only blame yourself).
We have all been caught once so don't be caught twice.

[FranzPattison]

Oh okay, this makes sense because if a file were corrupted it would not
open at all but I couldn't for the life of me understand how a file could
selectively delete parts of the code but in a very orderly way. And yeah
I've had issues with crashes so I can see this happening for sure. Well I'm
glad this has a specific cause, I thought the files were just corrupting on
the drive somehow. Thanks!