Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error in connecting repository DB

Status
Not open for further replies.

suris

Programmer
Feb 27, 2002
23
IN
Hi,

Have a problem in connecting infoview....

System config is as follows

DSN : System DSN
Rep DB : SQL Server 2000
O/S: Win 2000 Server

When using infoview username and password getting an error as follows

"Can't reach repository database"

Please thro light on this issue.

Regds,
suris

 
Could be any number of things.

1) Does the DSN exist on the server? Have you tested it? Is the name EXACTLY the same?

2) If it does exist, make sure you have it set up right. On the second screen of the definition, client the Client Configuration button. Make sure the client is set to TCP. I've seen alot of these where they are set to Named Pipes. BO won't work that way.

Try these, let us know how you're doing. Steve Krandel
BASE Consulting Group
 
Hi,

Thanks for showing interest to resolve the issue.

To answer your question

1. Yes, checked the database connection. It works fine.
2. Yes it is working well with supervisor and BOClient. The protocol installed is TCP/IP.

To give you clear picture.

WIServer is installed on IIS5.0 in Win2000 server. No other software is installed on that system.

BO Fileserver is installed in another system (Win2000 server)

BO Client is installed in another system (Win2000 server).

ODBC version are same.

Please thro more light on this issue.....

 
Hi,

In SQL Server two options are there.

1. Windows and SQLServer
2. Windows.


The option which has been set is 1.

There is no option for setting only SQLServer....

Please thro more light on this...
 
1. does the webi user have permissions to use the repository in supervisor?

2. if you're using webi/zabo you don't need the odbc on the client machine, but if it's in error it may cause a problem

3. why is the bo client (desktop components) installed on a server?

4. can the client see the document list or is that failing as well?
 
Hi suris,
Once you have check that you ODBC Data source is working(u can use MSQuery for this a very handy tool). Then the next thing u have to check is the reation of BOMain.key
u have to use the same name for the ODBC DSN and type(user, system) whihc was used at time of creation of BOMain.key.
Now if that is difficult to find out. then u can recreate the BOMain.key file by running the recreate option through supervisor. for this first delete all bomain.key file on your PC. Or in version 5, there is an admin button on the supervisor login which will take u to this menu
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top