I got this error message, right in the middle of a mix. Rebooted, launched sonar x3, got this message.
I'm not sure what to do .I Copied the project folder into my driver and tried to open the project on my laptop, no luck.
I am at my wits ends ; i do not want to re-record the artist -unless i have no other option. Any suggestion folks? I know there3 was a topic on this, however, i did not find any solution on that thread-sorry for bringing this up again..
Thanks.

Well you haven't given us much data to go on, so in the absence of more specifics (e.g., 32- or 64-bit?), I'd suggest opening the project in Safe mode by holding the shift key when you click on the project you want to open (not when opening Sonar, opening the project). Don't load any plug-ins and see if the program crashes. If it doesn't, load the plug-ins in groups on subsequent openings, and see if one particular group causes Sonar to crash. If so, then try to isolated the plug-in within that group.
 
Of course it could be something other than plug-ins, but I'm going with the odds here and plug-ins are a good place to start. BTW if you recorded the singer prior to the crash, the file is in your hard drive so it won't be lost.

My bad..
I run a 64 bit machine , i have sonar x3 , i also have Pro Tools, Cubase and ableton live-the reason for all these programs, is simply due to the fact that other engineers work in the studio, so we all have fave DAWS .Mine, just happens to be Sonar .
I had a few plugins, in the stereo bus , then i grouped the project-'verse', 'hook' and 'intro' , with their corresponding buses .
I was editing the parameter on perfect space-got kinda carried away-when all hell went loose. So, I'm wondering, should I remove this plugin, just to test of the project will work-start in safe mode as you suggested first of all?
 
I hope this is sufficient information?
Once again, thanks for replying, really!

Perfect Space is a 32-bit program in a 64-bit world. While bridging technology can work, it is a kludge. You have a clue that Perfect Space might be the source of the problem, so you can try loading the project in Safe mode without Perfect Space and seeing what happens. But if the problem persists, I highly recommend following my original advice about opening the Sonar project in Safe mode and don't load any plug-ins, and if that works, narrowing down the candidates from there.  
 
If the project loads and works properly after opening in safe mode without Perfect Space, and you then save the program, it will not include Perfect Space any more. You can then try inserting it and re-creating the settings it had. Sometimes after a "32-bit fail" saving Sonar without the plug-in loaded will let you re-insert the 32-bit plug-in and have it work.
 
 

Well Anderton , i cannot 100 % point at Perfect space as the culprit, but i was on it, before it crashed. So, i will try that. I am not in the studio right now, i left, rather angrily as you can imagine, lol.
Im home now, so i will try sonar in safe mode as you suggested and get back to you with an update.
Thanks once again!

What you described certainly increases the odds that the problem relates to Perfect Space. (I'd love to see a 64-bit convolution reverb in Sonar.)
 
Legacy plug-ins are a no-win situation. If you include them for backwards compatibility, you run into reliability problems. If you do like many DAW manufacturers and ship only the current 64-bit plug-ins with a 64-bit program, or can ONLY run 64-bit plug-ins, then good luck opening older projects.
 
When PreSonus introduced their 64-bit version of Studio One Pro, at a workshop one of the attendees asked what the solution was for running 32-bit plug-ins. Their answer was "tell the manufacturer to make a 64-bit version."

I still can't understand, why DAWS are 64 bit n most of the plugins are still 32 bit! And the guy at studio one workshop is right though , still can't believe he said that . lol... Oh Presonus, don't import OMF! GRRR!!
Oh, i have one auto save from an earlier point, i will try to open that first in safe mode .
As for perfect space, i am starting to suspect that, it was the catalyst for all this problem..

Tried one of the autosave , but that did not work. I will be in the studio tomorrow, so i will try out safe mode.

Anderton
Perfect Space is a 32-bit program in a 64-bit world. While bridging technology can work, it is a kludge. You have a clue that Perfect Space might be the source of the problem, so you can try loading the project in Safe mode without Perfect Space and seeing what happens. But if the problem persists, I highly recommend following my original advice about opening the Sonar project in Safe mode and don't load any plug-ins, and if that works, narrowing down the candidates from there.  
 
If the project loads and works properly after opening in safe mode without Perfect Space, and you then save the program, it will not include Perfect Space any more. You can then try inserting it and re-creating the settings it had. Sometimes after a "32-bit fail" saving Sonar without the plug-in loaded will let you re-insert the 32-bit plug-in and have it work.
 
 

I tried it with safe mode, got the option of loading plugins, i selected 'NO TO ALL' , the status bar on the top, almost loads, before, it crashes with the aforementioned error message. Any other suggestion? [ I should add that perfect space, has been removed,but i doubt it is the culprit,in that , I'm still unable to open the project. ]

To proceed any further you will need to provide some actual data to help with the troubleshooting - we don't know which version of Sonar you're running (X3e, I presume?), whether other projects open but only one doesn't (knowing this would help narrow down the problem considerably!), operating system, whether you're running Sonar as a 32- or 64-bit program, your audio interface and its drivers, whether you've updated your interface drivers recently, is the project only audio or also MIDI, etc. You should consider contacting tech support, but hey won't be able to troubleshoot if they have no idea where to look for trouble.
 
If other files open, or you can save a load a new project, then your project might be corrupted. There's documentation on ways to load at least part of the project.