I was also experiencing crashes on Windows
2003 Server. I have installed service release 1 beta and so far I haven’t
had any crashes, but my SMTP2POP3COM checks have stopped working.
On the current mailflow checks and any new mailflow checks that I try to
create, I get an error saying “Run-time error ‘430’: Class
does not support Automation or does not support expected interface”.
I have downloaded and installed the SMTP2POP3COM v1.0.0.23 – 25-FEB-2005
off of the free add-ons page and I still get the same errors. Any
ideas? Is there a newer version that I need to install? Thanks, Kris From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx We did several changes last week that we
related to crashes, I would suggest to retest with the version from
http://www.woodstone.nu/salive/sr.asp Dirk. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anoka Hennepin Originally this problem started with the
latest stable release of SA, since then I have upgraded to the lastest beta
release (as of about a week ago), with no improvement in the problem. Seeing as how most people run SA just fine under Windows
2003, I'm assuming my problem is at least partially local to me - still, I
wonder if anybody else has experienced this or has ideas on how I can
track this down. Thanks! - Eric From:
[EMAIL PROTECTED] on behalf of Dirk Bulinckx and what version of SA are you runninG? Dirk. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anoka Hennepin OK, just an update on my last problem. I had been experiencing SA crashes ("Service Terminated
Unexpectedly") while running SA as a service. Here is what I've done
to try and remedy this: 1) Removed McAfee Anti-Virus (just in case the
on-access virus scanner was causing conflicts while SA was writing the log
file). - Still crashed. 2) Disabled screen saver. (It was set to four
hour delay, and it was happening approximately that often, and only after
leaving the machine alone for a while). - Still crashed. 3) Running SA as a process instead of a service.
- Still crashed. 4) Disabling the second computer that I have checking
the SA service (or process) on my SA computer. It was authenticating and
checking every 30 seconds, thought maybe that was causing problems. -
Still crashed. 5) Disabling maximum debug logging on the SA
computer. (SA seemed to be crashing while writing the log file, since the
log file would always be cut off in the middle of a log line). - Still
crashed. HELP!! I'm running 11 URL checks with SA. It loads the URL,
checks for a phrase, and if the check fails it plays a sound and sends out some
e-mails. While it's running, it works perfectly. I have the service
set to restart after a failure, so it even stays running all the time.
It's just irritating not being able to see any worthwhile uptime figures -- by
now my "uptimes" are just an indication of the last time SA crashed. After each check cycle, SA logs to RRD databases, and
executes a batch file that generates a bunch of graphs. From checking the debug log files, it appears that SA
generally crashes towards the END of the check cycle. I have
added/removed/rearranged the URL check order, to determine that it's not
crashing on any particular check, but rather just towards the end of the
cycle. It MIGHT be crashing right after the check cycle (during RRD or
batch file execution), and the log file just doesn't quite get written due to
hard drive caching or something. Just a guess. My only step left is to turn off RRD or the batch file and
see if that solves it. But even if that DOES solve it, I'll still need
help! So I thought I'd notify the listserv group and see if Dirk or
anybody else has ideas. The second computer I have checking the SA computer never
crashes. It's running XP Pro SP 2. I was also thinking of
installing XP Pro instead of Server 2003 on the SA computer to see if that
makes a difference. Any ideas?!? Thanks in advance!! |
- RE: [SA-list] Still Crashing with Windows 2003 Server! Kris Jacobs
- RE: [SA-list] Still Crashing with Windows 2003 Server! Dirk Bulinckx