delayed write failures

XP client sp1 with all hotfixes and windows2003 server with all hotfixes.

Problem: when client make rapid updates to any type of database we get
delayed write errors on the client machines , the server does not report any
errors. We opened a case with microsoft and they gave us the following
suggestions. ;

apply KB834350 -- DONE - Latest redirector files for Windowsxp

force duplex settings on client and switch - DONE

turn of op locking on client and server - DONE

NetBIOS over TCP/IP set to Default. -done changed to Enable



They sent us the latest redirector files for windows 2003 today; KB Article
Number(s): 843517

we are still able to generate the delayed write failures in a testbed of 8
machines consistently. It only happens when we have significant bursts of IO
on foxpro databases, any type of file share database. Windows2000 Clients
sp4 do not have the same issues.



The server is a test server

COMPAQ DL380 G2

DUAL P4 1.4GHZ

4 gigs ram

Intel Pro1000f gig adapter



Has anyone run into this particular issue? and what did you do to fix the
issue?. thank you.

It is NOT the hardware. If you read my MAS90 lockup
situation just below your post - we are in the same boat!
XP and W2K3 are having some serious network connectivity
problems with DB's using ODBC or delayed read/writes!!!!

>-----Original Message-----
>XP client sp1 with all hotfixes and windows2003 server
with all hotfixes.
>
>Problem: when client make rapid updates to any type of
database we get
>delayed write errors on the client machines , the server
does not report any
>errors. We opened a case with microsoft and they gave us
the following
>suggestions. ;
>
>apply KB834350 -- DONE - Latest redirector files for
Windowsxp
>
>force duplex settings on client and switch - DONE
>
>turn of op locking on client and server - DONE
>
>NetBIOS over TCP/IP set to Default. -done changed to
Enable
>
>
>
>They sent us the latest redirector files for windows 2003
today; KB Article
>Number(s): 843517
>
>we are still able to generate the delayed write failures
in a testbed of 8
>machines consistently. It only happens when we have
significant bursts of IO
>on foxpro databases, any type of file share database.
Windows2000 Clients
>sp4 do not have the same issues.
>
>
>
>The server is a test server
>
>COMPAQ DL380 G2
>
>DUAL P4 1.4GHZ
>
>4 gigs ram
>
>Intel Pro1000f gig adapter
>
>
>
>Has anyone run into this particular issue? and what did
you do to fix the
>issue?. thank you.
>
>
>.
>

Our databases are residing on the Windows2003 File share, They are a mixture
of foxpro and access databases, main issue we are seeing is when we do
compacting of access databases and reindexing of the foxpro databases. The
errors are inconsistant and randly occur during the processes.



"Ron" <(E-Mail Removed)> wrote in message
news:192f01c47bef$223cb2e0$(E-Mail Removed)...
> It is NOT the hardware. If you read my MAS90 lockup
> situation just below your post - we are in the same boat!
> XP and W2K3 are having some serious network connectivity
> problems with DB's using ODBC or delayed read/writes!!!!
>
>>-----Original Message-----
>>XP client sp1 with all hotfixes and windows2003 server
> with all hotfixes.
>>
>>Problem: when client make rapid updates to any type of
> database we get
>>delayed write errors on the client machines , the server
> does not report any
>>errors. We opened a case with microsoft and they gave us
> the following
>>suggestions. ;
>>
>>apply KB834350 -- DONE - Latest redirector files for
> Windowsxp
>>
>>force duplex settings on client and switch - DONE
>>
>>turn of op locking on client and server - DONE
>>
>>NetBIOS over TCP/IP set to Default. -done changed to
> Enable
>>
>>
>>
>>They sent us the latest redirector files for windows 2003
> today; KB Article
>>Number(s): 843517
>>
>>we are still able to generate the delayed write failures
> in a testbed of 8
>>machines consistently. It only happens when we have
> significant bursts of IO
>>on foxpro databases, any type of file share database.
> Windows2000 Clients
>>sp4 do not have the same issues.
>>
>>
>>
>>The server is a test server
>>
>>COMPAQ DL380 G2
>>
>>DUAL P4 1.4GHZ
>>
>>4 gigs ram
>>
>>Intel Pro1000f gig adapter
>>
>>
>>
>>Has anyone run into this particular issue? and what did
> you do to fix the
>>issue?. thank you.
>>
>>
>>.
>>

Just a guess,...maybe you could turn off write caching on the effected drive
temporarily to see if it improves.

In Device Manager, goto Properties of the Drive, select the "Disk
Properties" of the Drive, uncheck the "Write Cache enabled" box.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Shawn Smith" <(E-Mail Removed)> wrote in message
news:O4ufwg$(E-Mail Removed)...
> Our databases are residing on the Windows2003 File share, They are a
mixture
> of foxpro and access databases, main issue we are seeing is when we do
> compacting of access databases and reindexing of the foxpro databases. The
> errors are inconsistant and randly occur during the processes.
>
>
>
> "Ron" <(E-Mail Removed)> wrote in message
> news:192f01c47bef$223cb2e0$(E-Mail Removed)...
> > It is NOT the hardware. If you read my MAS90 lockup
> > situation just below your post - we are in the same boat!
> > XP and W2K3 are having some serious network connectivity
> > problems with DB's using ODBC or delayed read/writes!!!!
> >
> >>-----Original Message-----
> >>XP client sp1 with all hotfixes and windows2003 server
> > with all hotfixes.
> >>
> >>Problem: when client make rapid updates to any type of
> > database we get
> >>delayed write errors on the client machines , the server
> > does not report any
> >>errors. We opened a case with microsoft and they gave us
> > the following
> >>suggestions. ;
> >>
> >>apply KB834350 -- DONE - Latest redirector files for
> > Windowsxp
> >>
> >>force duplex settings on client and switch - DONE
> >>
> >>turn of op locking on client and server - DONE
> >>
> >>NetBIOS over TCP/IP set to Default. -done changed to
> > Enable
> >>
> >>
> >>
> >>They sent us the latest redirector files for windows 2003
> > today; KB Article
> >>Number(s): 843517
> >>
> >>we are still able to generate the delayed write failures
> > in a testbed of 8
> >>machines consistently. It only happens when we have
> > significant bursts of IO
> >>on foxpro databases, any type of file share database.
> > Windows2000 Clients
> >>sp4 do not have the same issues.
> >>
> >>
> >>
> >>The server is a test server
> >>
> >>COMPAQ DL380 G2
> >>
> >>DUAL P4 1.4GHZ
> >>
> >>4 gigs ram
> >>
> >>Intel Pro1000f gig adapter
> >>
> >>
> >>
> >>Has anyone run into this particular issue? and what did
> > you do to fix the
> >>issue?. thank you.
> >>
> >>
> >>.
> >>
>
>

Phillip Windell wrote:

> Just a guess,...maybe you could turn off write caching on the effected drive
> temporarily to see if it improves.
>
> In Device Manager, goto Properties of the Drive, select the "Disk
> Properties" of the Drive, uncheck the "Write Cache enabled" box.
>
>
My previous problems with Goldmine and having to turn off opportunistic
locking on the server mentioned both Fox and Access databases as also
having trouble with OL.
gr