Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 494
  • Last Modified:

Insufficient privilege to backup print server object

About 18 months ago I replaced our main production server (4.11) with new
hardware and an upgrade to NW6. I used the Server consolidation utility to
move the files and printer objects over to the new server. No one was using
the old server, but I left in online until i had time to reinstall a number
of clients that were referencing it during login (that's a separate issue).
Anyways, i finally retired the old server. During the next backup of the
main server, I received these errors in BE9.1. These are all print server
objects. These are not the only print servers that were moved over. I am
assuming that I can clear this up by simply deleting these five print
servers and recreating them, but i am curious as to what may have caused
this situation. I have checked the Trustee Lists and they are the same for
the ones that get backed up and the ones that don't.

And yes, i know the tree and org should not have the same name. This was
inherited and I haven't seen that it has caused any problem that would
justify going through the trouble of correcting it.

##ERR##Insufficient privilege for
\.\.T=HPM\.O=HPM\.CN=2D_TRUST.O=HPM.T=HPM. -
##ERR##SKIPPED.
##ERR##Insufficient privilege for
\.\.T=HPM\.O=HPM\.CN=4SI_ACCT.O=HPM.T=HPM. -
##ERR##SKIPPED.
##ERR##Insufficient privilege for
\.\.T=HPM\.O=HPM\.CN=4SI_JL_OLD.O=HPM.T=HPM.
##ERR##- SKIPPED.
##ERR##Insufficient privilege for
\.\.T=HPM\.O=HPM\.CN=5SI_JST.O=HPM.T=HPM. - S-
##ERR##KIPPED.
##ERR##Insufficient privilege for
\.\.T=HPM\.O=HPM\.CN=HP5SI_1173.O=HPM.T=HPM.
##ERR##- SKIPPED.

An additional piece of info is that i cannot bring up the properties of the print servers in NWADNMN32. I get an Error 1063 that reads "The object could not be read.   Error code 110: -618"

0
jgcne
Asked:
jgcne
  • 3
  • 3
1 Solution
 
ShineOnCommented:
It's worth correcting the treename=orgname issue evenually, but if it's not causing immediate problems, put it down on the list a ways.  

From what I gather, renaming the tree isn't that bad.  Renaming a server is more of a hassle.

Let me guess - the 4.x server had a replica?

Have you tried doing a DSREPAIR?  Any errors?  Any that won't go away?

0
 
jgcneAuthor Commented:
Yes, the 4.11 server had a replica.

I performed all the regular NDS health checks, but did not get any errors. I have not done a Repair Local DS database though.
0
 
ShineOnCommented:
You might even want to do a rebuild local schema, to clean out any remnants of the old RECMAN DS.
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
ShineOnCommented:
You did properly remove the 4.11 server from the tree before shutting it off, right?
0
 
jgcneAuthor Commented:
Yes, I removed Directory Services through the Install screen.
0
 
jgcneAuthor Commented:
It turned out to be a simple matter of deleting and recreating the print servers
0
 
DarthModCommented:
PAQed with points (250) refunded

DarthMod
Community Support Moderator
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now