Thanks for the feedback. A subsequent check did work, although it took 54 seconds - I wonder if my running it manually conflicted with another remote test. I have seen failures of remote file checks (e.g. FileProperties COM) if I am already connected to that machine - it may have a limit on remote connections, or drops connection if another one starts. Richard ----- Original Message ----- From: Jason Passow (mailto:[EMAIL PROTECTED]) To: Servers Alive Discussion List (mailto:[email protected]) Sent: Thursday, November 08, 2007 10:55 AM Subject: Re: [SA-list] Eventlog COM check error - revisited
I check a remote system with many more than 209 entries. Jason Passow Mississippi Welders Supply [EMAIL PROTECTED] ph: (507) 494-5178 fax: (507) 454-8104 "If you do everything right, nobody will realize you've done anything at all." Dirk Bulinckx wrote: Most of our testing was done towards a remote system, so we're sure that is does work. Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sleegers Sent: Thursday, November 08, 2007 4:26 PM To: Servers Alive Discussion List Subject: Re: [SA-list] Eventlog COM check error - revisited Even after reducing the size to 64K, with only 209 events, it takes 39 seconds, then I receive the error: Object variable or With block variable not set. This limits the usability of this COM check for me. Is anyone else successfully using the EventLog COM check against a remote system? Richard On Tuesday, November 06, 2007 3:30 PM, Richard Sleegers <[EMAIL PROTECTED]> wrote: We have had to make our event logs large because an attack can fill up the log with invalid login attempts. However, I saved the log to file, reduced the size, then cleared it. The next attempt was *successful* - Initial check: setting values. So I guess there is a practical upper limit to the event log sizes, and if we need to save historical data, then we'll have to export and clear periodically. Richard On Tuesday, November 06, 2007 1:45 PM, Dirk Bulinckx <[EMAIL PROTECTED]> wrote: 16M is size is HUGE. The API that is used is very slow. If you look at the eventlog via the MS tools it's NOT loading all entries, only part of it. Dirk Bulinckx. ... -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sleegers Sent: Monday, November 05, 2007 11:30 PM To: Servers Alive Discussion List Subject: [SA-list] Eventlog COM check error ERR: COM Check problem (W00000012,122, 350):Object variable or With block variable not set I have checked this thread: http://www.mail-archive.com/[email protected]/msg10077.html but could not see any resolutions there. My specs: Servers Alive 5.1.1967 running as service, no terminal services. Windows 2000 Server SP4 checking event log on remote Windows 2003 Server Web Edition External COM's Eventlog Check setup (version 2.0 build 59): Give down when 'at least one' ... Hostname: [remote server's IP address] Logfile: System Source: EventLog Category: Event ID: 6008 User: Use Authentication: checked, and username has server\username and password fields Type: Error is checked Return: All matching entries Eventlog COM checks on the local network work fine. I have opened all ports 137-139 TCP/UDP for access by the SAlive server If I put an incorrect username or password, the error changes to: External COM check (W00000012,122):ERR: Unable to connect to host.( 7) so I believe the connection information is correct - I can even see increased network activity on the remote server. Any other ideas? --------------------------------------------------- Richard To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
