Two more questions: 1) Is that the API on the Servers Alive server reporting the timeout, or the API on the server being checked?
2) Is there a workaround? I ask, because I have two servers where I can't check any processes, because I can never see a list of processes, and another that will occasionally report the 1460 error on the store.exe process. Thanks, Chris Mang>> JDA Software Group, Inc. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Wednesday, March 14, 2007 4:50 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Windows NT Process Error In some cases the api call returns quicker then the given timeout and says "timeout", in that case we do show a timeout (even if that happens before the given timeout). Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Chris Mang Sent: Wednesday, March 14, 2007 10:46 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Windows NT Process Error I've regularly had a similar situation with checking STORE.EXE on various Exchange servers. How do you increase the timeout? Changing the timeout on the check itself has no effect. If I go to the Check tab, and click the button to list the available processes, it times out after 8 seconds or so and returns with the ERR: 1460 dialog. However, the timeout setting on the check is set to 100 seconds. Thanks, Chris Mang>> JDA Software Group, Inc. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Monday, March 12, 2007 12:15 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Windows NT Process Error The 1460 error is a timeout error, so if the system isn't responding correctly within the given timeout then you get that error. Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Neil Hayes-Webster Sent: Monday, March 12, 2007 5:26 PM To: Servers Alive Discussion List Subject: [SA-list] Windows NT Process Error Hiya We have an application called Guinevere (NT Process : guinevere) which is regularly being reported as DOWN with ERR: 1460 - its set to alert if there is less than one instance running. I have extended the timeout but we are still getting the errors. The process is still running without fault and is not restarting which we can see from the application stats. Do you have any ideas? There is nothing in either application or system event logs around the time of the failure. Win Server 2003 SP1 2GB RAM Dual core Dual Xeon 3.2GHz Neil Hayes-Webster IS Network Support 01935 404567 Ex 4569 www.ssh.co.uk . Gold Award for Excellence Winner - Housing Corporation . 'Demonstration status' gas servicing partnering contract from the Housing Forum Constructing Excellence Programme . First RSL to use Space4 . Worcester Bosch Environment 2010 Award Winner . Excellence Award by EROSH, National Consortium for Sheltered Housing . 'Code of Practice' Award - Centre for Sheltered Housing Studies . Commended by National Change Agent for Innovation in Procurement of Capital Works Visit our website at www.ssh.co.uk _______________________________________________________________________ Disclaimer: This email is intended for the use of the addressee only and may contain confidential information. If you receive this message in error please let us know by using the reply facility immediately. Attachments to this email may contain software viruses, we have taken every reasonable precaution to minimise this risk but we advise that any attachments are virus checked before they are opened. Any views or opinions expressed in this email are not necessarily those of the company. _______________________________________________________________________ South Somerset Homes Limited is registered in England No. 3488535 Charity No: 1108793 Registered Office: South Somerset House, Alvington, Yeovil Somerset BA22 8WN. Thank you for your cooperation. 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.
