Newbie - Trouble getting client/host connection to database 
Author Message
 Newbie - Trouble getting client/host connection to database

I am having trouble setting up a database to be accessed across a
simple TCP network. On the database host, I have started the proserver
as described in "Installation and Configuration Guide v9 for Windows":
-

proserve <db-location> -S myservice -H localhost -N TCP

and added the line, "myservice     20391/tcp" to  
"..\WINNT\system32\drivers\etc\services" file

However, when running the following command

prowin32 <UNC-db-location> -p <UNC-procedure-file.r> -S myservice -H
192.168.0.2 -N TCP

on the client machine, I get the error: "** Could not connect to
server for database <db-location>, errno 0. (1432)"

I am using two Windows 2000 machines with ProVision and Client
Networking installed (v 9.1C). They ping eachother fine. Am I missing
something really obvious or do I need to install something extra?! Any
help will be greatly appreciated!

Paul



Sat, 02 Jul 2005 04:20:21 GMT
 Newbie - Trouble getting client/host connection to database


Quote:
> I am having trouble setting up a database to be accessed across a
> simple TCP network. On the database host, I have started the proserver
> as described in "Installation and Configuration Guide v9 for Windows":
> -

> proserve <db-location> -S myservice -H localhost -N TCP

> and added the line, "myservice     20391/tcp" to
> "..\WINNT\system32\drivers\etc\services" file

> However, when running the following command

> prowin32 <UNC-db-location> -p <UNC-procedure-file.r> -S myservice -H
> 192.168.0.2 -N TCP

> on the client machine, I get the error: "** Could not connect to
> server for database <db-location>, errno 0. (1432)"

> I am using two Windows 2000 machines with ProVision and Client
> Networking installed (v 9.1C). They ping eachother fine. Am I missing
> something really obvious or do I need to install something extra?! Any
> help will be greatly appreciated!

> Paul

-H is not required on the server. It always asssumes 'localhost'. Also, -N
is no longer required on either client or server as TCP is the default
protocol.

Did you  add the service entry on the client as well?? Try using the Port
number as opposed to the service name.

For the client connection string, change "<UNC-db-location>" to just the
physical name of the database. Progress will use the TCP port to communicate
with the broker for the connection.

Kevin



Sat, 02 Jul 2005 16:44:23 GMT
 Newbie - Trouble getting client/host connection to database

Originally posted by Kevin

Quote:



> > I am having trouble setting up a database to be accessed across
>     a
> > simple TCP network. On the database host, I have started the
>     proserver
> > as described in "Installation and Configuration Guide v9 for
>     Windows":
> > -
> > proserve  -S myservice -H localhost -N TCP
> > and added the line, "myservice     20391/tcp" to
> > "..\WINNT\system32\drivers\etc\services" file
> > However, when running the following command
> > prowin32  -p  -S myservice -H
> > 192.168.0.2 -N TCP
> > on the client machine, I get the error: "** Could not connect
>     to
> > server for database , errno 0. (1432)"
> > I am using two Windows 2000 machines with ProVision and
>     Client
> > Networking installed (v 9.1C). They ping eachother fine. Am I
>     missing
> > something really obvious or do I need to install something
>     extra?! Any
> > help will be greatly appreciated!
> > Paul

> -H is not required on the server. It always asssumes 'localhost'.
> Also, -N
> is no longer required on either client or server as TCP is the default
> protocol.

> Did you  add the service entry on the client as well?? Try using
> the Port
> number as opposed to the service name.

> For the client connection string, change "" to just the
> physical name of the database. Progress will use the TCP port to
> communicate
> with the broker for the connection.

> Kevin

Thanks for your post, Kevin.

I have made the changes you suggested but get exactly the same error
message, "** Could not connect to server for database db-name, errno
0. (1432)"

SERVER: proserve [db-location] -S mysrv
CLIENT: prowin32 -db [db-name] -p [UNC-procedure-file.r] -S mysrv -H
192.168.0.2

I have also tried replacing "mysrv" with the port number as specified in
the winnt\driver\etc\services file (on both server and client).

However, when invoking the server, it gives the line "BROKER  0: This
server is licenced for local logins only. (4393)".
Do I have to get Server Networking AS WELL as Client Networking and
ProVision ?!

--
Posted via http://dbforums.com



Sat, 02 Jul 2005 21:33:42 GMT
 Newbie - Trouble getting client/host connection to database
Paul,

Start database on server with:

proserve C:\databases\mysports.db -N tcp -S mysrv

Start client:

prowin32.exe -db mysports.db -N tcp -S mysrv -H <hostname-of-server> -p
<startup-procedure>

