Strange Problem: Windows - Delayed Write Failed

[Guest]

We are running a SBS2000 Network where we have two Dell PowerEdge Servers
(PE2400 running Windows 2000 Server and PE2500 Running Windows 2003 Server
Std). Both these machines are on the LAN as member servers - they are acting
as work stations as opposed to 'servers'. There is no AD activated or
anything similar.

The PE2400 runs Visual dBase5.7 and dBase for DOS and a colleague of mine is
manipulating data on the PE2500 from the Power2400. His program gets through
about 70% (or sometimes much less) and he gets the error message on the
PE2400 machine. From PE2400 he maps to M Drive on PE2500:

-----------------------------------------------------

Windows - Delayed Write Failed
---------
\Device\LanmanRedirector\Power2500\M\.....<databasename>.dbf. The data has
been lost . This error maybe caused by a failure of your computer hardware
or network connection. Please try to save this file elsewhere.

_______________________________________


We followed article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;321733 which
suggested that we should have the latest service packs (hotfixes) - which we
did! Furthermore, in the article it mentions that we need to modify a
registry key - which we could not find!

The PE2400 machine has a whole host of EventID:50 in Event Viewer too.

How do we get to the bottom of this?

Skc

 

[aD]

We are running a SBS2000 Network where we have two Dell PowerEdge Servers
(PE2400 running Windows 2000 Server and PE2500 Running Windows 2003 Server
Std). Both these machines are on the LAN as member servers - they are acting
as work stations as opposed to 'servers'. There is no AD activated or
anything similar.

The PE2400 runs Visual dBase5.7 and dBase for DOS and a colleague of mine is
manipulating data on the PE2500 from the Power2400. His program gets through
about 70% (or sometimes much less) and he gets the error message on the
PE2400 machine. From PE2400 he maps to M Drive on PE2500:

What application was using that file? This screams of a time when a
customer of my former employer was running an Access 97 front-end
(shudder) and they had this a lot.

I believe this KB article carried the information needed to alleviate
the problem:

http://support.microsoft.com/kb/812937

This was to do with opportunistic locking, so YMMV.

We followed article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;321733 which
suggested that we should have the latest service packs (hotfixes) - which we
did! Furthermore, in the article it mentions that we need to modify a
registry key - which we could not find!

Are you sure you were looking on the client computers, as specified?
What operating system are the client computers using?

HTH,

aD

 

[Leythos]

We are running a SBS2000 Network where we have two Dell PowerEdge Servers
(PE2400 running Windows 2000 Server and PE2500 Running Windows 2003 Server
Std). Both these machines are on the LAN as member servers - they are acting
as work stations as opposed to 'servers'. There is no AD activated or
anything similar.

The PE2400 runs Visual dBase5.7 and dBase for DOS and a colleague of mine is
manipulating data on the PE2500 from the Power2400. His program gets through
about 70% (or sometimes much less) and he gets the error message on the
PE2400 machine. From PE2400 he maps to M Drive on PE2500:

I've only seen this when there was a defective controller or bad hard
drive in a mirror/raid array. You need to be checking the drives and
controller very quickly.