My BCA will not come up. When I start the Broadcast Agent Adminstrator tool and choose Broadcast Agent Manager from the Host tab, it shows that the Broadcast Agent is off. When I click on the On button and click apply, there is about a 20 second delay and a window pops up stating “Failed to connect to scheduler”. There is a Details button on the message window, but it’s greyed out and can’t be clicked.
I have checked the bomain key, tnsnames file ( our repository is in Oracle 7.3). I have also run the Business Objects Server Configuration tool ( servconf.exe). Under Identity for Busobj.exe Automation Server I have clicked This User (recommended setting). I have verfied that the user entered is in the local administrators group on the NT server that BCA is installed on. I’ve clicked on the Test User Account button and I am told “Identity Information has passed all tests”.
BCA was successfully running on the server a couple of weeks ago. I suspect someone has changed some setting somewhere, but I’m at a loss as to what it his.
My BCA will not come up. When I start the Broadcast Agent Adminstrator tool and choose Broadcast Agent Manager from the Host tab, it shows
We have this problem also. We logged a call to BO tech support and have tried numerous solutions, but have not been able to solve the problem. Since we are going to upgrade from 2.5 to 2.5.1, we are going to do the upgrade and see if it fixes the problem.
Has anyone out there seen this problem and solved it???
My BCA will not come up. When I start the Broadcast Agent Adminstrator tool and choose Broadcast Agent Manager from the
Host
tab, it shows
We have this problem also. We logged a call to BO tech support and have tried numerous solutions, but have not been able to solve the problem. Since we are going to upgrade from 2.5 to 2.5.1, we are going to do the upgrade and see if it fixes the problem.
The likely cause is that the password for the BCA within Supervisor has changed. To resolve this, either change the password back to what it was previously, or click on the button to ‘Monitor one more broadcast agent’ and add it again with the correct password details.
My BCA will not come up. When I start the Broadcast Agent Adminstrator tool and choose Broadcast Agent Manager from the Host tab, it shows
Mike Wrote:
We have this problem also. We logged a call to BO tech support and have tried numerous solutions, but have not been able to solve the problem. Since we are going to upgrade from 2.5 to 2.5.1, we are going to do the upgrade and see if it fixes the problem.
Has anyone out there seen this problem and solved it???
Well, I’ve solved my problem, but I doubt it’s the same solution for Mike’s problem.
We had a disc failure on the Oracle server that houses our repository. The disc was replaced and it was restored from a backup that was less than 24 hours old. About a month ago, we moved the repository from one Oracle server to another. Then about a week ago, we moved it again. Looking at the connection info in the Repository Management tool in Supervisor I noticed that the connection information pointed to the server that the repository was on two moves ago. Everything else that was restored seemed to be restored to the right version. Go figure? Add to that the fact that the Document Domain got corrupted when the disc was restored. Fixing those two things allowed me to start BCA successfully.