"Plug In missing" message for CE - SOLVED!

Ever since X3C whenever I open a project I get a message saying the Console Emulator is missing, the CLSID is wrong and that I need to replace it with one of the choices in the drop down menu directly below. In X3C I could choose the new option and the project would go ahead and load fine, no problem, so I went with it.
Now, using X3D, sometimes when I go through the same routine the project won't load and I get a shutdown and the problem reporter pops up. Very annoying.
Anybody else seeing this or do I need to do a reinstall or something?
 
I forgot to say that I did the plug in reset and rescan the was recommended.

Hi RS,
 
Check to see where your CE folder is installed. For me it resides in the following:
 
32 bit Sonar: C:\Program Files (x86)\Cakewalk\Shared Utilities\Internal/Console Emulator
 
64 bit: C:\Program Files\Cakewalk\Shared Utilities\Internal\Console Emulator
 
You should have two .dll's in each folder. If by chance you do not see these folders where I have them, search and see if by chance they were put somewhere else and then paste them to the directory(s) I have provided above.
 
Then, try doing a plug reset/rescan and see how you fair.
 
If you want, you can check to see if the internal path(s) I have listed are in your registry.
 
32 Bit Sonar: HKEY_CURRENT_USER/Software/Cakewalk Music Software/Sonar Producer/Cakewalk VST/VSTInternal Path
 
64 bit Sonar: HKEY_CURRENT_USER/Software/Cakewalk Music Software/Sonar Producer/Cakewalk VST X64/VSTInternal Path
 
You should see the folder references I've given you listed there. If they are not there, that's where the problem is. Or at least, that would be my best guess on where to start.
 
The only problem close to this that I've had was with the CA2A limiter being installed in a folder that wasn't being scanned. So I cut and pasted it into my Cakewalk directory where it should have gone. I'm thinking maybe something weird happened with your CE folder and it's not being seen or something.
 
Anyway, I hope some of this helps you get to the bottom of it. I'm not sure if you can just re-install the CE from the install program or not, but that may be something to consider also as it may have been a jacked install or update or something. I don't think this will be too hard to remedy though. Tech Support will probably sort it out in seconds if you can give them a call. Good luck....and let me know how you make out with this one.
 
-Danny

The Console Channel_64.dll is not in my CE directory. What I usually do, just to be safe, is rather than completely delete something; I move it to another directory, just in case I need to retrieve it. The plug-in would need to be moved to a directory out of the VST scan path. After moving or deleting the dll, take notice if the scanner indicates the plug-ins removal. If the scanner does not post a message about the removal, run the reset/rescan to force it to clean up the registry.

scook
What I usually do, just to be safe, is rather than completely delete something; I move it to another directory, just in case I need to retrieve it.

Sometimes just renaming something will cause it not to be recognized, like calling is XonsoleChannel.dll.

Danny, scook, and Craig,
Thanks so much for the help guys! I'll try moving the dll and see what happens. I'll let you know.
Thanks again, really appreciate it. It's guys like you that make this forum what it is.

articleI wrote an article about this I wrote an article about thisan article about this 

scook

Anderton

scook
What I usually do, just to be safe, is rather than completely delete something; I move it to another directory, just in case I need to retrieve it.

Sometimes just renaming something will cause it not to be recognized, like calling is XonsoleChannel.dll.

I suppose that would work but if the problem persists, there would still need to physically move the file(s) to be sure, so why not move them first place? And in this case, there is a tool which scans and dives down directory structures so the files need to be moved out of the search path.

 
In this case, you'd want to remove it anyway. But there are instances where you don't want to delete something permanently, you just want it not to be recognized so you can re-enable it again. I wrote an article about this [http://www.harmonycentral...tor-quot/ba-p/34633749]  in relation to the Ueberschall Inspire libraries. The Inspire series can mix and match loops among other members of the family, but not non-Inspire libraries. So when using Inspire libraries I just rename the other ones, the Elastik engine doesn't recognize them, and I can go back to the usual libraries by changing the name back.
 
Another example is when I had 64-bit plug-ins for Sonar and 32-bit for other programs. Sometimes Sonar would scan the 32-bit plug-ins and accept those as the ones to use. I renamed them, re-scanned, Sonar latched on to the 64-bit versions, then I put the names back for the other programs but Sonar ignored them because it was now "keyed" to the 64-bit plug-in.