At 05:50 PM 1/10/2008, Salvador Manzo wrote: Or make it optional... If you wont be using the Telephony service for notifications (example no phone line to the SAlive machine), the Telephony service shouldnt be necessary.
I know other applications deal with similar issues, so something can be done. Perhaps write something to the error log, or time out and exit. On 1/10/08 14:30, "Mark Perry" <[EMAIL PROTECTED]> wrote: Dirk could you not simply execute code to check the status/start the service prior to executing the code for the form? SALive will be running either as local system as a service in most cases which should have rights enough to start / enable the service if disabled. A popup/salive message could possibly be generated to signify this or failure?? Not sure how much work this would be though... From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) On Behalf Of Dirk Bulinckx Sent: 10 January 2008 21:11 To: Servers Alive Discussion List Subject: RE: [SA-list] Servers Alive not starting up right Well that would indeed seem like the obvious solution for this. However, one of the controls that is being used by Servers Alive needs this telephony service to be running, and this control is part of the startup form, this means that the form (app) can 't realy start without this service. Don't think I can get around that. Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) On Behalf Of Richard Sleegers Sent: Thursday, January 10, 2008 10:01 PM To: Servers Alive Discussion List Subject: Re: [SA-list] Servers Alive not starting up right Dirk, I know this is in the FAQ and can be found in this group, but wouldn't it be easy for SAlive to check on startup for the Telephony service to be in the running condition and report an error if it is not (either GUI or log or both)? It could process the ">net start" command and check for "Telephony", althouh I think services checks are already built in to SAlive. Unless I'm missing something, it seems to be an easy check to prevent support requests relating to it. Richard ----- Original Message ----- From: Dirk Bulinckx < mailto:[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> To: Servers Alive Discussion List < mailto:[email protected] (mailto:[email protected])> Sent: Thursday, January 10, 2008 3:25 PM Subject: RE: [SA-list] Servers Alive not starting up right Make sure the telephony service is running. Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) On Behalf Of Greg D. Moore Sent: Thursday, January 10, 2008 9:15 PM To: Servers Alive Discussion List Subject: [SA-list] Servers Alive not starting up right Very weird. Made a change on Dec. 29th. Didn't notice to day that we weren't getting our daily heartbeats (ok, so we're a little slow). Go in... services process is running at about 80% and Salive about 20%. Kill it, start over.. same thing. No matter what, when we try to run Servers Alive, the SERVICES app goes to 70-80% and SALIVE uses up the rest of the CPU and never starts. I've tried a couple of basic things, but no luck, the GUI never comes up. Looks like we're running: Woodstone Servers Alive version 6.0.2056.3 < http://www.woodstone.nu/salive (http://www.woodstone.nu/salive)> I don't mind upgrading if that's the solution, I just don't want to lose our settings. Greg D. Moore 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. ----- Salvador Manzo [ 620 W. 35th St - Los Angeles, CA 90089 e. [EMAIL PROTECTED] ] Auxiliary Services IT, Datacenter University of Southern California 818-612-5112 "Progress is made by lazy men looking for easier ways to do things." - Robert A. Heinlein 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. Greg D. Moore President [EMAIL PROTECTED] Personal: http://stratton.greenms.com (http://stratton.greenms.com/)Ask me about lily, an RPI based chat system: http://lilycore.sourceforge.net/ (http://lilycore.sourceforge.net/)SQL Server Consulting [EMAIL PROTECTED] 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.
