In a couple of threads semi-related to this problem, I'm starting a new thread just to isolate the Rapture problem specifically.
 
After rebuilding my DAW with both 32 and 64-bit X3 installed, I've had gobs o' problems with VSTs not loading. Most of these I've hunted down and solved, but two defy me: Pentagon (I was able to recover audio data and ignore this one) and Rapture.
 
You lovely folk pointed out a tip that solved some of these Rapture issues: the 1.2.1 DXi version, which I had forgotten about. So after installing 32 and 64 bit Rapture DXi (1.2.1) from an older purchase alongside 32 and 64 bit Rapture VST (1.2.2) from a more recent install where it's bundled with SONAR I was able to solve nearly all my project woes.
 
But, I still have two project files that will not load Rapture. It appears in the synth rack (disconnected). Trying to connect it crashes SONAR, and crashes it hard since it locks up the audio interface, and even after rebooting that (which allows hung SONAR to fully close) , SONAR will not recognize it so a full system reboot is needed.
 
Anyhow, I'm stumped on this one. I've got every flavor of Rapture installed (VST, DX, 32 and 64 bit), and can not get this synth to load properly. I've got an email out to tech support but figured I'd try a hail mary pass at y'all since nobody knows my troubles than other forum-ites.
 
 

I don't understand a disconnected synth rack in the context of X3. Is it, the instance of Rapture is not connected to the originally defined audio and MIDI tracks? If so, can new tracks be connected to the synth? Does the synth UI open?
 
Aside from trying some copy/paste/program save action (sounds like the crash beast already attempted), all I have is running SONAR as Administrator. I would have thought running as Administrator handles the Pentagon issue too.
 
Last resort, go back to a pre-X version of SONAR and freeze/bounce the tracks.

Everything looks right except the synth is greyed out in the synth rack. UI does not open. 
 
Tried running in admin, already am too, no luck.
 
I'll try opening in...sheesh what 8.5? I'll update!
 

So the project does not complain about the synth, it just has it greyed out? Usually that indicates a frozen synth but I am sure there is no indication the tracks are frozen. The safest bet is the version that last opened the project.
 

Wicked, in the project with the greyed out synth, are you able to insert a new instance of Rapture without any crashes?
 
If so, i would suggest you do this and simply drag/copy the old midi clips to your new midi track and then delete the greyed out synth.
 
You might have to manually delete any associated tracks as i believe Sonar has problems associating a disconnected synth with it's related tracks so you cannot use the "remove associated tracks" option when deleting a synth.

I would try Replace synth in the Synth Rack and see if you can load another version of Rapture.
 
Kind regards,
 
tecknot

Yes it does seem like something does load in the already-instantiated Rapture(s), but the instrument is disconnected in the synth rack. It doesn't otherwise indicate anything is strange until you try and power it up.
 
Yes I can load a new version of Rapture (or replace) just fine. The problem is that I lose my preset when I do that. These last two projects are some synth-pop tracks where the sound is pretty integral to the piece and I'm hoping to save myself the days and days of trying to rebuild the patch source. 
 
It's actually that very issue that was being discussed in a tangent thread that I consolidated. SONAR actually has that info  baked (haha) into the project file, there's just no way for us to get to it. 

Why not make a copy of the project, then you can play around with it until you figure out how to deal with the preset part of things?
 
I wish I had an idea of what else to do, other than just delete that instance.
 
Bob Bone
 

Good idea. I've also got other projects to work on but eventually I'll have to deal with it.
 
I was able to get a little time away from work and rang up tech support, less than 10 minutes and I'm in! On hold now. First solution attempt: copying Rapture's DXi folder into "Shared DXi" to see if it picks it up there. No luck so far.
 

The location of the DXi should not matter it is picked up by SONAR from the registry. Moving the DXi folder around is not going to change anything unless the dll is unregistered and re-registered with regsvr32.