Re: Windows Service & ADO problem
- From: "Allen" <allenf.NoSp@xxxxxxxxxxxxxxxxxxxx>
- Date: 18 Sep 2006 10:44:18 -0700
Guillem wrote:
this is an extreme case and IMHO not something your app should
control. The OS should be smart enough to handle such reboots.
Some questions:
Are you trying to create a fault-tolerant app? how do you determine
NTLDR becomes corrupted? Does the OS not load properly after trying
this case? Are you sure this problem is caused by your app?
well, first thought would be "use a good UPS". Second thought could be
"save a copy of the NTLDR and anything it needs".
The application is intended to run in a co-location facility and in the
event the machine hangs up (for some or other reason) an iLO card is
used to remotely reboot. The iLO is an ungraceful powerdown. When the
machine reboots it comes up saying that NTLDR & ntdetect.com could not
be found.
This is an unusual use case, however by my thinking this should not
happen. I do not understand how a very commonly used component can
have such horrid behaviour
--
.
- Follow-Ups:
- Re: Windows Service & ADO problem
- From: Guillem
- Re: Windows Service & ADO problem
- References:
- Windows Service & ADO problem
- From: Allen
- Re: Windows Service & ADO problem
- From: Guillem
- Windows Service & ADO problem
- Prev by Date: Re: Windows Service & ADO problem
- Next by Date: Manipulate Schema before SafeToFile(XML)
- Previous by thread: Re: Windows Service & ADO problem
- Next by thread: Re: Windows Service & ADO problem
- Index(es):
Relevant Pages
|
