Title: Message
Hi
Matt:
While
I was beta testing 2.0.6, I was also suffering from some distributed dictionary
attacks - and I was scrutinizing the log files much more closely (to look for
possible beta errors).
I
don't know WHICH of these three factors were critical (2.x vs. load vs.
Title: Message
Andy,
Thanks for the information. There is no doubt that you could limit the
processes and never reach this overloaded condition and that would mask
the issue, and gateway validation should also prevent overloaded
conditions if you were formerly being bombarded. What I'm
I submitted a support ticket this morning about problems I seen under 2.0.6
with high load. This weekend while doing some maintenance I ran into some
load issues when I brought one of the servers down I maintain. When I bring
one of the servers offline I know the other server will start dropping
Matt,
I had this same exact issue, with exact same
symptoms(Win 2000 SP4) and I called Declude on it a few weeks ago.
Eventually, I just copied in a new Declude 1.82.exe file and reinstalled my
scanners and the issue went away. I saw the same Error starting scanner
and the Error 183. I
FYI: I've running v1.82 on a Win2003 server and since SP1 is installed I've
had problems multiple times with the queue manager and also popup messages
for declude.exe. One problem could be the new SP1 application execution
protection.
This problem appears only some days but can also happen
Markus et. al,
This is my first full day on SP1, but I have seen double processing
before in D files stranded in the spool going back maybe a year or more
and on Win2K as well. I was only able to nail this down to a load
issue because the 1:30 a.m. mailing is a daily occurrence and I see
