A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Windows XP Help and Support
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

event id 50 on XP clients (status code: c000020c -- DISCONNECTED)



 
 
Thread Tools Display Modes
  #1  
Old December 28th 03, 01:06 PM
aldousd666
external usenet poster
 
Posts: n/a
Default event id 50 on XP clients (status code: c000020c -- DISCONNECTED)

Ok this is happening on many XP machines and the number goes up daily.
Everytime they try to save to a network share, DFS and non DFS. It's
not happening to our 2k boxes.

I placed a call to Microsoft about this and they sent me the hotfix
for Q321733, which DID NOT help the situation at all.

Anyone else seeing this? If so did you ever resolve it?

I saw a posting about this on
microsoft.public.windowsxp.help_and_support
which never received a reply, and is now a dead thread, yet the
support rep at ms claims that nobody has ever reported it.

Here's the excepts from the log:

Event Type: Warning Event Source: MRxSmb
Event Category: None
Event ID: 50
Date: 08/27/2003
Time: 4:12:16 PM
User: N/A
Computer: insert computer name here
Description: {Delayed Write Failed} Windows was unable to save all the
data for the file blabla. 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.
Data: 0000: 00040004 00560002 00000000 80040032 0010: 00000000
c000020c 00000000 00000000 0020: 00000000 00000000 c000020c
-- last word is the status code

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 08/27/2003
Time: 4:12:17 PM
User: N/A
Computer: insert computer name here
Description: Application popup: Windows - Delayed Write Failed :
Windows was unable to save all the data for the file blabla.doc. 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.

End of Excepts from the log
I didn't really suspect the server because it would be happening to
everyone then, but microsoft's q article 293842 seems to suggest that
may have been it. That article claims the fix is included in SP3, the
server is at SP3, so that's at least a dead end.
http://support.microsoft.com/default...b;en-us;293842
This actual error is coming from many (more popping up each day since
the RPC patch was deployed) XP machines ....
There is a similar looking qarticle for XP, but the status code I'm
getting in event viewer is c000020c (DISCONNECTED) and not
c000022c(ACCESS DENIED) as the below article describes
http://support.microsoft.com/?kbid=321733

Disabling write cachine on the machine did not resolve the issue, and
I tried their suggestion of lowering the UDMA in the bios, only to
find that the machines would then not even save files locally. Also
for the record, these machines already have SMB signing disabled.
Ads
  #2  
Old December 28th 03, 02:23 PM
Richard Michalski
external usenet poster
 
Posts: n/a
Default event id 50 on XP clients (status code: c000020c -- DISCONNECTED)

(aldousd666) wrote in message . com...
Ok this is happening on many XP machines and the number goes up daily.
Everytime they try to save to a network share, DFS and non DFS. It's
not happening to our 2k boxes.

I placed a call to Microsoft about this and they sent me the hotfix
for Q321733, which DID NOT help the situation at all.

Anyone else seeing this? If so did you ever resolve it?

I saw a posting about this on
microsoft.public.windowsxp.help_and_support
which never received a reply, and is now a dead thread, yet the
support rep at ms claims that nobody has ever reported it.

Here's the excepts from the log:

Event Type: Warning Event Source: MRxSmb
Event Category: None
Event ID: 50
Date: 08/27/2003
Time: 4:12:16 PM
User: N/A
Computer: insert computer name here
Description: {Delayed Write Failed} Windows was unable to save all the
data for the file blabla. 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.
Data: 0000: 00040004 00560002 00000000 80040032 0010: 00000000
c000020c 00000000 00000000 0020: 00000000 00000000 c000020c
-- last word is the status code

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 08/27/2003
Time: 4:12:17 PM
User: N/A
Computer: insert computer name here
Description: Application popup: Windows - Delayed Write Failed :
Windows was unable to save all the data for the file blabla.doc. 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.

End of Excepts from the log
I didn't really suspect the server because it would be happening to
everyone then, but microsoft's q article 293842 seems to suggest that
may have been it. That article claims the fix is included in SP3, the
server is at SP3, so that's at least a dead end.
http://support.microsoft.com/default...b;en-us;293842
This actual error is coming from many (more popping up each day since
the RPC patch was deployed) XP machines ....
There is a similar looking qarticle for XP, but the status code I'm
getting in event viewer is c000020c (DISCONNECTED) and not
c000022c(ACCESS DENIED) as the below article describes
http://support.microsoft.com/?kbid=321733

Disabling write cachine on the machine did not resolve the issue, and
I tried their suggestion of lowering the UDMA in the bios, only to
find that the machines would then not even save files locally. Also
for the record, these machines already have SMB signing disabled.


I have had this problem for months and can not find a solution. I
create install files for our Goldmine Contact Management system. I am
writing to a network drive. After about 2-3 hours of constant writing
it crashes. Before SP1 was installed, I could create a file that took
36 hours to create. Hope we hear positive news soon. I also tried
the hotfix for the 22C error and I also have the 20C error.

Rich Michalski
  #3  
Old November 24th 06, 12:09 PM
wa1shy wa1shy is offline
Registered User
 
First recorded activity by PCbanter: Nov 2006
Posts: 1
Default

Hi

I have been getting this message on a few PC's for the last few months. today i set the NIC from auto negotiate to force 100mb Full and bang worked fine after that no one is having the problem at all now

give it a go

Darren
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 08:20 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.