Re: help with 2000i on win2k server (sp3 on database)
- From: "Bill Bach" <goldstar@xxxxxxxxxxxxx>
- Date: Sun, 05 Feb 2006 10:26:11 -0600
I agree with only having TCP -- this is by far the most preferred
protocol, especially for Windows.
See Leonard's post for the config options.
If the server is mangling itself, then ANYTHING running on the server
can get corrupted -- DLL's, EXE's, databases, Word Docs, etc. If the
server is unstable, it should be replaced as soon as possible.
Continuing to run will be like building your house on sand -- it may
work fine for a while, but one strong wind and it will collapse quickly.
As for AMSI support policy, this is quite unfortunate, as most vendors
that I work with will support the database AND the application.
However, some have chosen to distance themselves, because of limited
time or limited skill set -- there is a reason why companies such as
ours (providing support for JUST the database, regardless of the
application) exist and thrive. Perhaps they are just too busy to get
involved with something that will be a protracted error. Of course,
this is only an explanation -- not an excuse, especially for a company
that sells their application to people for use in critical services.
As for Windows vs. Linux/NetWare, I can agree, but I also see MANY
sites running Windows nowadays, and most successfully. I also worked
with a company in Australia recently that had a physical problem on
their NetWare server -- and it caused major file corruption in numerous
files. Bad hardware will mangle the data on any OS. It's just a mater
of using the best tool for the job.
On your original post, you also asked about rebuilding indices. This
is NOT required from Pervasive, but you can do so if you wish. Use the
Rebuild Utility (if the files are NOT damaged), or the BUTIL Recover
process (if they are damaged). For instructions on BUTIL, see our
white papers at www.goldstarsoftware.com/press.asp for the one on File
Maintenance and another on using Rebuild.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Sydney: Pervasive.SQL Service & Support Class - 02/27/06 ***
*** Chicago: Pervasive.SQL Service & Support Class - 03/27/06 ***
h0u wrote:
Thank you for the reply,
How can I get an output list of all the settings in the control
center? I'd have to write a lot of things down here to get all the
settings. I see where it's looking for multiple protocols (ipx,
ms_spx and tcp/ip). They only use tcp/ip. I assume it would be safe
to have only tcp/ip as the protocol. Would you agree?
Also, is there a text config file for all the stuff in control center?
I guess I'm biased to text config files instead of GUI-based stuff.
Tomorrow I'll look for the 2 files you pointed out.
One other thing, this was working fine for a while. But lately, the
windows server seems to be going downhill (it's getting corrupt). In
your experience, how does this affect pervasive?
The accountant (using the AMSI software) had done closes for 2005 and
they were fine. But around the 19 or 20 of January, there was a hard
server crash. After that, she can't get into the 2005 closes anymore
and all these problems started happening. AMSI uses pervasive as its
database.
I called AMSI and they said they have nothing to do with this problem
- the problem is the database! I'll make sure to remember to never
recommend that vendor! Every other vendor I've worked with supports
their application and the database they chose to write their
application to!
This only proves my opinion that for running anything important, it
should NOT be run on windows. I'm sure you've seen corporate
datacenters. Almost all the ones I've worked at use unix (now linux)
or novell to run anything important. Whatever is left over (that
isn't too important) can run on windows. This case is a text-book
example.
Thank you,
Oskar
Bill Bach wrote:
There isn't much of value in the Event log -- you are getting some
10047 errors, which Microsoft defines as:
10047 WSAEAFNOSUPPORT Address family not supported by protocol
family This can be caused by the NIC on the server going to sleep.
A much more likely issue is that the config is not up to snuff, as
you suspected. It would be helpful if you could post the
configuration data from the PCC on the server.
It is also very likely that you are simply getting conflicts between
multiple database engines. The data in the BTI.INI file that you
submitted indicates that a very old version of Macola was on this
box -- one that came with a Btrieve 6.15 Workstation Engine. It
may be as simple as some workstations finding an old 6.x engine
instead of using the new one. Scour your systems (including the
server) for the files WBTR32.EXE or W32MKDE.EXE -- the old 6.x
engines -- and rename them where you find them. This will help
ensure that all files are opened with the server engine.
Your other problem may be within the Windows Named Pipes calls,
resulting in the Status 3119. While there are several causes for
this, one of the bigger one is due to bugs in the engine. Please
be sure that you have patched the server to Pervasive.SQL 2000i
Service Pack 4 AND the SP4 HotFixes. Then, assuming the clients
arer all SP3 already, update them with the Client HotFixes as well.
This may help.
Other issues could be related to anti-virus software (an old
version of McAfee used to cause 3119's) and similar problems.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Sydney: Pervasive.SQL Service & Support Class - 02/27/06 ***
*** Chicago: Pervasive.SQL Service & Support Class - 03/27/06 ***
sed
.
- References:
- Prev by Date: Re: Strang behavior of Backup-Agent 1.0
- Next by Date: Re: Pervasive SQL - Timeout
- Previous by thread: Re: help with 2000i on win2k server (sp3 on database)
- Next by thread: Strang behavior of Backup-Agent 1.0
- Index(es):
Relevant Pages
|
|
