Sometimes I need to open Cakewalk TTS-1 and I can't do it. Whenever I am trying to do that I have this information: Can not open registry.{C25C3D78-OFBC-4dbb-BA9F-3A7DDEE3818D}. I tried to reinstall Sonar Platinum - doesn't helps. I installed additional Sonar X3 - TTS1 works perfectly. On the Platinum not. Anyone knows how to solve this problem?
 
Thanks in advance
 

Did you try to start Sonar as administrator ?

Hi. I have not seen this myself before.
If you installed Splat after X3, I would try re installing Splat again. 
If you use CCC, it only takes a couple of minutes.
TTS1 is a Dxi, if I'm not mistaken, and should be installed with the program.
Others may have better answers than me.
All the best.

Thank you CedricM.
I never tough that this is such a simple solution. However I never experienced this problem before. 
So, as administrator I can open TTS-1.
Thanks again
 
Henryk

I'm glad that worked out, but I really think you shouldn't have to run Sonar as administrator.  TTS-1 opens for me when I run Sonar as a normal user.
 
Perhaps a permission did not get set correctly during an install?  I don't have an answer, but was just wondering ...

Yes, I agree. It shouldn't work like that, but et least is working. 
I don't think the problem is with installation. I tried to reinstall several times - didn't work.
Thank you guys again.
 
Henryk

There's something qwerky about TTS-1 these days. I've had it stop working on Platinum. It worked in Home Studio  but not Splat, it would just be greyed out. .  I was due for a upgrade of SPlat so that fixed it. This was back in January/February. It did the same thing on both my computers. So it's possibly a minor bug with the new versions of Splat. Possibly TTS_1 code is very old and losing out in the new environment.
I'd sure hate to loose TTS-1. 

abacab
I'm glad that worked out, but I really think you shouldn't have to run Sonar as administrator.  TTS-1 opens for me when I run Sonar as a normal user.
 
Perhaps a permission did not get set correctly during an install?  I don't have an answer, but was just wondering ...

OP doesn't mention his OS -- but if he's still on Win7/8 that might explain things.  The whole "Run as admin" fix doesn't seem to be an issue with Win 10 users. 
 
In any case, it's a simple enough workaround, and even better, if he sets the RAA option for the shortcut under Properties-Compatibility, he never has to think about it again.