I have come across this problem quite a few times and most likely on busy 
windows servers.

The problem was always solved with a cleanup+restart of NW (i.e. (1) stop nw; 
(2) clean /nsr/tmp -- remove everything except nsr.dir, seg/ and sg/; (3) 
start nw)

Note: Always rename tmp and logs temporarily after Nw shoutdown just to see if 
they are locked by some stalled process. 

jee


On Tuesday 28 Feb 2012 06:10:44 you wrote:
> Anyone ever see this in the GUI? The group shows as failed but when you show
> the details all of the clients have backed up successfully? Is there a way
> to force the GUI to show as successful? Thanks!
> 
> +----------------------------------------------------------------------
> 
> |This was sent by andrew.j.wendler AT questdiagnostics DOT com via Backup 
> Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> 
> +----------------------------------------------------------------------
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS at
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER