Re: Delayed write failure..... Please Help!
- From: "Pegasus [MVP]" <news@xxxxxxxxxxxxx>
- Date: Wed, 22 Apr 2009 00:13:53 +0200
"mpaulic" <mpaulic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A3A9A6B8-6A6B-4B98-9DF2-F46DCABF2A96@xxxxxxxxxxxxxxxx
Hello,
I was hoping that someone can help with a problem I'm having.
Here is the setup;
-Small office network.
-Windows 2003 fileserver, fully up to date. Used as a file server.
-User A's local machine, Windows XP Prof, fully up to date.
-User B's local machine, Windows XP Prof, fully up to date.
-The file server has various shared folders on the network.
-The local machine maps these foldrs as local network drives when the
users
logs in.
-All drive mappings is common to all computers.
-I set up a standard backup using the windows backup to backup the users
\work\ folder.
-For user A the backup work just fine.
-For user B the backup fails with a delayed write failed.
I've been reading & reading with no luck. I found a number of articles
that
describe the issue close but not exact.
I found an article ID#890352 that exactly describes a system event warning
that comes up at the time of the delayed failure. But its for a W2003
server
based OS not a WinXP Prof machine.
I also found a forum thread that described increasing the SessTimeout
parameter from 45 to 300 in the registry under
\HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters. But
there is no SessTimeout parameter in my users machines. So...?
Here is the warning out of the event log;
Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 50
Date: 4/21/09
Time: 10:02:00 AM
User: N/A
Computer: OWNER
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: 00040004 00560002 00000000 80040032
0010: 00000000 c000020c 00000000 00000000
0020: 00000000 00000000 c000020c
Does anyone have a suggestion?
Thanks,
Mat
I suggest you post the following items:
- The full backup command
- The contents of the ntbackup log file that relates to this event.
By the way - why do you run ntbackup on the workstations? Since you have a
file server, the usual method is to run a centralised backup process on this
server.
.
- Follow-Ups:
- Re: Delayed write failure..... Please Help!
- From: mpaulic
- Re: Delayed write failure..... Please Help!
- References:
- Delayed write failure..... Please Help!
- From: mpaulic
- Delayed write failure..... Please Help!
- Prev by Date: Re: Control Panel Freeze
- Next by Date: Re: Is WinXP Sp3 update necessary?
- Previous by thread: Delayed write failure..... Please Help!
- Next by thread: Re: Delayed write failure..... Please Help!
- Index(es):
Relevant Pages
|
Loading