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 4 Mar 2010 15:40
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: Paul on 4 Mar 2010 19:29
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
>

Is it possible the server is using a RAID array ? Say you
had an extremely long recovery time, from an attempt to
read or write, on the RAID array. Would the client application
time out, before the recovery on the RAID was complete ?

Perhaps you could use an ordinary single drive, on the server,
connect it to a Southbridge port, and store the server-side
data on that. Simplifying the path to the server storage,
might give a different set of symptoms.

The application "Wireshark", can be used to capture packets
on either of the computers. (Install an instance on each machine.)
The packets are time stamped. But such a scheme, doesn't tell
you what is happening within the server storage subsystem. You'd
also need some logs of any timeouts or the like, on the server
storage subsystem, to help in the debugging effort.

http://en.wikipedia.org/wiki/Wireshark

Paul
From: Andrew E. on 4 Mar 2010 23:48
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 5 Mar 2010 10:50
Thanks for the input, but we don't have a true server. I used that term for
where the primary app was installed since my app is pointed to hers under
the multi-use scenario. We, unfortunately, are in a P2P network behind a
Sonicwall firewall. I'm working on making the case for a LAN.

Mike

"Paul" <nospam(a)needed.com> wrote in message
news:hmpj8f$2sh$1(a)speranza.aioe.org...
> 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
>
> Is it possible the server is using a RAID array ? Say you
> had an extremely long recovery time, from an attempt to
> read or write, on the RAID array. Would the client application
> time out, before the recovery on the RAID was complete ?
>
> Perhaps you could use an ordinary single drive, on the server,
> connect it to a Southbridge port, and store the server-side
> data on that. Simplifying the path to the server storage,
> might give a different set of symptoms.
>
> The application "Wireshark", can be used to capture packets
> on either of the computers. (Install an instance on each machine.)
> The packets are time stamped. But such a scheme, doesn't tell
> you what is happening within the server storage subsystem. You'd
> also need some logs of any timeouts or the like, on the server
> storage subsystem, to help in the debugging effort.
>
> http://en.wikipedia.org/wiki/Wireshark
>
> Paul


From: Mike in Nebraska on 5 Mar 2010 10:51
I'll do that. I have suspected the motherboard, but you raise a good point.
I'll report back with the results.

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
>>
>>
>> .
>>


 |  Next  |  Last
Pages: 1 2
Prev: New system with USB 3.0 Ports
Next: toggling removable bit for A Data SDHC? (so XP sees SDHC as a Fixed Drive)