'Delayed Write Failed' - after SP2 - Q213733

[BP Ritchie]

Error Message:

"Delayed Write Failed" ... occurs during scheduled backup (often when output
file > 4GB)

After installation of Service Pack 2 on Windows XP Pro some of my customers
have started to experience this error message while doing their scheduled
(once per night) backups to their local file server which is dedicated for
backups. The Backup fails as a result. The failure symptoms are identical
to the symptoms described by Q321733 (including the details of the event log
record), which seems to have been fixed for Windows 2000 (about year ago)
but I cannot find a fix for Windows XP.

Does anyone know where to find the XP version of the 'hot fix' for this
problem?

 

[Quaoar]

Error Message:

"Delayed Write Failed" ... occurs during scheduled backup (often when
output file > 4GB)

After installation of Service Pack 2 on Windows XP Pro some of my
customers have started to experience this error message while doing
their scheduled (once per night) backups to their local file server
which is dedicated for backups. The Backup fails as a result. The
failure symptoms are identical to the symptoms described by Q321733
(including the details of the event log record), which seems to have
been fixed for Windows 2000 (about year ago) but I cannot find a fix
for Windows XP.
Does anyone know where to find the XP version of the 'hot fix' for
this problem?

Intel Application Accelerator can lead to this error with some HDs.

Q

 

[BP Ritchie]

Do you mean Intel Application Accelerator on the server or client? ... not
installed on the server, I believe it is installed on the client systems ...
but I don't understand how this might affect network data integrity.

This problem only occurs when executing a backup (so far with output files >
4 GB) to a mapped network drive. The scheduled backups have been running
once per day for about 14 months now ... failures only started being
reported after the installation of Windows XP Service Pack 2 on the Client
systems ... the server was not updated.