This isn't an audio file you are trying to open, but a multitrack session. Is that what you intended? If it is, then you'll probably need some help from Suite Spot, who's probably forgotten more about session files than the rest of us know!
If that really is a space in the name in the file path, rather than just a typo, then Windows will reject it, hence the error message. If you can get to the file in Windows Explorer try renaming it without the space.
It should open it with a space - Windows regards it as an invisible graphic represented in the real file name. It's the same as typing Alt+255.
I did look at that session file and if you remove the space from the name then that tells the whole story
The sesx file was filled with nulls - not an easy thing to do but can occur if opened with some other application (like Word) I guess
Unfortunately, most of the time I get to examine these sort of files it is usually after the user has made (understandably) several attempts to open the file
It would be interesting to know the circumstances so as to determine a cause
I have the original file that I didn't attempt to open with word. I tried
to self-fix as you mentioned. If I take out the space on the original file
would that help?
The space is unlikely to be the cause.
I assume that the sesx that you emailed me yesterday was the original file and not the one you tried to open with Word?
I thought so. Im concerned of this happening again. I thought i saved and
closed out properly.
Unfortunately its sometimes difficult to recall some small detail which may have impacted.
I don't know how many times I've been asked to fix some PC problem and when you ask the person what happened between the time it was working last and now and invariably the answer is 'nothing'. Of course later you find that they had upgraded their OS, installed a new video card and a heap of cracked software or some other such events.
'Oh I didn't think that made any difference' LOL
I'm not saying this is the case with you but something has occured which is out of the norm otherwise every Audition user would have this problem every time they used Audition and that is certainly not the case.
In my case (this is a few years ago) I went through a period where I would get a crash more often than not - to the point I was hesitant to do too much.
I ended up writing a specific ses/sesx backup utility (http://www.mediasweeper.com.au/sesbackup.htm). Maybe use that before or after each session until confidence returns
The crashes BTW were caused by a rogue video driver and since then the only crash I have had has been due to a dodgy plugin
Bottom line is that any small detail you can offer will only go towards someone working out the cause.
So think of things like - were you accessing the session across a network, was there something different about this session or the files used, a new hard drive, or new software or hardware just installed, etc, etc
Also (and yes I know it is too late now) but any session which requires work spanning a number of days should always be backed up to at least one other location - most of us have been guilty of not doing that at least once