Here is an update. Today we had to reboot our Windows based print server. Since then the amount of false positives with error code 1460 was greatly decreased. There were only 3 for the day ! Before and after the reboot I had none of these false positives related to that server ! I tend to believe, that this SA error points to some general Windows network error. Details to be figured out.
> ----- Original Message ----- > From: Dirk <[EMAIL PROTECTED]> > To: "Servers Alive Discussion List" <salive@woodstone.nu> > Subject: RE: [SA-list] Error code 1460 > Date: Tue, 07 Oct 2008 22:00:36 +0200 > > > A connection is made to the remote registry were in the "volatile" part of it > the running processes are also listed. > > Dirk Bulinckx. > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of > Frank Schnell at home > Sent: Tuesday, October 07, 2008 9:50 PM > To: Servers Alive Discussion List > Subject: RE: [SA-list] Error code 1460 > > Dirk, > thanks for the fast reaction. > If WMI is not used at all could you elaborate how the > check is actually done. It will help me to better > diagnose the problem in more detail. What protocols/ > services/Microsoft technologies are involved? > > > There is nothing you can do about that. > I do not believe in that. Up to now I found a solution > for any problem we had. But I need to have more detailed > info from you. > > > A timeout does NOT mean that the process is not running, > SA sends an alert the process is not running. I do understand > that at that moment the check itself could not be performed. > But when receiving 200 of these a day people stop looking at > them. And the one time the message is true ... > The only chance I see is in either changing the tool or finding > a solution. The latter should be possible as the checks worked > fine for many years. I just have to find what is causing it now. > And there I need some information from you. > > Tx for your help > Frank > > this one fixed. > > ----- Original Message ----- > > From: Dirk <[EMAIL PROTECTED]> > > To: "Servers Alive Discussion List" <salive@woodstone.nu> > > Subject: RE: [SA-list] Error code 1460 > > Date: Tue, 07 Oct 2008 20:05:53 +0200 > > > > > > The service and process check of Servers Alive is not using WMI at all. > > The 1460 is typicaly something you get with the process check not with the > > service check. > > > > A timeout does NOT mean that the process is not running, it means that > > within > > the given timeout we did not get an answer from the remote system > > OR that the OS > > "decided" that the wait was long enough and that "it" (the os) > > "thinks" that no > > more answer will come from the remote system. > > > > There is nothing you can do about that. > > > > Dirk Bulinckx. > > > > -----Original Message----- > > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of > > Frank Schnell at home > > Sent: Tuesday, October 07, 2008 7:35 PM > > To: Servers Alive Discussion List > > Subject: [SA-list] Error code 1460 > > > > Hello all, > > > > we are running since a few years a SA instance. Occasionally > > there were false alerts when checking Windows process/services. > > The extra informatiobn showed error code 1460 (time out) > > even though the service was running happily. About 8 weeks ago > > these false alerts increased to about 15 a day. Since a week > > we have about 200 of these per day. The average time out value > > is 2-3 seconds. > > > > I do understand that this is not a time out problem with the > > actual check settings in SA. I increased it to 300 sec and still > > the same problem. > > > > The problem lies somewhere else, but where? Could someone elaborate > > on how that check is actually being performed. We do use authentication > > data per check on Windows services/processes. From a Wireshark dump > > I see that WMI is somehow involved. How can a analyse this problem? > > > > We already installed SA on a different, brandnew computer, to ensure > > it is not a problem with the computer SA is running on. No change. > > > > Any hints, tips and tricks are welcome. > > > > Tx > > Frank > > > > -- > > _______________________________________________ > > Surf the Web in a faster, safer and easier way: > > Download Opera 9 at http://www.opera.com > > > > Powered by Outblaze > > > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to > > salive@woodstone.nu > > 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 salive@woodstone.nu > > 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. > > > > > > -- > _______________________________________________ > Surf the Web in a faster, safer and easier way: > Download Opera 9 at http://www.opera.com > > Powered by Outblaze > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to > salive@woodstone.nu > 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 salive@woodstone.nu > 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. > -- _______________________________________________ Surf the Web in a faster, safer and easier way: Download Opera 9 at http://www.opera.com Powered by Outblaze To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu 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.
