Did this article resolve your question/issue?



"[DataDirect][ODBC PROGRESS driver][PROGRESS] Error in Network Daemon" error with Progress ODBC driver

« Go Back


Title"[DataDirect][ODBC PROGRESS driver][PROGRESS] Error in Network Daemon" error with Progress ODBC driver
URL Name3030
Article Number000143989
EnvironmentProduct: Connect for ODBC Progress driver
Version: 4.1, 4.2
OS: Windows
Database: Progress 9.1E
Application: all supported applications
Question/Problem Description

The below error is received when connecting.

Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC PROGRESS driver][PROGRESS] Error in Network Daemon
Defect/Enhancement Number

Some of the reasons for this error message are:

1.> Connecting to a database version which is NOT supported. e.g. connecting via the Connect 4.2 driver for ODBC for PROGRESS (9) to Progress 9.1A and older or to a PROGRESS OpenEdge 10.0A.

2.> The PROGRESS database picks up a wrong copy of the Java Virtual Machine. Make sure to install the PROGRESS recommended version of the JVM/JDK and that the PROGRESS database actually picks up this version. (e.g. JVM 1.3.0_02 is required for PROGRESS 9.1D on Red Hat Linux 7.1). Check the version of the Java Virtual machine by executing the command: java -version

3.> The PROGRESS Database Server service has not been started, or has been started with _mprosrv. Make sure to start the PROGRESS database server service (after checking that the DLC/PROMSGS environment variables have been set correctly) by using the command proserve databasename.db -N xx -S xx -H xx

4.> The PROGRESS Database Server may not support SQL92 connections (e.g. there is no SQL-92 RDBMS on DG/UX Intel, SCO OpenServer & Solaris Intel platforms, and only SQL89 connections are supported with the Connect 4.0 driver for ODBC for Progress).

5.> Hostname resolves to wrong IP-address or does not resolve at all. In this case, specify the IP address as host name.

6.> The wrong port number is specified. Make sure to specify the correct port number in the ODBC data source. This should point to the TCP port number on which the PROGRESS database server service is started.


If the PROGRESS database server service is started as follows:

 proserve -db theDatabase.db -N TCP -H thehost -S theServiceName

where theServiceName is specified in the etc/services file as follows:

 theServiceName xxxxx/tcp  

(note: where xxxx should be a valid TCP/IP number below 65536, like 1234)
(note: specify '/tcp', not '/udp')

then you must specifiy

 xxxxx (eg: 1234)

7.> You may have run out of remote servers on the database. If the 4GL remote clients are using all of the remote servers then the database can't serve SQL-92 clients. You may have to set up a secondary login broker to attend SQL-92 connections.

8.> The firewall (e.g. Zone Alarm,..) may be blocking access. Check with the system administrator to monitor network traffic.

Last Modified Date6/2/2016 10:48 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.