Problem with Pervasive 2000i SP3

Thomas Kenyon

unread,

Feb 10, 2009, 3:52:13 AM2/10/09

to

We inherited an in house database which uses Pervasive 2000i SP3 running
on NT4 as a back end.

I'm more used to Postgresql running on Linux, so I may need help in
posting all the relevant information.

Recently, the ODBC connectors stopped working (and the ones running on
the host can't use ADO because I haven't got SP4).

Remote ODBC clients and local ones (ODBC Engine Interface) fail.

Trying to browse the Databases in Control Center produces
"[Pervasive][Pervasive ODBC Client Interface][Pervasive ODBC Client
Interface LNA]Connection attempt timed out. The SQL Connection Manager
may be inactive or using a different transport protocol from the client."

Trying to look at the configuration of the engines in the ODBC
Administrator (from control panel) produces "The setup routines for the
Pervasive ODBC Engine Interface ODBC driver could not be found. Please
reinstall the driver.".

An ASP script that uses it produces

"Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified"

netstat shows that both 3351 and 1058 are listening and there is no
firewall configured.

PVSW.log consists of lots of lines stating Resources allocated and
Resources released.

I have tried almost everything I can think of, on the weekend I will
have some downtime with the server so can try uninstalling and
reinstalling pervasive.

I don't know where to get SP4 or any of the Hotfixes, so I haven't tried
that route yet.

According to my notes I also had these errors along the way (not sure
where).

"Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed"
"The SQL Connection MAnager may be inactive or using a different transport"
"ODBC Error: SQLSTATE = 08S01, Native error code = 10013"

I am almost at wits end with this, any help would be greatfully received.

BtrieveBill

unread,

Feb 11, 2009, 5:15:03 PM2/11/09

to

It sounds like the engine itself is shut down. A quick reboot is the
first/best option, to see if that helps. Otherwise, a reinstall makes
the most sense. It sounds like one or more of the engine files got
blown away.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
Bill...@goldstarsoftware.com
http://www.goldstarsoftware.com
*** Pervasive Training - March 2009 in Chicago ***

Thomas Kenyon

unread,

Feb 12, 2009, 4:32:50 AM2/12/09

to

BtrieveBill wrote:
> It sounds like the engine itself is shut down. A quick reboot is the
> first/best option, to see if that helps. Otherwise, a reinstall makes
> the most sense. It sounds like one or more of the engine files got
> blown away.

Thanks, will try a reinstall over the weekend.
The engine is up (and reboots don't help). The databases can still be
accesses through btrieve.

Do you know anywhere I can get the SP4 update?

BtrieveBill

unread,

Feb 12, 2009, 9:56:29 AM2/12/09

to

Thomas Kenyon wrote:
> Do you know anywhere I can get the SP4 update?
>

Try this:
http://www.goldstarsoftware.com/patches2k.asp

Thomas Kenyon

unread,

Feb 14, 2009, 2:49:00 AM2/14/09

to

Thanks, reinstalling seems to have fixed it, although it has broken IIS
and stopped NT from starting, but one problem at a time :-).