When loading a Sonar project from another system Sonar complains about missing plug-ins despite the plug-ins being installed 
 
Anybody have a fix for this ? As there is no feature to search or browse to missing plug-ins, how is one supposed to load a project from another studios system ? Or are we expected to all use the same plug-in folder/naming conventions ? We've had this issue in the past when upgrading a system etc and are usually forced to re install plugins but have not had to deal with the issue in regards to opening a file from another studios session. 
I have been a long time Sonar user and supporter but man is it getting hard to keep that game up.
 
We submitted more than a few bug reports years ago when this cropped up and still no fix ?
 
 
 
 
 

Frequency Studios
When loading a Sonar project from another system Sonar complains about missing plug-ins despite the plug-ins being installed 
 
Anybody have a fix for this ? As there is no feature to search or browse to missing plug-ins, how is one supposed to load a project from another studios system ? Or are we expected to all use the same plug-in folder/naming conventions ? We've had this issue in the past when upgrading a system etc and are usually forced to re install plugins but have not had to deal with the issue in regards to opening a file from another studios session. 
I have been a long time Sonar user and supporter but man is it getting hard to keep that game up.
 
We submitted more than a few bug reports years ago when this cropped up and still no fix ?
 
 
 
 
 

So are you saying that either you, or the other Sonar studio system has "customized" the plugin install paths, rather than going with the default install paths ?

More data, please...are you talking about plug-ins that come with SONAR, or plug-ins from other manufacturers?

Thanks for chiming in Craig, The plug-ins in question are 3rd party Slate Digital to be exact and are the exact same build etc in the other studios session, the session came to us via a .cwb file. And yes the plug in path has been customized as has always been our preference which to the best of our knowledge is not an issue, nor should it be. We have been using Cakewalk for well over 10 years and have experienced this in the past with 3rd party plug-ins and have remedied it by re installation if memory serves. We are not willing to do that in this instance and assumed that the bug would have been sorted by now, apparently not. This is very frustrating and is impacting our business in a very serious way.
 
Any constructive insight is welcome 
 

Is it possible one machine used VST3 and the other does not have them (but does have VST2 versions)? The only time I saw this was testing a project (created in Splat with VST3 migration on) and opening it in X2. The VST2 plugs were there but the project referenced the VST3s it could not use.

I have since shut VST3 migration off in preferences so both versions remain exposed.

The plugin paths shouldn't matter if the relevant plugins are all installed - it's their unique IDs that matter, and they should be identical. Can you verify that the plugins are showing in the Plugin Manager?

related to the old 8.3 filename format maybe?

pwalpwal
related to the old 8.3 filename format maybe?

Most likely, hence why a reinstall can resolve.

I have many third-party plug-ins installed on my laptop and desktop. They have different install paths; the laptop is a to-the-letter Cakewalk installation and the desktop is highly customized, but I have not experienced this problem so can't offer any suggestions on how to solve. IIRC Slate uses iLok, yes? Could there be some kind of secondary authorization, like being keyed to a specific hard drive or machine ID? 
 
Do Kylotan's suggestion first - make sure the plug-ins show up in the plug-in manager. But consider contacting Slate support. Perhaps they have encountered this issue before, and have a simple solution.
 
If all else fails, maybe you could obtain the presets used for the plug-ins in particular projects, load your plug-ins to replace the identical ones in the project, then load the presets. But it really seems that shouldn't be necessary. SONAR can load projects from collaborators where you have mutually owned plug-ins. The question is what about specific plug-ins complicates that process.

Kylotan
The plugin paths shouldn't matter if the relevant plugins are all installed - it's their unique IDs that matter, and they should be identical. Can you verify that the plugins are showing in the Plugin Manager?

Yes, we checked there first then inserted a plug  in the bin to verify, Thanks for the suggestion though