Re: Instantiating DCOM components during reboot
From: Alexander Nickolov (agnickolov_at_mvps.org)
Date: 02/23/05
- Next message: Alexander Nickolov: "Re: COM Security"
- Previous message: Alexander Nickolov: "Re: Error from _Module.RegisterServer()"
- In reply to: Brian Muth: "Re: Instantiating DCOM components during reboot"
- Next in thread: Brian Muth: "Re: Instantiating DCOM components during reboot"
- Reply: Brian Muth: "Re: Instantiating DCOM components during reboot"
- Reply: Scott Ure: "Re: Instantiating DCOM components during reboot"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Feb 2005 10:56:56 -0800
Brian, the 6 minutes timeout is for detecting server death.
OP is talking about establishing a new connection (creating
a new object). The calling application will "hang" the thread
calling CoCreateInstanceEx of course, but not indefinitely.
The proper term is block, not hang. And an STA thread
dispatches some messages in the mean time.
-- ===================================== Alexander Nickolov Microsoft MVP [VC], MCSD email: agnickolov@mvps.org MVP VC FAQ: http://www.mvps.org/vcfaq ===================================== "Brian Muth" <bmuth@mvps.org> wrote in message news:u2BxyzEGFHA.128@TK2MSFTNGP14.phx.gbl... > Are you sure machine A is hanging? In the worst case scenario, I would > expect the proxy to break down the connection after roughly six minutes > passed, and machine A to continue on its way (albeit with an error > HRESULT). > > Please confirm. > > Brian > > "Scott Ure" <ScottUre@discussions.microsoft.com> wrote in message > news:BC2F6A06-37BC-4934-A182-A55E488FFFDA@microsoft.com... >> Hi, >> >> I hope this is the correct newsgroup to ask this question. >> >> On machine A (running Windows 2000 professional) we have windows services >> exposing DCOM interfaces which are accessed from machine B (running > Windows >> 2000 server). If machine B attempts to instantiate one of those >> components >> while machine A is rebooting, depending on what point the reboot is at, >> it >> will log errors to the event log like: >> >> DCOM got error "General access denied error " from the computer >> COMM_SERVER-LRT when attempting to activate the server: >> {BD77409E-8930-4505-AB7E-EDE76D977177} >> >> or >> >> DCOM was unable to communicate with the computer COMM_SERVER-LRT using >> any >> of the configured protocols. >> >> During one test, I was able to cause machine A to hang during its startup >> (prior to the log-on screen showing) by calling it. Also, this seems to > hang >> the calling application under certain circumstances. >> >> When machine A is up and running, no errors occur, everything works as >> expected. >> >> I would have expected DCOM to throw the error RPC_S_SERVER_UNAVAILABLE in >> these cases, but it does not appear to. >> >> My question is: what should we be doing to avoid these errors and hangs? > We >> would like to design our software so that it handle the case of machine A >> rebooting or being unavailable cleanly. >> >> Thanks, >> Scott. > >
- Next message: Alexander Nickolov: "Re: COM Security"
- Previous message: Alexander Nickolov: "Re: Error from _Module.RegisterServer()"
- In reply to: Brian Muth: "Re: Instantiating DCOM components during reboot"
- Next in thread: Brian Muth: "Re: Instantiating DCOM components during reboot"
- Reply: Brian Muth: "Re: Instantiating DCOM components during reboot"
- Reply: Scott Ure: "Re: Instantiating DCOM components during reboot"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading