Guys,
yes you can shut the "Station Database", i.e the log. This will allow you to continue to playout from either the pad or manually - this is how stations that run two (or more) services from the same studios and audiowall work, i.e FM and AM in the same building.
As we are talking about a problem with a particular user, the database you'll want to try to repair is the "directory" database, sadly as every copy of Myriad, Myriad Manager, Remote Edit Server, Scoop, etc are all checking this database for correct user login at startup (for history and rights), they maintain a connection to this database, so you HAVE to close all applications before using the emergency recovery utility.
You can tell if any PC still has a connection to the database, as you'll see a *.ldb file (locking database file), you can try deleting this manually if you are sure no PC's still have connection, if it won't let you delete it then something is still accessing the database. If this is the case you could try forcibly closing the connection to the file on the server, but this could cause instability with any client PC's still connected.
As a LAST RESORT, you could try renaming the "directory.mdb" to "directoryOLD.mdb", When you start Myriad it will detect that it is missing and create a new one for you - HOWEVER you will need to enter all of your users again.
Regards
David Boulton Brand Manager Broadcast Radio Ltd
|