Re: Problem with Pervasive 2000i SP3

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?

Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Pervasive Training - March 2009 in Chicago ***


Thomas Kenyon wrote:
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.
.

Relevant Pages

  • Re: Problem with Pervasive 2000i SP3
    ... a reinstall makes the most sense. ... It sounds like one or more of the engine files got blown away. ... the ODBC connectors stopped working. ... Trying to look at the configuration of the engines in the ODBC Administrator produces "The setup routines for the Pervasive ODBC Engine Interface ODBC driver could not be found. ...
    (comp.databases.btrieve)
  • Re: Replication bandwidth comparison
    ... subjective to hardware, OS, OS configuration, NIC, NIC drivers, network ... >> benchmark, because your conclusions are fatally flawed. ... The merge engine picks up everything ... >> data more than once between synchronization cycles. ...
    (microsoft.public.sqlserver.replication)
  • Re: turbo 4 already dead?
    ... that it doesn't lend itself to be a stressed member of the ... V6 engine design, which would be much easier to adapt from the current ... to its configuration; when Gordon Murray 15 years later fitted a four ...
    (rec.autos.sport.f1)
  • Re: RCS Load Simulators
    ... The SCS was configured to launch configuration, ... The A14-275 quad simulators were connected instead of the RCS ... REACTION CONTROL SYSTEM CONFIGURATION ... The engine simulators were installed in lieu of actual engine ...
    (sci.space.history)
  • Re: Lancair Legacy Design Flaw?
    ... NOT a pusher and the engine is mounted forward of the ...  The weight of the engine on the Legacy is ... involved a tractor configuration with the thrust line being ...
    (rec.aviation.homebuilt)