Hey there folks. It has been forever since I posted here. I am migrating my whole setup to a brand new computer and have been able to reinstall plenty of things fine including Sonar Platinum Producer. I am running the absolutely latest version of Platinum. The system is a 64 bit Windows 10 Pro system. I reinstalled the latest version of Ivory 2 and can use it fine in Cantabile (the Ivory 2 standalone app). It isn't seen in a VST scan by Sonar. I know the iLok 2 is working correctly with Sonar because several of my other plugins (Softube FET Compressor and TSAR-1 for example) work fine. A forced rescan does not show problems and it doesn't get Ivory 2 to show up. A check of the Ivory 2 library integrity shows no problems. I have my 64 bit VSTs in C:\Program Files\VstPlugins rather than the standard Sonar default. That has never mattered before and is exactly the same as it was before in my old system.
 
How can I force Ivory 2 to be recognized? I know in the past this was a problem for some people but Sonar has changed quite a bit so I am not sure the solutions are relevant now. Any help would be greatly appreciated.

I have Ivory 2 running on my 64 bit Jim Roseberry computer I got about 16 months ago. I had no problems reinstalling. ON some of the programs or softsynths you need to go back to the original DVD to install and then update to the latest version.
 
Go to Preferences Vst scan paths and make sure you have C:\Program Files\VstPlugins in there. Go to Plugin Manger and see if Ivory is showing up there. Make sure it’s in the Synth Rack Menu so you can add it as a softsynth
 
 In my system I found ivory VST.dll in C:\Program Files (x86)\Cakewalk\Vstplugins and also in C:\Program Files\Cakewalk\VstPlugins  If you run out of options, for sure try installing in those default locations.
 
Once the VST shows up in plugin manager then  try this to link it up with it’s Library: C:\Program Files (x86)\Synthogy\Ivory\Ivory Library Tools.EXE

I solved the problem. Everything was located where it should have been and the VST path was configured properly in Sonar. I went in and reset the VST's to defaults and then rescanned and it all came up perfectly well and is now working fine.