And does it do this towards all systems?
Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of steve Sent: Friday, January 13, 2006 8:53 PM To: [email protected] Subject: [SA-list] V2 build 55 eventlog check problem I'm having some odd issues with v2 build 55 of the External COM check event log checker. When the check is run it just sits there i.e. longer than 10 minutes (much slower than V1). It seems that the image name in my task manager COMSAW~1.exe uses up 50% of my CPU and just hangs there until I kill it. I'm certain that my login data is correct, when I deliberately miss type the login error "ERR: Unable to connect to host.(7)" results. After Killing the process I also notice that the check was successful, so I wonder if the check it self is having trouble closing it self down. I'm running SA on Windows 2000, but I intend to run the check on Windows server 2003 once I figure out what to do about this issue. The machine that is being checked is also Windows server 2003 Any thoughts would be greatly appreciated. Steve ________________________________________________________________ Sent via the WebMail system at mail.gawd.net To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
