Hi,
Has anyone come across ‘Cannot reach repository database’ error? BO installation went OK but when I copied BOMain.key in my Locdata folder, I get above mentioned error. However, same BOMain.key allows some users to logon to repository without any problem.
Any suggestions would be greatly appreciated.
neel
Listserv Archives (BOB member since 2002-06-25)
Has anyone come across ‘Cannot reach repository database’ error? BO installation went OK but when I copied BOMain.key in my Locdata folder, I get above mentioned error. However, same BOMain.key allows some users to logon to repository without any problem. Any suggestions would be greatly appreciated.
How did you install? If you installed from a “Master” Install on a network as opposed to the CD, BO probably wants the BOMain.key file in the SHData directory. Don’t know why there is a difference but it was a problem we ran into.
Hope that helps!
David Jelinek
Listserv Archives (BOB member since 2002-06-25)
Neel wrote:
Has anyone come across ‘Cannot reach repository database’ error? BO installation went OK but when I copied BOMain.key in my Locdata folder, I get above mentioned error. However, same BOMain.key allows some users to logon to repository without any problem. -------------------------------------------------- Your installation may not be able to find the bomain.key file. The easiest way to check where it is looking for this file is to run the setup program again. A dailog box should come up with a modify button in the lower right hand corner. If you click in this it will bring up another box that lets you adjust the paths for certain directories and where certain files should be located like objects.lsi/ssi or bomain.key. First check to see where the Security domain is set for either local or shared. You want it local. This should then let you work properly.
Glenn Fredericks
Data Warehouse Specialist
glenn_fredericks@aal.org
(920) 730-4700 x4236 or 1-800 CALL AAL
Aid Association for Lutherans
4321 N. Ballard Road
Appleton, WI 54919-0001
Visit our Web site at www.aal.org or e-mail us at aalmail@aal.org
AAL… Financial services. Lutheran heritage. A powerful combination.
Listserv Archives (BOB member since 2002-06-25)
We have gotten this message when the tnsnames.ora file does not have a reference to the repository
database in Oracle.
Hope that helps.
Jennifer LaTulippe
PowerTel, Inc
jlatulip@powertel.com
Neel Sekhon neels@CADENCE.COM on 10/12/98 12:32:02 PM
Has anyone come across ‘Cannot reach repository database’ error? BO installation went OK but when I copied BOMain.key in my Locdata folder, I get above mentioned error. However, same BOMain.key allows some users to logon to repository without any problem.
Any suggestions would be greatly appreciated.
Listserv Archives (BOB member since 2002-06-25)
Neel,
Make sure you have valid Middleware (and are using the same middleware that is specified in the BOMAIN.key). If others can login with the same key, then you either have:
Reinstall your middleware and try again. If that doesn’t work, try creating a new BOMAIN.key using the safe recovery. If that doesn’t work, run the Oracle Installer and make sure that you only have a 2.x version or Net8 version of the middleware installed. If you have them both, Oracle has BIG issues with getting them both running at the same time. You can do it, but it is a pain to configure and Oracle doesn’t suggest/recommend it.
Hope this helps.
-rm
Listserv Archives (BOB member since 2002-06-25)
Neel wrote:
Has anyone come across ‘Cannot reach repository database’ error? BO installation went OK but when I copied BOMain.key in my Locdata folder, I get above mentioned error. However, same BOMain.key allows some users to logon to repository without any problem.
Note that contrary to a few previous responses, this error has nothing do with the inability to find a bomain.key. If you can’t find a bomain.key, a user will simply go directly into Business Objects without being prompted for a userid/password. This problem indicates that there is an issue in the configuration of the middleware being used to connect to the database. The most likely problem is that the user does not have the database connectivity drivers specified in the bomain.key installed (SQL*Net for Oracle, for example). I’d also suspect that the data source configuration could cause problems if you were using ODBC to connect to the repository (I’ve never used ODBC for this connection). If the data source name specified in the bomain.key connection has not been set up in the user’s 32-bit ODBC setup, this would make the connection impossible.
FYI,
Bob Molby
GE Lighting
Listserv Archives (BOB member since 2002-06-25)