Yes. I just joined the email list and your email was the 1st that I saw. Sorry.
Dave -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Trevor MacDougall Sent: Tuesday, February 05, 2008 3:06 PM To: Servers Alive Discussion List Subject: Re: [SA-list] Salive 6.1.2199 service depends on Telephony Yes, same here. Dave, my original email was sent to the Servers Alive discussion Mailing list. Did you perhaps confuse it with a Woodstone support email response? Trevor Dirk Bulinckx wrote: > Somehow I have the feeling that you're both talking about totally different > things... > > Dirk Bulinckx. > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of > David Carter > Sent: Tuesday, February 05, 2008 8:50 PM > To: Servers Alive Discussion List > Subject: RE: [SA-list] Salive 6.1.2199 service depends on Telephony > > Hi Trevor, > > Thanks for the response. The telephony service is running, and even > stopping the ServersAlive service and restarting it makes no difference. > The service starts fine, but I only get the one alert when a problem > arises with the service running. In application mode, with the service > stopped, I get continual alerts and an update when the alert condition > goes away. It works in either mode, just not quite the same way. > > Dave > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Trevor MacDougall > Sent: Tuesday, February 05, 2008 2:36 PM > To: Servers Alive Discussion List > Subject: [SA-list] Salive 6.1.2199 service depends on Telephony > > Hello again, > > There was a recent change to the beta that requires the Telephony > (TapiSrv) be running > before Salive will start. If you startup Salive manually this is > usually not an issue > because Telephony will be running by the time you login. > > On bootup with Salive setup as an autostart service, Salive wants to run > before the > Telephony service has started. This causes Salive to fail to start. > I've gotten around > this by manually editing the registry and adding the Telephony (TapiSrv) > service as a > dependency to the Salive service. (details here: > http://support.microsoft.com/kb/193888 ) > > Perhaps this should be added the Salive install? > > Trevor MacDougall > > 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.
