Kbase 17342: Actuate This client not licensed for remote connections 4406
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Actuate This client not licensed for remote connections 4406
You are trying to connect from Actuate to a Progress db across a
network. You are getting the error:
This client is not licensed for remote connections. (4406)
You say, "but I have installed client-networking on my PC!"
It is important to understand the connection path to the database.
Actuate makes a direct connection to the OIB/OID. It is then the OID
which actually makes the connection to the database. The error
message indicates that you do not have client-networking installed on
the server machine. You have asked the OIB to use the TCP protocol to
connect to the db. However, you do not have a license to use Progress
with TCP on the machine where the OIB has been started.
There are three ways to avoid this error.
1) Install client-networking on the machine where the OIB/OID has
been started.
2) Do not ask the OID to connect to the db through TCP. Instead, have
the OID connect to the db through shared memory. This type of
connection is known as a self-service client. In order to do this,
you must make sure that the OIB and the database server have both
been started in the same directory on the server machine. If you have
done this correctly, you will see two log files in your database
directory, <dbname>.lg and prooidrv.lg (this is the OIB/OID log file).
On the Actuate side, you must remove your network connection
parameters from the DatabaseList in the connection dialog.
For example:
Databaselist: -db <database-name> NO PATH or EXTENSION
Removing the network parameters in this manner instructs the OID to
use shared memory rather than TCP when making the connection to the
database.
You still retain the network parameters in the StartUpParameters line
within Actuate. This line is used to tell Actuate where to find the
OIB. Since you have client-networking installed on the client
machine, you are able to use TCP to connect from the client to the OIB
on the server.
For example:
StartUpParameters: -SV -S <broker-port> -H <broker-host> -N tcp
3) Another option is to start the OIB on the client machine. Since
you have client-networking on the client machine, you can use TCP to
connect from Actuate to the OIB and you can use TCP to connect from
the OIB to the database on the server machine.
Note: Among the above options, #2 makes the fastest connection.
Connecting through shared memory is faster than connecting through a
network protocol (i.e. TCP).
If you are sure that you do have client-networking on the server, you
should check to see if you have more than one version/installation of
Progress on that machine. If this is the case, it may be that you
have set PROCFG to point to one of your PROGRESS.CFG files which does
not include client-networking. You can type showcfg at an OS command
line to see which .cfg file you are using and what products are in
that .cfg file.
For more detailed information, see the following knowledgebase
entries:
16794 Connecting to a Progress DB from Actuate Developer Workbench
16723 How to start and stop an OID or an OIB under UNIX
Progress Software Technical Support Note # 17342