(Maybe is the -p parameter between in -db and the -N causing that Progress
does not know
where to find the DB. So keep the -db and the -N/-S/-H parameters together)

Martin



Quote:
> I am having trouble setting up a database to be accessed across a
> simple TCP network. On the database host, I have started the proserver
> as described in "Installation and Configuration Guide v9 for Windows":
> -

> proserve <db-location> -S myservice -H localhost -N TCP

> and added the line, "myservice     20391/tcp" to
> "..\WINNT\system32\drivers\etc\services" file

> However, when running the following command

> prowin32 <UNC-db-location> -p <UNC-procedure-file.r> -S myservice -H
> 192.168.0.2 -N TCP

> on the client machine, I get the error: "** Could not connect to
> server for database <db-location>, errno 0. (1432)"

> I am using two Windows 2000 machines with ProVision and Client
> Networking installed (v 9.1C). They ping eachother fine. Am I missing
> something really obvious or do I need to install something extra?! Any
> help will be greatly appreciated!

> Paul



Sun, 03 Jul 2005 04:26:31 GMT
 Newbie - Trouble getting client/host connection to database
Thanks Martin,

I have tried grouping together the network parameters as you
suggested, but again still the same error messsage!

Should I be concerned about the line "BROKER  0: This server is
licenced for local logins only. (4393)" when the server is invoked, or
doesn't this matter?

Is there any other way of connecting across a network? I have
ProVision v9.1C and Client Networking installed. PLEASE HELP!

Paul

Quote:

> Paul,

> Start database on server with:

> proserve C:\databases\mysports.db -N tcp -S mysrv

> Start client:

> prowin32.exe -db mysports.db -N tcp -S mysrv -H <hostname-of-server> -p
> <startup-procedure>

> (Maybe is the -p parameter between in -db and the -N causing that Progress
> does not know
> where to find the DB. So keep the -db and the -N/-S/-H parameters together)

> Martin



> > I am having trouble setting up a database to be accessed across a
> > simple TCP network. On the database host, I have started the proserver
> > as described in "Installation and Configuration Guide v9 for Windows":
> > -

> > proserve <db-location> -S myservice -H localhost -N TCP

> > and added the line, "myservice     20391/tcp" to
> > "..\WINNT\system32\drivers\etc\services" file

> > However, when running the following command

> > prowin32 <UNC-db-location> -p <UNC-procedure-file.r> -S myservice -H
> > 192.168.0.2 -N TCP

> > on the client machine, I get the error: "** Could not connect to
> > server for database <db-location>, errno 0. (1432)"

> > I am using two Windows 2000 machines with ProVision and Client
> > Networking installed (v 9.1C). They ping eachother fine. Am I missing
> > something really obvious or do I need to install something extra?! Any
> > help will be greatly appreciated!

> > Paul



Sun, 03 Jul 2005 19:21:49 GMT
 Newbie - Trouble getting client/host connection to database


Quote:

> Thanks for your post, Kevin.

> I have made the changes you suggested but get exactly the same error
> message, "** Could not connect to server for database db-name, errno
> 0. (1432)"

> SERVER: proserve [db-location] -S mysrv
> CLIENT: prowin32 -db [db-name] -p [UNC-procedure-file.r] -S mysrv -H
> 192.168.0.2

> I have also tried replacing "mysrv" with the port number as specified
> in the winnt\driver\etc\services file (on both server and client).

> However, when invoking the server, it gives the line "BROKER  0: This
> server is licenced for local logins only. (4393)".
> Do I have to get Server Networking AS WELL as Client Networking and
> ProVision ?!

> --
> Posted via http://dbforums.com

That error means that you only have Provision installed on the 'server'.
You must have Enterprise or Workgroup DB in order to accept connections
from a remote client.

If you did install Enterprise or Workgroup, double check your
progress.cfg file, and be sure that the products you think you have, are
actually installed. If you installed Provision after one of the DB
products, then the CFG file get's overwritten, unless you used the 'Add
Components' utility (%DLC%\setup.exe -addcomp).

Kevin



Mon, 04 Jul 2005 00:16:21 GMT
 Newbie - Trouble getting client/host connection to database
Did yout try to start the server with Procontrol service
utility?
You can find it in contol panel.
Insert ...
In General section:
-Chose the database
-define the startup parameters such as protocol(-N), host(-H), service(-S)
and so on
(as host name choose the name of local host)

In DBWriters section you can check Before image writer
and Watchdog process

In Enviroment section set
ACCESS=ALL

In Services in Control panel set the procontrol service
to start automatically on boot.

In Services file define the tcp port somewhere on the
first free position above 2500 (isn't your port 20391
too high a bit?). Of course, you have to do it on both
sides - server and clients.

