Hi David,
I was wondering...
You said SA is running as a service, using the admin login. Is this the
admin login for the local machine (running SA) or for a domain. When you run
the BAT manually, are you logged in with the same account that SA is using?
I'm thinking there's possibly a rights issu
OK - this is frustrating. When I first upgraded and did some tests with the
alert command thing, it worked. Now it isn't. Here is the log and the
configuration I have - and this is with the latest BETA installed:
I have it setup for device EMSPRO to email me and run a command when down
and when
installed directly on the system and rebooted afterwards.
Dave
- Original Message -
From: "Dirk Bulinckx" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 31, 2004 3:21 PM
Subject: RE: [SA-list] Command Alerts
How did you install? Directly on the system or via TS sessi
How did you install? Directly on the system or via TS session?
Did you reboot after the install?
s
Dirk.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of David Bruck
Sent: Sunday, October 31, 2004 9:06 PM
To: [EMAIL PROTECTED]
Subject: Re: [SA-list] Com
Dirk,
I installed the new beta version...
Everytime the service starts now, I get this error:
"ActiveX Component can't create object ( 429) on line 0"
It appears to run okay though. Now I will go do more testing with the Alert
Commands...
Dave Bruck
- Original Message -
From: "Dirk
Try running it with the latest beta build (http://beta.woodstone.nu) it
includes logging when the command is executed.
Dirk.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of David Bruck
Sent: Sunday, October 31, 2004 4:54 PM
To: [EMAIL PROTECTED]
Subject
Alistair,
Running it as a service using the admin login account.
Path is c:\mainton.bat
Dave
- Original Message -
From: "Alistair Francis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 28, 2004 1:53 AM
Subject: RE: [SA-list] Command Alerts
Hi David,
Are you runn
The port is open IF you use TCP syslog logging. However most syslog logging
devices (devices/apps that log towards syslog) are not able to use TCP and
use the "old" RFC define UDP logging. And in UDP there is no open port that
you can realy check.
Dirk.
_
From: [EMAIL PROTECTED]