can not open a specific project. Heavy V Vocal was used
sonar x1 crash     fatal error has occured module C\Program Files\ Cakewalk Sharred DXI\VVocal\cronus.dll

Open in “safe” mode.
Hold down the shift key.
You’ll be prompted to select which plugins you want to load.
T

Safe mode would be the first thing I would suggest. It couldn't hurt.
But I believe V Vocal is exempt from Safe mode.
I could be wrong about that. but I thought I remember someone mentioning it was somehow not a loaded plug in.
 
 

You might try temporarily removing the Vvocal .dll from your vst folder. It might launch then but without v-vocal.At least you might get it back online.

vvocal is dx not vst, it's the cronus.dll referenced above

My bad. I haven't used a DX plug-in in ages and had forgotten it isn't vst. I went to Melodyne as soon as it was offered.
I would look for the DX folder then and try removing it, unless someone else has another idea. 

Thanks Guys I was able to open the project in safe mode without the cronus.dll  The vocal clips are there without the V Vocal however some clips are muted a small red circle indicates which ones. It looks like the data is still there. Is there a way to bring them back to life.
 

I know you probably don't want to hear this but as time goes on V Vocal will become obsolete and unusable.
Sonar X3 and up uses Melodyne ARA. It took me a few to pick up the tricks of Melodyne compared to V Vocal but is was and is well worth it.
 
It seems to me anyway, there is just so much more control and ease of use in the features themselves.
Just something to think about when Bandlab has Sonar up and going again.

John Martelli
Thanks Guys I was able to open the project in safe mode without the cronus.dll  The vocal clips are there without the V Vocal however some clips are muted a small red circle indicates which ones. It looks like the data is still there. Is there a way to bring them back to life.
 

The symbol just denotes that the clip is muted. You should be able to "bring them back to life" by simply unmuting the clip. IIRC v-vocal always worked on a copy of the clip and kept the original in a muted state hidden below it, which I guess is the clip that you are seeing now. For future use it might be better to make sure that you bounce any v-vocal edits before closing the project so that open edits are not left open. This seemed to be what caused the most problems with it. Later versions (X3>) use v-vocal via ARA and it seems to be more stable that way for whatever reason.