Write-Delay errors for multi-user app
in [Hardware]
|
Prev: New system with USB 3.0 Ports
Next: toggling removable bit for A Data SDHC? (so XP sees SDHC as a Fixed Drive)
From: Mike in Nebraska on 5 Mar 2010 17:18 Finally had a chance to run CHKDSK /F. It only found minor errors, but nothing wrong with the HD. Hmmmmm... "Andrew E." <eckrichco(a)msn.com> wrote in message news:32A22187-01D8-4732-B5D9-CC37D6529BE0(a)microsoft.com... > Write delays typically are always hard-drive issues,meaning the hd needs > replacing.Download the MS-DOS hd checker from its mfg web site,install to > floppy or cd,boot pc to floppy,run the tests... > > > "Mike in Nebraska" wrote: > >> PC: Intel P4 CPU 3gHz dual processor, 1 GB RAM, no-name box with a MSI >> motherboard running Phoenix BIOS dated 2005. >> OS: WinXP Pro SP3 >> >> We're running a multi-user app with the 'server' on another WinXP Pro PC. >> I >> get several Write-Delay errors per day when workign within the app. We've >> changed out the switch, ran new CAT5, updated BIOS and NIC drivers - no >> change. Had app tech support look at data and they say it's within our >> network. Would appreciate your ideas. >> >> Here's the System log error: >> >> Event Type: Warning >> Event Source: MRxSmb >> Event Category: None >> Event ID: 50 >> Date: 3/4/2010 >> Time: 2:26:20 PM >> User: N/A >> Computer: ESTIMATION >> Description: >> {Delayed Write Failed} Windows was unable to save all the data for the >> file >> \Device\LanmanRedirector. The data has been lost. This error may be >> caused >> by a failure of your computer hardware or network connection. Please try >> to >> save this file elsewhere. >> >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> Data: >> 0000: 04 00 04 00 02 00 56 00 ......V. >> 0008: 00 00 00 00 32 00 04 80 ....2..? >> 0010: 00 00 00 00 0c 02 00 c0 .......� >> 0018: 00 00 00 00 00 00 00 00 ........ >> 0020: 00 00 00 00 00 00 00 00 ........ >> 0028: 0c 02 00 c0 ...� >> (Yes, I checked the KB at Microsoft and this error shouldn't occur since >> I >> have SP3.) >> >> And here's the Application error (if it helps): >> >> Event Type: Error >> Event Source: Application Error >> Event Category: None >> Event ID: 1000 >> Date: 3/4/2010 >> Time: 1:34:55 PM >> User: N/A >> Computer: ESTIMATION >> Description: >> Faulting application turningpoint.exe, version 6.4.11.0, faulting module >> kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb. >> >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> Data: >> 0000: 41 70 70 6c 69 63 61 74 Applicat >> 0008: 69 6f 6e 20 46 61 69 6c ion Fail >> 0010: 75 72 65 20 20 74 75 72 ure tur >> 0018: 6e 69 6e 67 70 6f 69 6e ningpoin >> 0020: 74 2e 65 78 65 20 36 2e t.exe 6. >> 0028: 34 2e 31 31 2e 30 20 69 4.11.0 i >> 0030: 6e 20 6b 65 72 6e 65 6c n kernel >> 0038: 33 32 2e 64 6c 6c 20 35 32.dll 5 >> 0040: 2e 31 2e 32 36 30 30 2e .1.2600. >> 0048: 35 37 38 31 20 61 74 20 5781 at >> 0050: 6f 66 66 73 65 74 20 30 offset 0 >> 0058: 30 30 31 32 61 66 62 0d 0012afb. >> 0060: 0a . >> >> TIA, >> Mike >> Hastings, NE >> >> >> . >>
From: Mike in Nebraska on 16 Mar 2010 10:17 Just an update. I'm still getting these errors - although not all the time nor every day. This is the typical error: Event Type: Warning Event Source: MRxSmb Event Category: None Event ID: 50 Date: 3/16/2010 Time: 9:07:03 AM User: N/A Computer: ESTIMATION Description: {Delayed Write Failed} Windows was unable to save all the data for the file \Device\LanmanRedirector. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 04 00 04 00 02 00 56 00 ......V. 0008: 00 00 00 00 32 00 04 80 ....2..� 0010: 00 00 00 00 0c 02 00 c0 .......� 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 0c 02 00 c0 ...� =========== Since the HD seemed to check OK (see previous post), I uninstalled WinXP SP3, then installed SP2 then SP3 in hopes it'd repair the Write-Delay problem that was one of the fixes with SP2. But ... no change. Any other tests I can run to nail down the specific cause? (I want to be able to show definitively to the boss what the problem is so we can fix it and move on.) TIA, Mike "Andrew E." <eckrichco(a)msn.com> wrote in message news:32A22187-01D8-4732-B5D9-CC37D6529BE0(a)microsoft.com... > Write delays typically are always hard-drive issues,meaning the hd needs > replacing.Download the MS-DOS hd checker from its mfg web site,install to > floppy or cd,boot pc to floppy,run the tests... > > > "Mike in Nebraska" wrote: > >> PC: Intel P4 CPU 3gHz dual processor, 1 GB RAM, no-name box with a MSI >> motherboard running Phoenix BIOS dated 2005. >> OS: WinXP Pro SP3 >> >> We're running a multi-user app with the 'server' on another WinXP Pro PC. >> I >> get several Write-Delay errors per day when workign within the app. We've >> changed out the switch, ran new CAT5, updated BIOS and NIC drivers - no >> change. Had app tech support look at data and they say it's within our >> network. Would appreciate your ideas. >> >> Here's the System log error: >> >> Event Type: Warning >> Event Source: MRxSmb >> Event Category: None >> Event ID: 50 >> Date: 3/4/2010 >> Time: 2:26:20 PM >> User: N/A >> Computer: ESTIMATION >> Description: >> {Delayed Write Failed} Windows was unable to save all the data for the >> file >> \Device\LanmanRedirector. The data has been lost. This error may be >> caused >> by a failure of your computer hardware or network connection. Please try >> to >> save this file elsewhere. >> >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> Data: >> 0000: 04 00 04 00 02 00 56 00 ......V. >> 0008: 00 00 00 00 32 00 04 80 ....2..? >> 0010: 00 00 00 00 0c 02 00 c0 .......� >> 0018: 00 00 00 00 00 00 00 00 ........ >> 0020: 00 00 00 00 00 00 00 00 ........ >> 0028: 0c 02 00 c0 ...� >> (Yes, I checked the KB at Microsoft and this error shouldn't occur since >> I >> have SP3.) >> >> And here's the Application error (if it helps): >> >> Event Type: Error >> Event Source: Application Error >> Event Category: None >> Event ID: 1000 >> Date: 3/4/2010 >> Time: 1:34:55 PM >> User: N/A >> Computer: ESTIMATION >> Description: >> Faulting application turningpoint.exe, version 6.4.11.0, faulting module >> kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb. >> >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> Data: >> 0000: 41 70 70 6c 69 63 61 74 Applicat >> 0008: 69 6f 6e 20 46 61 69 6c ion Fail >> 0010: 75 72 65 20 20 74 75 72 ure tur >> 0018: 6e 69 6e 67 70 6f 69 6e ningpoin >> 0020: 74 2e 65 78 65 20 36 2e t.exe 6. >> 0028: 34 2e 31 31 2e 30 20 69 4.11.0 i >> 0030: 6e 20 6b 65 72 6e 65 6c n kernel >> 0038: 33 32 2e 64 6c 6c 20 35 32.dll 5 >> 0040: 2e 31 2e 32 36 30 30 2e .1.2600. >> 0048: 35 37 38 31 20 61 74 20 5781 at >> 0050: 6f 66 66 73 65 74 20 30 offset 0 >> 0058: 30 30 31 32 61 66 62 0d 0012afb. >> 0060: 0a . >> >> TIA, >> Mike >> Hastings, NE >> >> >> . >>
From: trashcan on 17 Mar 2010 02:00 On Tue, 16 Mar 2010 09:17:05 -0500, "Mike in Nebraska" <Mike_Webb(a)q.com> wrote: >Just an update. I'm still getting these errors - although not all the time >nor every day. This is the typical error: > >Event Type: Warning >Event Source: MRxSmb >Event Category: None >Event ID: 50 >Date: 3/16/2010 >Time: 9:07:03 AM >User: N/A >Computer: ESTIMATION >Description: >{Delayed Write Failed} Windows was unable to save all the data for the file >\Device\LanmanRedirector. The data has been lost. This error may be caused >by a failure of your computer hardware or network connection. Please try to >save this file elsewhere. > >For more information, see Help and Support Center at >http://go.microsoft.com/fwlink/events.asp. >Data: >0000: 04 00 04 00 02 00 56 00 ......V. >0008: 00 00 00 00 32 00 04 80 ....2..� >0010: 00 00 00 00 0c 02 00 c0 .......� >0018: 00 00 00 00 00 00 00 00 ........ >0020: 00 00 00 00 00 00 00 00 ........ >0028: 0c 02 00 c0 ...� >=========== >Since the HD seemed to check OK (see previous post), I uninstalled WinXP >SP3, then installed SP2 then SP3 in hopes it'd repair the Write-Delay >problem that was one of the fixes with SP2. But ... no change. Any other >tests I can run to nail down the specific cause? (I want to be able to show >definitively to the boss what the problem is so we can fix it and move on.) > >TIA, >Mike > >"Andrew E." <eckrichco(a)msn.com> wrote in message >news:32A22187-01D8-4732-B5D9-CC37D6529BE0(a)microsoft.com... >> Write delays typically are always hard-drive issues,meaning the hd needs >> replacing.Download the MS-DOS hd checker from its mfg web site,install to >> floppy or cd,boot pc to floppy,run the tests... >> >> >> "Mike in Nebraska" wrote: >> >>> PC: Intel P4 CPU 3gHz dual processor, 1 GB RAM, no-name box with a MSI >>> motherboard running Phoenix BIOS dated 2005. >>> OS: WinXP Pro SP3 >>> >>> We're running a multi-user app with the 'server' on another WinXP Pro PC. >>> I >>> get several Write-Delay errors per day when workign within the app. We've >>> changed out the switch, ran new CAT5, updated BIOS and NIC drivers - no >>> change. Had app tech support look at data and they say it's within our >>> network. Would appreciate your ideas. >>> >>> Here's the System log error: >>> >>> Event Type: Warning >>> Event Source: MRxSmb >>> Event Category: None >>> Event ID: 50 >>> Date: 3/4/2010 >>> Time: 2:26:20 PM >>> User: N/A >>> Computer: ESTIMATION >>> Description: >>> {Delayed Write Failed} Windows was unable to save all the data for the >>> file >>> \Device\LanmanRedirector. The data has been lost. This error may be >>> caused >>> by a failure of your computer hardware or network connection. Please try >>> to >>> save this file elsewhere. >>> >>> For more information, see Help and Support Center at >>> http://go.microsoft.com/fwlink/events.asp. >>> Data: >>> 0000: 04 00 04 00 02 00 56 00 ......V. >>> 0008: 00 00 00 00 32 00 04 80 ....2..? >>> 0010: 00 00 00 00 0c 02 00 c0 .......� >>> 0018: 00 00 00 00 00 00 00 00 ........ >>> 0020: 00 00 00 00 00 00 00 00 ........ >>> 0028: 0c 02 00 c0 ...� >>> (Yes, I checked the KB at Microsoft and this error shouldn't occur since >>> I >>> have SP3.) >>> >>> And here's the Application error (if it helps): >>> >>> Event Type: Error >>> Event Source: Application Error >>> Event Category: None >>> Event ID: 1000 >>> Date: 3/4/2010 >>> Time: 1:34:55 PM >>> User: N/A >>> Computer: ESTIMATION >>> Description: >>> Faulting application turningpoint.exe, version 6.4.11.0, faulting module >>> kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb. >>> >>> For more information, see Help and Support Center at >>> http://go.microsoft.com/fwlink/events.asp. >>> Data: >>> 0000: 41 70 70 6c 69 63 61 74 Applicat >>> 0008: 69 6f 6e 20 46 61 69 6c ion Fail >>> 0010: 75 72 65 20 20 74 75 72 ure tur >>> 0018: 6e 69 6e 67 70 6f 69 6e ningpoin >>> 0020: 74 2e 65 78 65 20 36 2e t.exe 6. >>> 0028: 34 2e 31 31 2e 30 20 69 4.11.0 i >>> 0030: 6e 20 6b 65 72 6e 65 6c n kernel >>> 0038: 33 32 2e 64 6c 6c 20 35 32.dll 5 >>> 0040: 2e 31 2e 32 36 30 30 2e .1.2600. >>> 0048: 35 37 38 31 20 61 74 20 5781 at >>> 0050: 6f 66 66 73 65 74 20 30 offset 0 >>> 0058: 30 30 31 32 61 66 62 0d 0012afb. >>> 0060: 0a . >>> >>> TIA, >>> Mike >>> Hastings, NE >>> >>> >>> . >>> > This fixed the same ptoblem on my standalone box: Windows Delayed Write Failed � Latest Solution http://www.gibni.com/windows-delayed-write-failed-2 -- Eddie in Loveland "Personally, I don't trust weathermen. They change their story every day!" - Tia Carmen
From: Mike in Nebraska on 17 Mar 2010 09:00
I'll give it a try. I set the minimum to 80,000 and the max to 128,000 as it was currently at 92,000+. On a related note, I downloaded and used Seagate's HD Diagnostic (my HD is an ST380817AS legacy) and the scans I ran from it found no problem. Doesn't mean there isn't one - could be an intermittent thing that will soon manifest itself. Just don't know. Mike <trashcan(a)xrex.us> wrote in message news:unr0q5t2as74b23eh72m9d9tu9ujmm15nn(a)4ax.com... > On Tue, 16 Mar 2010 09:17:05 -0500, "Mike in Nebraska" > <Mike_Webb(a)q.com> wrote: > >>Just an update. I'm still getting these errors - although not all the >>time >>nor every day. This is the typical error: >> >>Event Type: Warning >>Event Source: MRxSmb >>Event Category: None >>Event ID: 50 >>Date: 3/16/2010 >>Time: 9:07:03 AM >>User: N/A >>Computer: ESTIMATION >>Description: >>{Delayed Write Failed} Windows was unable to save all the data for the >>file >>\Device\LanmanRedirector. The data has been lost. This error may be caused >>by a failure of your computer hardware or network connection. Please try >>to >>save this file elsewhere. >> >>For more information, see Help and Support Center at >>http://go.microsoft.com/fwlink/events.asp. >>Data: >>0000: 04 00 04 00 02 00 56 00 ......V. >>0008: 00 00 00 00 32 00 04 80 ....2..? >>0010: 00 00 00 00 0c 02 00 c0 .......� >>0018: 00 00 00 00 00 00 00 00 ........ >>0020: 00 00 00 00 00 00 00 00 ........ >>0028: 0c 02 00 c0 ...� >>=========== >>Since the HD seemed to check OK (see previous post), I uninstalled WinXP >>SP3, then installed SP2 then SP3 in hopes it'd repair the Write-Delay >>problem that was one of the fixes with SP2. But ... no change. Any other >>tests I can run to nail down the specific cause? (I want to be able to >>show >>definitively to the boss what the problem is so we can fix it and move >>on.) >> >>TIA, >>Mike >> >>"Andrew E." <eckrichco(a)msn.com> wrote in message >>news:32A22187-01D8-4732-B5D9-CC37D6529BE0(a)microsoft.com... >>> Write delays typically are always hard-drive issues,meaning the hd >>> needs >>> replacing.Download the MS-DOS hd checker from its mfg web site,install >>> to >>> floppy or cd,boot pc to floppy,run the tests... >>> >>> >>> "Mike in Nebraska" wrote: >>> >>>> PC: Intel P4 CPU 3gHz dual processor, 1 GB RAM, no-name box with a MSI >>>> motherboard running Phoenix BIOS dated 2005. >>>> OS: WinXP Pro SP3 >>>> >>>> We're running a multi-user app with the 'server' on another WinXP Pro >>>> PC. >>>> I >>>> get several Write-Delay errors per day when workign within the app. >>>> We've >>>> changed out the switch, ran new CAT5, updated BIOS and NIC drivers - no >>>> change. Had app tech support look at data and they say it's within our >>>> network. Would appreciate your ideas. >>>> >>>> Here's the System log error: >>>> >>>> Event Type: Warning >>>> Event Source: MRxSmb >>>> Event Category: None >>>> Event ID: 50 >>>> Date: 3/4/2010 >>>> Time: 2:26:20 PM >>>> User: N/A >>>> Computer: ESTIMATION >>>> Description: >>>> {Delayed Write Failed} Windows was unable to save all the data for the >>>> file >>>> \Device\LanmanRedirector. The data has been lost. This error may be >>>> caused >>>> by a failure of your computer hardware or network connection. Please >>>> try >>>> to >>>> save this file elsewhere. >>>> >>>> For more information, see Help and Support Center at >>>> http://go.microsoft.com/fwlink/events.asp. >>>> Data: >>>> 0000: 04 00 04 00 02 00 56 00 ......V. >>>> 0008: 00 00 00 00 32 00 04 80 ....2..? >>>> 0010: 00 00 00 00 0c 02 00 c0 .......� >>>> 0018: 00 00 00 00 00 00 00 00 ........ >>>> 0020: 00 00 00 00 00 00 00 00 ........ >>>> 0028: 0c 02 00 c0 ...� >>>> (Yes, I checked the KB at Microsoft and this error shouldn't occur >>>> since >>>> I >>>> have SP3.) >>>> >>>> And here's the Application error (if it helps): >>>> >>>> Event Type: Error >>>> Event Source: Application Error >>>> Event Category: None >>>> Event ID: 1000 >>>> Date: 3/4/2010 >>>> Time: 1:34:55 PM >>>> User: N/A >>>> Computer: ESTIMATION >>>> Description: >>>> Faulting application turningpoint.exe, version 6.4.11.0, faulting >>>> module >>>> kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb. >>>> >>>> For more information, see Help and Support Center at >>>> http://go.microsoft.com/fwlink/events.asp. >>>> Data: >>>> 0000: 41 70 70 6c 69 63 61 74 Applicat >>>> 0008: 69 6f 6e 20 46 61 69 6c ion Fail >>>> 0010: 75 72 65 20 20 74 75 72 ure tur >>>> 0018: 6e 69 6e 67 70 6f 69 6e ningpoin >>>> 0020: 74 2e 65 78 65 20 36 2e t.exe 6. >>>> 0028: 34 2e 31 31 2e 30 20 69 4.11.0 i >>>> 0030: 6e 20 6b 65 72 6e 65 6c n kernel >>>> 0038: 33 32 2e 64 6c 6c 20 35 32.dll 5 >>>> 0040: 2e 31 2e 32 36 30 30 2e .1.2600. >>>> 0048: 35 37 38 31 20 61 74 20 5781 at >>>> 0050: 6f 66 66 73 65 74 20 30 offset 0 >>>> 0058: 30 30 31 32 61 66 62 0d 0012afb. >>>> 0060: 0a . >>>> >>>> TIA, >>>> Mike >>>> Hastings, NE >>>> >>>> >>>> . >>>> >> > > > > This fixed the same ptoblem on my standalone box: > > Windows Delayed Write Failed - Latest Solution > > http://www.gibni.com/windows-delayed-write-failed-2 > > -- > Eddie in Loveland > > "Personally, I don't trust weathermen. They change their story every > day!" - Tia Carmen |