On the client computer try to define(besides services) in
Hosts file (same folder as Services) host,
of course in case that your server has a static IP adress
Add line
(IP-address-of-server)  (host-name-of-server)
it's not so necessarily but but with this, line the time of
connection is shorter.

Try to not use "TAB" in Services and Hosts files.
Use only spaces.

And finally, as you know allready, try to connect to server
database form client computer with:

prowin32 -p (proc-file.r) -db (db-name) -H
(computer-local-name-of-dbserver) -N tcp -S (service-name)

As a db-name you can use only logical name of database.

One thing, maybe  important:
If you put this line in shortcut with a starting directory on host(server)
machine cou can try to use predefined maped drive for example P:\...
If you use full path, use "\",  not "/"   as follows
\\server-name\shared-folder\
I wrote one time(by mistake) in startup directory of a shortcut
the full path with a "/" (//server-name/...) and got exactlly the
same error message as you are.

Thats all I can say from my experience.
Try it.
Good luck

Boris


Quote:
> I am having trouble setting up a database to be accessed across a
> simple TCP network. On the database host, I have started the proserver
> as described in "Installation and Configuration Guide v9 for Windows":
> -

> proserve <db-location> -S myservice -H localhost -N TCP

> and added the line, "myservice     20391/tcp" to
> "..\WINNT\system32\drivers\etc\services" file

> However, when running the following command

> prowin32 <UNC-db-location> -p <UNC-procedure-file.r> -S myservice -H
> 192.168.0.2 -N TCP

> on the client machine, I get the error: "** Could not connect to
> server for database <db-location>, errno 0. (1432)"

> I am using two Windows 2000 machines with ProVision and Client
> Networking installed (v 9.1C). They ping eachother fine. Am I missing
> something really obvious or do I need to install something extra?! Any
> help will be greatly appreciated!

> Paul



Mon, 04 Jul 2005 03:00:44 GMT
 Newbie - Trouble getting client/host connection to database

Quote:
> Did yout try to start the server with Procontrol service
> utility?
> You can find it in contol panel.
> Insert ...
> In General section:
> -Chose the database
> -define the startup parameters such as protocol(-N), host(-H),
> service(-S) and so on
> (as host name choose the name of local host)

> In DBWriters section you can check Before image writer
> and Watchdog process

> In Enviroment section set
> ACCESS=ALL

> In Services in Control panel set the procontrol service
> to start automatically on boot.

> In Services file define the tcp port somewhere on the
> first free position above 2500 (isn't your port 20391
> too high a bit?). Of course, you have to do it on both
> sides - server and clients.

20931 is perfectly fine.. I currently use 25000, 26000 & 27000 in my
services file.

- Show quoted text -

Quote:

> On the client computer try to define(besides services) in
> Hosts file (same folder as Services) host,
> of course in case that your server has a static IP adress
> Add line
> (IP-address-of-server)  (host-name-of-server)
> it's not so necessarily but but with this, line the time of
> connection is shorter.

> Try to not use "TAB" in Services and Hosts files.
> Use only spaces.

> And finally, as you know allready, try to connect to server
> database form client computer with:

> prowin32 -p (proc-file.r) -db (db-name) -H
> (computer-local-name-of-dbserver) -N tcp -S (service-name)

> As a db-name you can use only logical name of database.

Actually, as db-name, you can only use physical name. Logiacl db-name is
available through the -ld parameter.

- Show quoted text -

Quote:

> One thing, maybe  important:
> If you put this line in shortcut with a starting directory on
> host(server) machine cou can try to use predefined maped drive for
> example P:\... If you use full path, use "\",  not "/"   as follows
> \\server-name\shared-folder\
> I wrote one time(by mistake) in startup directory of a shortcut
> the full path with a "/" (//server-name/...) and got exactlly the
> same error message as you are.

> Thats all I can say from my experience.
> Try it.
> Good luck

> Boris



Mon, 04 Jul 2005 03:55:12 GMT
 
 [ 8 post ] 

 Relevant Pages 

1. REQ: Trouble Hosting Database on Windows Peer to Peer

2. Remote client connection with host lost over and over again

3. Getting an SQL database hosted

4. Getting database to a hosted web site?

5. Trouble Getting Database on CE Device

6. Trouble getting reports from other databases to enter into a master report

7. Connection from client doesn't gets disconnected after task

8. Can Win Client open Mac Client-hosted db?

9. Database connection with embeddedSQL and C as host

10. (newbie) having trouble installing Red Hat Database

11. Database connection with embeddedSQL and C as host


 
Powered by phpBB® Forum Software