Gerard -

In looking at the resources I found in the MSKB (http://support.microsoft.com/default.aspx?scid=fh;EN-US;KBHOWTO - search for "delayed write"), this error, possibly with different causes, seems to be addressed in both SP2 and SP3 of Win2K. It might be that updating to SP2 or SP3 on the client machines (or possibly the server?) will solve the problem. There also appears to be a post-SP3 hotfix that deals with this error.

You should look in the Event Log on the client machines and on the server to determine where the error is being logged. That will help you as you try to determine which of the KB articles applies to your situation. You can reach the Event Log Viewer from Administrative Tools in Start/Programs or in the Control Panel.

One other thing to look at is network hardware (cables,hubs,switches) between the client and server. Do you have another server you can test with? If it works on another server, that might indicate that there is a network component with problems. In my situation, I first confirmed that I could run the append on the local drive without problems. From there, you could test it with other machines in close proximity network-wise and keep doing that as you move toward the server.

I also read of one case where a virus scanner was causing this problem. That might be something to consider as well.

This was a frustrating error for me to resolve. Hope you can get it solved.

Scott

>Hi Scott.
>Just an update on this problem.
>I checked the site and both the Client PC (Win2000 Prof) and the Server PC (Win2000 Server) had diabled write-caching. However, this problem is still appearing with these setting disabled.
>
>One thing that did look a little strange. On the client PC, the Box for Enabling Write Caching was disabled, but it was also greyed out , so it could not even be enabled if that was a requirement.
>
>Do you know if the version of Win2k is relevant or are there any other avenues I could look at ?
>
>Regards,
>
>Gerard