This is why I tell customers to do all configuration and editing with a
user-neutral ID with system privilege--an ID that doesn't belong to
anyone in particular.
 
--
Mark Stapleton (mark.stapleton AT cdw DOT com)
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com
 

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Howard Coles
> Sent: Thursday, November 20, 2008 11:26 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Why can't I delete an administrator?
> 
> Nope, admin schedules is what I meant. However, a running client owned
> by this admin might also cause an issue, but you said no sessions were
> running.
> Like, Mark S. said below Storage pools being setup / modified by this
> admin could cause it to be locked.
> 
> I would try halting the server and restarting it at this point and see
> if you can delete / lock the admin.
> 
> See Ya'
> Howard
> 
> 
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf
> > Of Zoltan Forray/AC/VCU
> > Sent: Thursday, November 20, 2008 10:19 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] Why can't I delete an administrator?
> >
> > We don't have any user-created server scripts, so that doesn't
apply.
> >
> > You mentioned "a running client schedule".  Does that mean that if
> this
> > ID
> > updated/created a CLIENT schedule (not just an ADMIN schedule), that
> > would
> > also cause this?
> >
> >
> >
> >
> > Howard Coles <Howard.Coles AT ARDENTHEALTH DOT COM>
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > 11/20/2008 11:15 AM
> > Please respond to
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> >
> > To
> > ADSM-L AT VM.MARIST DOT EDU
> > cc
> >
> > Subject
> > Re: [ADSM-L] Why can't I delete an administrator?
> >
> >
> >
> >
> >
> >
> > Normally it would be a script that's running that would hang you up.
> > If
> > you have a maintenance script that was created by that ID then
you'll
> > have trouble deleting it.
> >
> > I would check those, as normally unless there is a running client
> > schedule, that would not stop you from deleting or locking the admin
> > ID.
> >
> > See Ya'
> > Howard
> >
> >
> > > -----Original Message-----
> > > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf
> > > Of Zoltan Forray/AC/VCU
> > > Sent: Thursday, November 20, 2008 10:03 AM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Re: [ADSM-L] Why can't I delete an administrator?
> > >
> > > No scripts.
> > >
> > > Nodes??? Storage Pools???
> > >
> > > I can't fathom why modifying these would restrict deletion of an
> > admin?
> > > Can someone explain this?   Is there some magical, secret list of
> > what
> > > has
> > > an admins "fingerprint" and therefore does not allow an admin to
be
> > > deleted?
> > >
> > >
> > >
> > >
> > > Mark Stapleton <Mark.Stapleton AT CDW DOT COM>
> > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > > 11/20/2008 10:41 AM
> > > Please respond to
> > > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > >
> > >
> > > To
> > > ADSM-L AT VM.MARIST DOT EDU
> > > cc
> > >
> > > Subject
> > > Re: [ADSM-L] Why can't I delete an administrator?
> > >
> > >
> > >
> > >
> > >
> > >
> > > Scripts being run? Nodes or storage pools having been last
modified
> > by
> > > said admin?
> > >
> > > --
> > > Mark Stapleton (mark.stapleton AT cdw DOT com)
> > > CDW Berbee
> > > System engineer
> > > 7145 Boone Avenue North, Suite 140
> > > Brooklyn Park MN 55428-1511
> > > 763-592-5963
> > > www.berbee.com
> > >
> > >
> > > > -----Original Message-----
> > > > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > Behalf
> > > > Of Zoltan Forray/AC/VCU
> > > > Sent: Thursday, November 20, 2008 10:21 AM
> > > > To: ADSM-L AT VM.MARIST DOT EDU
> > > > Subject: [ADSM-L] Why can't I delete an administrator?
> > > >
> > > > I have been trying to lock/delete an administrator ID and the
> > server
> > > > keeps
> > > > telling me the ID is in use when it clearly isn't  (no sessions
> > > > active).
> > > > When I revoked all authority from the ID, admin schedules
started
> > > > failing
> > > > since they were created/updated by this ID.
> > > >
> > > > So, I went through and updated all admin schedules with my id
> > (select
> > > > schedule_name,chg_admin from admin_schedules verifies this) yet
I
> > > still
> > > > can't deleted the ID
> > > >
> > > > What else is locking this ID?  Client schedules?