That's too bad. With thousands of clients, you can imagine we have a
certain number fail at random because of this bug.
At least the workaround is consistent.
Robert Maiello
Pioneer Data Systems
-----Original Message-----
From: Kathleen [mailto:kathleen_scalise AT ML DOT COM]
Sent: Saturday, May 13, 2006 10:54 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU; Maiello, Robert
Subject: Re: Unable to extract resource info
Doesn't seem to be fixed in 7.2.1 Build 311 for Windows. I just added a
NEW client, tested for connectivity, worked fine, then when I went to
backup for real, got the message: Unable to extract resource . After
reading through the archives for Unable to extract resource , I deleted
all
the aliases and then added them back in and it worked!
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
wit 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
|