Re: Help: inappropriate OLEDB timeout:
- From: "Matt C." <canimal@xxxxxxxxxxx>
- Date: Thu, 07 Jul 2005 13:12:09 -0700
"Matt C." <canimal@xxxxxxxxxxx> wrote in
news:Xns968BAE6E45433canimalmydejacom@xxxxxxxxxxxxx:
> Erland Sommarskog <esquel@xxxxxxxxxxxxx> wrote in
> news:Xns968BE49E853C9Yazorman@xxxxxxxxx:
>
>> Matt C. (canimal@xxxxxxxxxxx) writes:
>>> Starting yesterday, an application that has previously run without
>>> problems (for several weeks now) has started throwing Timeout
>>> Expired errors after 30 seconds.
I believe I've sorted this out. It is a combination of two things: the
MDAC hotfix described in kb article 832483, and setting the
CommandTimeout to a large value ( > 65536).
On PCs that have the hotfix applied, when the CommandTimeout is set to
65537, I get the premature 30 second timeout. When it's set to 65534,
there is no premature timeout and the process completes normally.
Matt
.
- Follow-Ups:
- Re: Help: inappropriate OLEDB timeout:
- From: Erland Sommarskog
- Re: Help: inappropriate OLEDB timeout:
- References:
- Help: inappropriate OLEDB timeout:
- From: Matt C.
- Re: Help: inappropriate OLEDB timeout:
- From: Erland Sommarskog
- Re: Help: inappropriate OLEDB timeout:
- From: Matt C.
- Help: inappropriate OLEDB timeout:
- Prev by Date: Speed up opening of MS Access databases
- Next by Date: Re: Help: inappropriate OLEDB timeout:
- Previous by thread: Re: Help: inappropriate OLEDB timeout:
- Next by thread: Re: Help: inappropriate OLEDB timeout:
- Index(es):
Relevant Pages
|