Hi Jason, Yeah, the servers are thousands of miles away from me right now, but I'm sure the 2nd instance is running when this happens. I just verified that with SysInternals process viewer. Tiny snapshot is here now: http://screenshots.href.com/woodstone/snapServersAlive-v7-running2x.png (http://screenshots.href.com/woodstone/snapServersAlive-v7-running2x.png) The 2nd column is PID and the 3rd column is an indication of how long the process has been running.  When I click [ok] on the dialog, the longer-running instance stays and the other one disappears.
I do not use a 2nd instance to monitor the first.  I keep an eye on the salive web report almost constantly. I have not had any stability problems with salive itself in many months. I'm running v7.0.2565 as-service on Win2003. I used to have a lot of crashes with v6 when I ran as-app. I now suspect that whatever is triggering this 2nd instance is the same thing that was triggering the problems that I saw with v6. Ann On 06/06/2013 4:00 AM, Jason Passow wrote: We use VNC to connect to a machine running Salive as an app now.  We use to use it to connect as a service until our move to Server 2008.   I have never experienced the only one instance problem due to VNC.  I am wondering if you were to physically go to the console screen if you would also see it there. Do you have a second Salive instance monitoring the first?  If so does it have an alert for auto-recovery to start the Salive service?  If so I would bet that the issue is there.   This happens occasionally to us when Salive gets hung and our monitoring instance kills and restarts the main instance.   Jason Passow Network Administrator Mississippi Welders Supply http://www.mwsco.com (http://www.mwsco.com) [email protected] (mailto:[email protected]) ph: (507) 494-5178 fax: (507) 454-8104 -------------------------------------------------------------------------------- From: Ann Lynnworth [mailto:[email protected] (mailto:[email protected])] To: Servers Alive Discussion List [mailto:[email protected] (mailto:[email protected])] Sent: Wed, 05 Jun 2013 22:00:20 -0600 Subject: Re: [SA-list] only one instance I don't quite follow your advice yet. By "you will need to use the remote," do you mean Remote Desktop? Or a remote mode of Servers Alive itself? With VNC, there is a just a single shared Windows account in play. Using VNC is like connecting to the console session with Microsoft Remote Desktop. Ann On 06/06/2013 12:15 AM, Goggins, Patrick wrote: > You will need to use the remote. I've since stopped using the service and > have the monitoring VM startup, auto-login, and auto-start interactively SA. > Then whenever we need access a single shared account is used. > > > ~Patrick > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[email protected] > (mailto:[email protected])] On Behalf Of Ann Lynnworth > Sent: Wednesday, June 05, 2013 5:46 PM > To: Servers Alive Discussion List > Subject: [SA-list] only one instance > > On a server where I use VNC to manage the machine, I see this message almost > each time I connect: > > You can only have one instance of Servers Alive running! > [ok] > > I have SA configured to run as a Windows service. > > No other applications appear to try to start just because I connect to the > machine. > > I would not say this is a huge problem, it's just annoying and I guess it is > particular to VNC usage, so maybe you (Dirk) were not aware it was happening. > I'm using TightVNC service 1.3.10 from 2009. > > Ann > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to > [email protected] (mailto:[email protected]) If you use auto-responders > (like out-of-the-office messages), make sure that they are not sent to the > list nor to individual members. Doing so will cause you to be automatically > removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to > [email protected] (mailto:[email protected]) > If you use auto-responders (like out-of-the-office messages), make sure that > they are not sent to the list nor to individual members. Doing so will cause > you to be automatically removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
