It's very strange - when a controller first starts up (such as when rezzed and/or scrip reset) it sends out a 'ping' to see if any other controllers are active. It must be getting a response from some actively running script (i.e. the ghost one at the location it gives!) One easy way to fix is just to change the group used for the farm as two controllers are allowed if set to different groups, although I appreciate there may be reasons she doesn't want to do that. Another thought is to go into the region debug settings (in Firestorm it's Alt R then click the Debug tab) and click to Disable scripts. You can then manually start the scripts in the controller (click to edit it then from the Build menu, select Scripts then Set Scripts To Running) and hopefully the controller will start okay. Once that is done go back to the regions debug and deselect the Disable Scripts option to start up the rest of the scripts in the region. Doing this the 'ghost' controller should become the backup and you may be able to find it by looking for the floating text. Hope that helps! Also, if the region is open to public I'm happy to go there and see if anything odd stands out to me!
OK Buzzy! I will send this to her and let her know. She's pretty techy with these kinds of things but I will definitely let her know that you will be glad to help and yes her grid is open. Thank You So Very Much for your kindness & support!
I am updating this in case any others might experience this. The issue was with the grid running y engine scripts. Using the power controller for y engine scripts found in the update section in Mintor resolved this. I am will also note with the Q3 pre release edition the controller works out of box as is.