Scheduler cannot log into the repository.(BCAG0460)

Question

Hi All,
Could anyone please help me in the issue described below?
We are using BO 6.5 ZABO version for our Business Reporting purpose. The BO application is installed on one server and the BO Repository is residing on another server. We have been experiencing the following error messages, especially during the Weekends.
==============================================
-Error- 11/10/08  08:08:13:961000  (<server_name>@BCASchedulersGroup_BCA_0) Scheduler cannot log into the repository.     (BCAG0460) - Cannot obtain SQLBO connection.     (BCAG0680)
HYT00
[Microsoft][ODBC SQL Server Driver]Timeout expired
0
-Error- 11/10/08  08:08:13:961000  (<server_name>@BCASchedulersGroup_BCA_0) Bad connection to repository (4865)     (BCAG1180)
-Error- 11/10/08  09:37:52:689000  (<server_name>@BCASchedulersGroup_BCA_0) Scheduler cannot log into the repository.     (BCAG0460) - Cannot obtain SQLBO connection.     (BCAG0680)
-Error- 11/10/08  09:37:52:689000  (<server_name>@BCASchedulersGroup_BCA_0) Bad connection to repository (4865)     (BCAG1180)
-Error- 11/10/08  10:37:29:836000  (<server_name>@BCASchedulersGroup_BCA_0) Scheduler cannot log into the repository.     (BCAG0460) - Cannot obtain SQLBO connection.     (BCAG0680)
-Error- 11/10/08  10:37:29:836000  (<server_name>@BCASchedulersGroup_BCA_0) Bad connection to repository (4865)     (BCAG1180)
-Error- 11/10/08  10:53:42:214000  (<server_name>@BCASchedulersGroup_BCA_0) Scheduler cannot log into the repository.     (BCAG0460) - Cannot obtain SQLBO connection.     (BCAG0680)
08001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
17
==============================================
On last week of Sept'2008 we faced similar issue and we tried fixing the issue by recreating the bomain.key file & restarting the BO services on the servers, but it didn't help as the actual cause was network connectivity issue between the BO application server and the BO repository server.
This issue again reappeared on last week of Oct'2008. We tried rebooting the servers and restarting the BO services. The issue got resolved.
I would like to know the followings:
1) Why this issue occurs once in a week, mainly on weekends?
2) Is it necessary to reboot the servers and restart the BO services on a periodic manner? If Yes, what should be the frequency of doing this activity?
3) What would be the consequences if the BO applications and the BO repository are made to reside on the same server?
Thanking in advance to all those generous souls willing to help me out in tackling the issue at the earliest.

Answer 1

Hi Suraj,
Following information might help you to resolve your query.
Cause
There are two possible causes for this error.
- The WebIntelligence services are set as 'System Account'.
- The Broadcast Agent was not installed properly.
Resolution
1. Change the WebIntelligence Manager and Orb services parameters from 'Log on as' to 'This Account'.
2. Logon with the local machine administrator account who installed and configured Informix.
3. Restart these two services.
4. Re-install BCA following the steps listed in the 'Note for Informix Users' section in the Readme file.
Regards,
Sarbhjeet Kaur