I read a post on the Spacial forums today where a user had just downloaded the latest version of SAM broadcaster because the program told him there was an update available.
The problem was this user was using SAM Broadcaster 2013 and the auto updater tried updating it to SAM Broadcaster 2014 for which the user didn’t have a valid key & inevitably it all went horribly wrong for him.
He now can’t get his copy of 2013 reactivated until the support staff (or lack of) are back in the office. It’s a holiday weekend in America.
So it looks like he’s going to be stuck until at least Tuesday with no way of using SAM Broadcaster.
When it comes to a SQL server running along side RadioDJ some users have found that their webhosts won’t allow connections to the default SQL port 3306.
If you need a specific port open for this to work it’s probably a wise idea to email your website host support department asking if it’s OK to use a non standard port for use with SQL. Otherwise you may get into trouble with them.
If your webhost doesn’t allow mysql connections on a standard 3306 port then you need to get creative by changing the default SQL port in the SQL server.
It’s not as scary as it sounds. Honestly it shouldn’t take too much to sort it.
1) Backup your RadioDJ database using the database setup tool.