Re: Pervasive error in IIS 6.0

Hi Wayne

When I change the port number, I get a timeout. So I guess the port is
open on the webserver, and the communication succeeds. But still the
same error...

Wayne schreef:

Hi Jan,

This is a wild guess: Could this be a firewall issue on the webserver?
The default TCP/IP port for the Pervasive Relational Engine is 1583.
Check your configuration to see what it's currently set at, then check
to see that it's open through your webserver firewall. Or,
alternatively, set the PSQL TCP/IP port to one that is open.

Wayne
Analytica Business Systems, Inc.
www.analyticabiz.com
waynef at theabovedomain dot com
Subscribe to our Pervasive News Feed at:
http://www.analyticabiz.com/rss20.php


jan82 ha scritto:

Hi Bill

I can perfectly ping the database server from the client (webserver in
this case). The weird thing is that I can execute SQL queries on the
datasource on the webserver. The connection seems to work. Only my
web applications return this error, while they DO work on my
development machine. My development machine runs win XP and connects
to the database seemlessly. When I run the PSA, all tests succeed,
except for the "relational" database test. This returns the same
error.

Greetz!

Jan

Bill Bach schreef:

This error indicates that the Pervasive client is trying to connect to
the database server, and it can't seem to find it, or communications
doesn't work. Verify that you can PING the database server by name
from the web server -- if this fails, then you won't have connectivity
at all.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 10/2006 ***

jan82 wrote:

I receive the following error when trying to connect to a Pervasive
database through ODBC:

ERROR [08S01] [Pervasive][Pervasive ODBC Client Interface][Pervasive
ODBC Client Interface][Pervasive ODBC Client Interface LNA]No
available



transport protocol for the Pervasive Network Services Layer.
ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's
SQLSetConnectAttr failed
ERROR [01000] [Microsoft][ODBC Driver Manager] The driver doesn't
support the version of ODBC behavior that the application requested
(see SQLSetEnvAttr).


The application is working fine on my development machine (windows XP
with IIS 5.0 and .NET framework 2) and doesn't work on my web server
(windows server 2003 web edition with IIS 6.0 and .NET framework 2)


Any ideas?

.

Relevant Pages

  • Re: Pervasive error in IIS 6.0
    ... Could this be a firewall issue on the webserver? ... The default TCP/IP port for the Pervasive Relational Engine is 1583. ... the database server, and it can't seem to find it, or communications ... ODBC Client Interface]No ...
    (comp.databases.btrieve)
  • Re: Pervasive error in IIS 6.0
    ... datasource on the webserver. ... the database server, and it can't seem to find it, or communications ... ODBC Client Interface]No ...
    (comp.databases.btrieve)
  • Re: Newbie questions
    ... >> 1) Can I install a piece of firewall software which will only permit ... >> running Linux) to route requests to port 80 to MS-Windows Server? ... cash you have at your disposal, and what other network services your ... have to run a webserver for business read a book and get advice/help from ...
    (comp.security.firewalls)
  • Re: Clarification
    ... >I am writing a webserver for a class project and I need to write one ... >port in rapid succession. ... >communicating with the client is not necc. ... >If firewalls are typically set up to allow outgoing HTTP requests ...
    (comp.security.firewalls)
  • Re: Masqed client cannot access masqed server
    ... >> sharing app and the aforementionned webserver. ... but port 80 connections time out. ... The internal client looks at the destination address and its own address ... then the router no longer drops the packets (check the syslog ...
    (comp.os.linux.networking)