Hello,

I have a really hard time trying to install PVSW9.1 Server
on a Netware 5.1 SP8 . It seems like a half-baked product right now.

Tech support has been of no help to date. Needless to say
they were sending v.8.6 patches to "help".

PROBLEMS:
- PSA is unable to perform trasactional and relational tests (error
170)
AND
([Pervasive][ODBC Client Interface][Client LNA]The ODBC Client
Interface cannot access the data source because the server could not be
located on the network.). Stress test works OK.
- In PCC I can log to the server but I cannot change anything in
configuration because of various error messages :
* 7004: General failure code - if I try to open Databases
* The currently displayed page contains invalid values - on
Properties/Communication tab
* An error has occured. See error log for more details. - When I try
to hit OK at server properties

To make long story short - PSQL is useless right from the start and its
utilites cannot be used to help it.
So I kindly ask for any assistance in this situation.
I have a lot of bad taste about this product.
My client is angry.
It's my worst experience with Pervasive product to date.

Any help will be appreciated
Thanks
Przem






PS.Server is configured for IPX only.
PS.2.
MY INSTALL PROCEDURE:
- a fresh Netware server
- a PSQL Srvr installation apparently was succesful (no error messages)
- after server reboot it turned out that
A. Install didn't installed core NLM's in F:\SYSTEM because they were
flagged read-only (BTRIEVE.NLM, NWMKDE.NLM etc)
B. PSA,PCC etc. were not working
C. License was not applied even though Setup asked for license code
during installation

Then I did an effort to remove r/o flag from EVERY file on a Netware
server.
Then performed PSQL install again. This time it did replace core NLMs.
I applied license manually.
All NLMs appear to load (except BTCPCOM , there is no TCPIP loaded on
server)

So I am replying to my own post , because I managed to make few steps
further:
1. It turns out that use of TCP/IP is now MANDATORY ,
2. If you want PSA tests to complete, do yourself a favor and remove
manually read-only attributes from files in following directories:
F:\PVSW\SAMPLES and F:\PVSW\DEMODATA - or else you'll get #46 status.



Few more obstacles to pass...



Now I can also see databases in PCC, but cannot manipulate them - after
clicking on DEMODATA for example, I get following error message -
java.io.IOException - could not connect.

Also ODBC access is acting strangely.
Existing System DSN's don't work (DefaultDB and DEMODATA),
however I can create additional DSN , say DEMODATA2, pointing to
DEMODATA , and this time connection is successful.
I cannot delete defunct ODBC DSN's : ODBC error [Component not found in
registry].

All this after a complete install and reboot and reinstall of PSQL9.1
client and another reboot .

Can anyone point me to how to make PCC 9.1 and/or ODBC to work ?
thanks
Przem

The problem is that the old install (that Novell ships) and the new one
don't work well together. This is a sad state of affairs, but one that
I've been trying to get PVSW to fix.

I have been successful in installing to NetWare by removing ALL old
components (via the old NWCLEANUP.BAT file or by simply manually
deleting all of the "right" files). Then, the new install works very
well.

One of the major problems is that the upgrade does NOT replace your
existing DBNAMES.CFG file. As such, you must MANUALLY create the named
databases for the first two databases. This explains why you are
having problems with the two "default" databases. (This IS documented
in the README file, BTW.)

To fix this, you'll need to manually create the Named Database entries.
This can be done with the PCC, which now creates DBNames directly
instead of DSN's. Once you create DEMODATA (pointing to
SYS:PVSW\DEMODATA) and DefaultDB (pointing to SYS:PVSW\SAMPLES), you
should be OK. If you have DSN's that link to these, then try deleting
them (the DSN) and recreating them to point to the new DBName. (Note
that PSQLv9 does NOT require the use of Engine DSN's any more, although
I've found that it is still a good idea to have them. Unfortunately,
most people end up creating an alternate DBName that then links to the
WRONG DSN -- and it ALL gets messed up.) When if doubt, wipe
everything & start from scratch.

Once you have the DefaultDB entry created properly, all should be well
after that.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - November, 2005 ***
*** Chicago: Pervasive DataExchange Class - November, 2005 ***


przemm (AT) poczta (DOT) onet.pl wrote:

Hello,
Thanks for your help.

The problem was , that I wasn't able to do anything in PCC , due to
java.io.IOException error . I did see databases , I couldn't open them.
Solution was to manually add my server to Windows HOSTS file.
say
192.168.0.90 PLWAT

BTW. Where is this NWCLEANUP.BAT located. Can I get this file?
Best regards
Przem

While you could run the nwcleanup.bat file the Pervasive System
Analyzer does a good job of cleaning up.

Leonard

On 24 Aug 2005 23:42:00 -0700, przemm (AT) poczta (DOT) onet.pl wrote:

If it's a part of v9.1 install - it doesn't :-(