[OPENEDGE]Broker rejects connection

sql92

New Member
We use ODBC a lot to fetch data from Progress database. Usually things work, but from time to time we get this error message: [OPENEDGE]Broker rejects connection. It looks that the problem occurs when there're many concurrent ODBC queries. Could this be due to some kind of limitation on the number of ODBC connections that the server can accept? If so, is there a way to change this limit?
 

sql92

New Member
This is from the log:

[2014/07/25@19:45:23.001-0700] P-5092 T-3504 I SRV 1: (452) Login by SYSTEM on batch.
[2014/07/25@19:45:23.008-0700] P-5092 T-3504 I BROKER 1: (5644) Started for 2600 using TCP IPV4 address 0.0.0.0, pid 5092.
[2014/07/25@19:45:23.008-0700] P-5092 T-3504 I BROKER 1: (5645) This is an additional broker for this protocol.
[2014/07/25@19:45:23.009-0700] P-5092 T-3504 I BROKER 1: (8864) This broker supports SQL server groups only.
 

sql92

New Member
Thank you, RealHeavyDude.

The article refers to OpenEdge Console, but I cannot find this program on the server. How do I start it?
Also, when I try to start OpenEdge Explorer, IE opens and navigates to http://localhost:9090, but it shows "This page can't be displayed". What am I doing wrong?
 

sql92

New Member
>Is the admin service running?

How do I check this? (As many others here, I know nothing about OpenEdge. The company "inherited" this system and we are trying to salvage it)
 

Cringer

ProgressTalk.com Moderator
Staff member
Are you running this on Windows? The admin service is a service that should be running in order to connect to port 9090. Run the services program and look for AdminService for OpenEdge.
Could you also let us know which Progress version you're on, as well as OS. Might help us work things out more easily :)
 

sql92

New Member
OpenEdge 11.1 on Windows Server 2012 R2.
I don't see any service with "Progress" or "OpenEdge" in its name among the "Administrative Tools"/"Services"
 

Cringer

ProgressTalk.com Moderator
Staff member
It should be called "AdminService for OpenEdge XX.X". Is Progress definitely installed on the box? Sorry for the stupid question...
 

sql92

New Member
There's no "AdminService for OpenEdge..." on this server. Is there a way to start it manually.

>Is Progress definitely installed on the box?

Well, this is the box that the ODBC driver points to, and the ODBC connection does work. OpenEdge 11.1 is listed under "Programs and Features" and the .db and log files are on this server.
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
Do you know how the database brokers are started? The parameters of the command ("proserve") determine how many SQL servers can be started, and in which port ranges, and how many clients can connect to each server. This information will help you diagnose the issue.
 

sql92

New Member
>Do you know how the database brokers are started?

I know that the brokers start automatically when the OS loads. I don't know what script or service or ... starts them. Any idea where to look for it?
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
Well, there are various ways a process can start when Windows starts; via autostart services, scheduled tasks, group policy, etc. One way to get a unified view of these various automation points is with autoruns from Sysinternals. Typically in OpenEdge databases are started automatically via the Admin Service, although you said there is no such service on your machine.

So I guess you didn't inherit any people to go with the software?
 

Cringer

ProgressTalk.com Moderator
Staff member
Out of interest, is the system a known system, or is it something that was developed internally? If it's a purchased system there may be folks who are familiar with it.
If not, you may be best placed buying a day's time from a consultant.
 

sql92

New Member
Sorry, but I'm not allowed to provide details about the system. I've initiated a separate broker for SQL connections by using the article recommended by RealHeavyDude. Will see how it works.
 

TomBascom

Curmudgeon
First of all make sure that you are logged in to the database server.

The admin server and OpenEdge Explorer run on the db server -- not on the client. The "broker rejects connection" message is a client side message. You might be running the client on the same box as the server but it isn't obvious if you are or are not.

Once you are on the db server you should be able to open a "proenv" window. This is a command line window that knows about the Progress tools and environment.

From "proenv" type:

proadsv -query

This will tell you if the admin server is running or not.

If it is not then the OpenEdge Explorer tool will not function. This might be normal -- it is possible that the application is "scripted" and not run using the admin server. That is more typical in a UNIX environment than Windows but it could be the case. You could look at the dbname.lg (".lg" not ".log" as you typed above...) file and see if there is evidence one way or the other. Posting the extract of the 75 or so lines from the last (333) message might tell us. You might also find some evidence in the \OpenEdge\WRK folder (that is the default name for the work floder -- it might have been changed...)

If the admin server *is* running then type

fathom -query

If that is running then the OE Explorer should work. If you need to start it then type:

fathom -start

proshut allows you stop the whole database or disconnect individual sessions. It does not have a "stop a broker" option.
 
Top