Do you have a backup of the tuner workspace on console server?
Yes, I have it.
I tried restoring the backuo but may be its corrupted.
The last thing I will do is remove the CMS channel and subcribe to it again. The objective is that BBCA create a new channel folder (ch.##). Then restore de msf.txt file.
What do you think about it?
Yes, you can try this, but there would be inconsistencies in the console configuration which you need to fix later... I am saying this as I have done this before.
I will try it on the production environment because I cant reproduce the issue in my test environ.
The deletion and subscription of the CMS channel dont solve the issue.
What you think about reinstall de console?
I will install it in other machine just for test but in the production environment we have the CMS in the same master transmitter server.
I installed the Console in other machine and all work fine, so the issue is not related to the CMS channel, its related to the same Console application installed on the server.
Theres a way to reinstall the Console if its installed in the same server with the master transmitter?
What will happen with report center, collections createds? I will lost it?
The best way is to be proactive and back up the CMS channel and keep a separate backup of the workspace. There might be issues with CMS settings and whenever you find one you can replace the old CMS channel or if that does not work replace the workspace.
Re-installing the console will take ages, Although, the collections would not be lost, as they are stored in AD as well as the Query Library. you have to re-initialize the Database and AD connections and so on so forth.
I tried to reinstall the console but the BBCA installer dont let run it again if there is a BBCA component (transmitter or console) installed.
I tried to just uninstall the console but the installer uninstall both (transmitter and console).
There's a way to just reinstall the console?
After some tests I think that the only difierence between an endpoint tuner and the tuner hosting the console is the precense of the CMS channel.
I suscribe the CMS channel in an endpoint tuner and the console work fine. So aparently you dont need to run the BBCA installer to have the console working, just have to subcribe the CMS channel.
Now I'm not shure why after the delition and re-subscription of the CMS channel the issue is still happen.
May be there are a cache that I have to flush after delete the CMS?
There are dependencies associated with the CMS channel (infact an other channel in the BBCA world). So resolving the issue at the CMS end wont solve the issue. You have to check it within the tuner kernel (Infrastructure Service), the Console channels., i.e., Report Center, Policy Manager, Infrastructure Administration and so on, so forth.
So re-installing the console or replacing the CMS channel may not resolve this issue.