After you pkgrm, wipe out the /nsr directory which will be left behind.  Having 
lived through
this nightmare a few times now, the problem is most likely the former machine 
name that is
hiding in the /nsr/res/nsrladb area along with the SSL cert in there.

I've seen a lot of strange errors happen when that DB has the wrong system name 
stored.  We use
systemimager to lay out the foundation on a lot of our deployed systems and 
vmware clones for
others.  Both of those deployment techniques will cause me to have to diagnose 
why machineX is
trying to recover data from its own backup and is being told that machineY 
doesn't have access.

Frank

On 10/21/10 1:55 PM, otislafayette wrote:
> I have a machine machineX that acts like it is machineY when I attempt a 
> recover.  Very similar, I think, to the situation described previously.  I 
> have deleted the client via the GUI.  De-installed the SUNWebsc package.  
> Re-installed the package and defined the client again and still get the same 
> error.  WHY was the "-c machine1" option required?  HOW do I remove the 
> residue from a previous life of the ebs client from a machine because 
> evidently a pkgrm doesn't get it.  Any help would be greatly appreciated.
> 
> ba


-- 
Frank Swasey                    | http://www.uvm.edu/~fcs
Sr Systems Administrator        | Always remember: You are UNIQUE,
University of Vermont           |    just like everyone else.
  "I am not young enough to know everything." - Oscar Wilde (1854-1900)

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