Since changing our internal Server to Windows2003 we are seeing a lot of
problems with PSQL2000 SP4 and our internal Clarion applications. Are there
any known problems with Win2003 Server and PSQL 2000i SP4?
Switching back to Win2000 Server makes everything work fine ...

Which Pervasive SQL engine is 100% compatible with Win2003 Server? Should we
wait for V9?

Steven Sitas

I don't know of any actual problems.
Many times there are configuration issues.
Security too tight is common, although Pervasive does not really need
"relaxed" security, just that the service installed as the system
account have read + execute rights to the \pvsw\bin folder and full
control to the \pvsw\bin\mkde\log folder. Whatever account the
service is run as will also need the correct rights to the data files.
Also common is trying to administer it through a Terminal server
session. That usually does not work (usually at all) or well.
Administering it from the console works just fine though.

If it is not the above could you be a little more specific about the
"problems" being experienced for more specific help.

Leonard

On Tue, 1 Feb 2005 22:25:20 +0200, "Steven Sitas" <tspeed (AT) otenet (DOT) gr>
wrote:

Hello,
Our Clarion application from time to time STOPs responding.
Killing the application returns everything to normal ...

It happens when the applications windows OPEN the Btrieve files.
Sometimes if you wait a little (say a minute) the application "returns to
normal" by itself.
It looks like Pervasive STOPs responding for sometime.

Our Clients are WindowsXP SP1 and as I said this doesnt happen with Win2000
but happens with SMB Server (Win2003)

Steven Sitas


? "Leonard" <lharvey (AT) austin (DOT) rr.com> ?????? ??? ??????
news:3nk001p4oi6k9c543353baa82860hp9fta (AT) 4ax (DOT) com...

From what it sounds like after the delay on the first open everything
runs normally.

A "Not Responding" from the OS simply means that it has asked the
application for a status and did not get one within a small waiting
period. This usually happens when the application has made network
calls to the OS as they are "blocking" and do not return control to
the application until it is finished. Waiting is probably the safest
thing to do as everything completes normally eventually.

How long does a "ping <server_name>" take between the enter key and
sending the first request?
Does "ping <server_name>" return server_name or does it return
server_name.domain?
Perhaps a hosts file entry is all it would take to fix it up.

Is the Clarion application transactional or ODBC based?
If it is ODBC based what hapens if you change the client DSN to the IP
address of the server as opposed to the server_name?
If it is transactional and uses a mapped drive, what happens if you
map the drive to the server IP address instead of the name?

There is a diagnostic utility with Pervasive.SQL 2000i called Smart
Scout. It is easiest to just do a Start -> Run -> sscout32 and hit
enter. Go to the 3rd tab "Network Tests" if I remember correctly. If
you use a drive mapping put the drive letter into the "Target" address
then hit run. If you use ODBC use a UNC formatted target of
\\server_name. It may turn up something.

And as a funny side note, MS Windows name resolution usually does not
like an underscore "_" in a server name. Also known to cause the
database requesters problems is starting a server name with a number.

Leonard

On Wed, 2 Feb 2005 11:06:46 +0200, "Steven Sitas" <tspeed (AT) otenet (DOT) gr>
wrote:

Hello Leonard,

thanks for the Information

Steven Sitas

? "Leonard" <lharvey (AT) austin (DOT) rr.com> ?????? ??? ??????
news:dl83019fn63irjvfhgljjc5oskpg9m05e8 (AT) 4ax (DOT) com...