Subject | Re: [ib-support] Periodical Server Crashes (from Firebird-Java) |
---|---|
Author | Christian Gütter |
Post date | 2002-10-24T08:30:56Z |
Hi Roman,
when you take a look at
http://www.eventid.net/display.asp?eventid=2019&source=
you will see that the error 2019 can be caused by many
other reasons:
- Under certain circumstances, heavy usage of particular programs can
cause non-paged pool memory to become
exhausted. This can happen due to various reasons. Some of these
problems are fixed by Windows 2000 Service Pack
2.
- As per Microsoft: "This behavior can occur because the kernel-mode
tag, Dynamic Access Protocol version 4 (DAP4),
is leaking memory. This tag is provided by 3Com. The tag is a driver
that is loaded into the computer for the 3Com
3C980C-TXM network adapter.". See Q294346
- In Microsoft Small Business Server 2000 the windows proxy service
leaks memory when a USRobotics PCI 56K faxmodem
is installed with the drivers from the box. On a system with 512meg of
ram it takes about 15 hours for the #
nonpaging pool to be exhausted. Downloading updated drivers from the
USR web site seems to fix the problem.
- See Q317249 on how to troubleshoot this type of events as they
typicall occur when the Server service cannot
process the requested network I/O items to the hard disk quickly
enough to prevent the Server service from running
out of resources.
- See Q130926 - Using Performance Monitor to Identify a Pool Leak
The issue is adressed by the following articles of the MS knowledge
base:
Q296265 , Q272568 , Q293841 , Q272194 , Q289209 , Q221926 , Q294346 ,
Q130926 , Q317249.
The person who contacted you should take a look at these articles,
because one of them might describe a problem his configuration
oder server software has.
HTH,
Christian
when you take a look at
http://www.eventid.net/display.asp?eventid=2019&source=
you will see that the error 2019 can be caused by many
other reasons:
- Under certain circumstances, heavy usage of particular programs can
cause non-paged pool memory to become
exhausted. This can happen due to various reasons. Some of these
problems are fixed by Windows 2000 Service Pack
2.
- As per Microsoft: "This behavior can occur because the kernel-mode
tag, Dynamic Access Protocol version 4 (DAP4),
is leaking memory. This tag is provided by 3Com. The tag is a driver
that is loaded into the computer for the 3Com
3C980C-TXM network adapter.". See Q294346
- In Microsoft Small Business Server 2000 the windows proxy service
leaks memory when a USRobotics PCI 56K faxmodem
is installed with the drivers from the box. On a system with 512meg of
ram it takes about 15 hours for the #
nonpaging pool to be exhausted. Downloading updated drivers from the
USR web site seems to fix the problem.
- See Q317249 on how to troubleshoot this type of events as they
typicall occur when the Server service cannot
process the requested network I/O items to the hard disk quickly
enough to prevent the Server service from running
out of resources.
- See Q130926 - Using Performance Monitor to Identify a Pool Leak
The issue is adressed by the following articles of the MS knowledge
base:
Q296265 , Q272568 , Q293841 , Q272194 , Q289209 , Q221926 , Q294346 ,
Q130926 , Q317249.
The person who contacted you should take a look at these articles,
because one of them might describe a problem his configuration
oder server software has.
HTH,
Christian