[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number   :  4933
Date     :  2003-07-03
Author   :  Garry Deane
Subject  :  Re: xxcopy hanging in scheduled tasks
Size(KB) :  2


--- In xxcopy@yahoogroups.com, "Melissa Evans"  wrote:

> We have two particular "hanging" problems. When the more
> benign one occurs, the script appears to hang, but then
> over a minute later it begins to work again, v-e-r-y
> s-l-o-w-l-y. We see this less often since we replaced
> Lantastic software with Windows Client software,
> but it still happens. Usually, restarting the PC helps.
> Sometimes restarting makes no difference.
> 
> The less benign problem happens on certain computers more
> than others, but it has happened on every computer at
> least once, and, this is what happened at least once using
> command.com's COPY. A copy activity hangs up while copying
> a file from the local to the server. On the server, the
> file's name with "now" as date and time has been written,
> but that's all. The file cannot be deleted because the
> permission is locked. The local computer has to be
> restarted with the Reset button or turning off and on.
> If a script was running an xxcopy command line that was
> going to clear the archive bit after copying (/m), the
> archive bit was not cleared. On the server, the corrupt
> file is either zero bytes in size, or it will be 
> about 1500b; it is expected to be about 1.2Mb.
 

Mel,

It's been a while since we had similar problems so I'm not 100% sure 
our problems were the same as you're experiencing but they do seem 
familiar. IIRC, our major problem was with DOS based LAN software and 
the redirector not automatically re-establishing a dropped 
connection. Although it would seem that this shouldn't be an issue 
during an active copy, changing this fixed up a lot of apparently 
unrelated problems we had been experiencing.

The solution was to disable autodisconnect on the server which by 
default, is set to disconnect the client after 15 mins of inactivity. 
See this KB article for details on autodisconnect and how to change 
it http://support.microsoft.com/default.aspx?scid=kb;EN-US;297684

Depending on the number and nature of connections your server has to 
maintain, possibly just increasing the autodisconnect time might be 
appropriate rather than setting it to the maximum value.

Of course there's plently of harware related problems that could also 
produce similar symptoms but that would normally be confined to a 
particular network segment or one or two NICs.

Garry



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.