If there is an alert for a TEAM and the convertion of the TEAM becomes empty (talking about mail alerting now) because of an unactive team OR an unknown team, then we do log "Didn't send mail (TO part is empty)" I would have been good to have an alert that is set to ALWAYS (that way we are sure that the alert does fire) and see if that logged anything.
Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Stout, Josh Sent: Tuesday, February 19, 2008 9:26 PM To: Servers Alive Discussion List Subject: RE: [SA-list] SA 6.x Teams fail to function There are no alert entries in the logfile. The system is simply not sending out any alerts. All of our alerts are sent by groups (e.g. {Citrix Administrators}) if groups fail then the system does not see any recipients and does not attempt to send any alerts at all. But, if I replace {Citrix Administrators} with (josh stout) then an alert is generated and everything works fine. So no, no logfile entries other than server monitoring events. Josh Stout -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Tuesday, February 19, 2008 3:06 PM To: Servers Alive Discussion List Subject: RE: [SA-list] SA 6.x Teams fail to function Have you checked the logfile to see if it shows any type of error around the sending? Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Stout, Josh Sent: Tuesday, February 19, 2008 7:41 PM To: Servers Alive Discussion List Subject: RE: [SA-list] SA 6.x Teams fail to function Checked that. They're active. Josh Stout -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Trevor MacDougall Sent: Tuesday, February 19, 2008 1:36 PM To: Servers Alive Discussion List Subject: Re: [SA-list] SA 6.x Teams fail to function Silly question. Have you checked that the teams are set to "Active"? I only ask because I've had that problem before where I would create a new team and it is set non-active. Trevor Stout, Josh wrote: > I'm not able to isolate the cause of our problem. We are running SA6.1 > on two servers: one inside our corporate network and one outside. They > each monitor different sets of servers (inside/outside). The outside > server does not have this issue. > > If I delete [HKEY_LOCAL_MACHINE\SOFTWARE\DBU Consulting\Servers > Alive\team] > and restart the service I can add a new group and it works. > > I have triple checked our server.txt file, our registry keys, all .ini > files... I cannot find any likely cause of the team failure. > > > Josh Stout > > > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Chris Mang > Sent: Tuesday, February 19, 2008 1:01 PM > To: Servers Alive Discussion List > Subject: RE: [SA-list] SA 6.x Teams fail to function > > ....and support like THIS is priceless. > > Chris Mang>> > ITG Security Administrator > JDA Software Group, Inc. > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Mark Perry > Sent: Tuesday, February 19, 2008 11:36 AM > To: Servers Alive Discussion List > Subject: RE: [SA-list] SA 6.x Teams fail to function > > If I have this right you need to update the registry on a lot of > Servers? > > If you require assistance I can assist with a writing a script that you > could paste the necessary Server names into. > > > Mark Perry > > Systems & Networks Administrator > > Telephonetics VIP Ltd > > > > "making sound > > business sense" > > > > Simply dial +44 (0)1442 242 242 and ask for me by name. > > www.telephoneticsVIP.co.uk > > Providing innovative hosted and customer premises speech recognition and > voice automation solutions. > > > > Disclaimer: available at > http://www.telephoneticsVIP.co.uk/telephonetics/emaildisclaimer.jsp or > by sending email to <mailto:[EMAIL PROTECTED] > applies to this email. > > Registered address: 7th Floor, Hamilton House, 111 Marlowes, Hemel > Hempstead, Hertfordshire HP1 1BB > > Registered in England No: 2831215 > > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Stout, Josh > Sent: Tuesday, February 19, 2008 5:21 PM > To: Servers Alive Discussion List > Subject: RE: [SA-list] SA 6.x Teams fail to function > > "Excellent" support normally includes person to talk to. A single email > address based in a foreign country with *still* no response is not > "excellent." > > I'm sure they have good intentions and are nice people. But I'm not > seeing any results. > > *Still* no response (other than the newsgroup -- which got a quick > retort.) > > Josh Stout > > > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Jason Passow > Sent: Tuesday, February 19, 2008 11:56 AM > To: Servers Alive Discussion List > Subject: Re: [SA-list] SA 6.x Teams fail to function > > WOW! Seems like you are barking up the wrong tree here. We have all > received GREAT support. Not just mediocre but EXCELLENT support. I do > > recall seeing a post come across the mailing list with any problems > either. I am sure that this problem could have been solved. Perhaps > before griping about the fact that you created more work for yourself > you should have exhausted all options including the mailing list. That > > is all I am saying about the issue in order to ensure this thread does > not degenerate to name calling. > > 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." > > > > Stout, Josh wrote: >> We ran into a problem with our SA6.x server where team entries failed > to >> produce an alert. When we added a user to the alert dialogue box the >> system produced an alert. >> >> I removed all teams from the registry and added a new team. The new >> team then successfully produced an alert. I am now faced with > replacing >> 46 teams on 367 servers. Not fun. >> >> Also, you should all be warned that we purchased an annual support >> agreement for Servers Alive ($100/yr) and could not get any help with >> our issue. So I wouldn't buy support from these guys if I were you. >> >> Josh Stout >> >> >> >> -----Original Message----- >> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On >> Behalf Of [EMAIL PROTECTED] >> Sent: Tuesday, February 19, 2008 10:56 AM >> To: Servers Alive Discussion List >> Subject: RE: [SA-list] MS Virtual Server checks >> >> I am currently running Servers Alive on a virtual machine running > Server >> 2003 Enterprise and have not had a single issue. >> Also have Servers Alive checking all 120 of my virtual machines and > that >> has also worked great with no issues at all. >> >> >> >> >> >> Thanks, >> Dave >> >> >> >> Dave Ashe >> Hill-Rom IT Specialist >> 1225 Crescent Green, Suite 200 >> Cary NC 27518 >> (919) 854-3255 >> -----Original Message----- >> From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of >> Barry George >> Sent: Tuesday, February 19, 2008 10:46 AM >> To: [email protected] >> Subject: RE: [SA-list] MS Virtual Server checks >> >> This is checking against a VM. Has anyone had any issues with running > SA >> as a VM? >> I was about to install SA into a VM running V Server 2005 R2. >> Thanks >> >> >> >> -----Original Message----- >> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On >> Behalf Of Dirk Bulinckx >> Sent: February 19, 2008 5:56 AM >> To: Servers Alive Discussion List >> Subject: [SA-list] MS Virtual Server checks >> >> We're currently working on an MS Virtual Server check, however due to >> the way that the MS APIs work is looks like the check will have some >> limitations. >> We would like to know if the SA system that would do the checks is >> within the same DOMAIN/FORREST as the system running the MS Virtual >> Server? >> Also we would like to know if it a problem to have on a both the > system >> running >> SA and the system running the virtual server a useraccount with the > same >> NAME >> and PASSWORD. >> >> >> (from the info we found now, it will be very hard, not to say > impossible >> to run >> this type of check using the MS APIs when SA is running as service > using >> the >> SYSTEM account). >> >> >> >> Dirk Bulinckx. >> >> 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. >> > > 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. > > 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. 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.
