ahidalgo1 Absent Member.
Absent Member.
409 views

workorder driver


I am in the process of moving drivers from a 3.6 driver set to a 4.0.2
driver set. Each driver set has it's own partition and I have not had
any problems moving my delimited text drivers but I am stuck with a
workorder driver.

I export the workorder driver from the 3.6 driver set and import it to
the 4.x driver set. I change the references to the driver itself as well
as the workorder OU. All this driver really does is move disabled users
to a different OU but I get the following error. I tried setting setting
security in the driver itself to all OUs involved in the move as well as
setting trustee rights to the OUs via ConsoleOne. What could I be
missing?

Code(-9010) An exception occurred: novell.jclient.JCException: moveEntry
-672 ERR_NO_ACCESS

Thanks,

Al


--
ahidalgo
------------------------------------------------------------------------
ahidalgo's Profile: https://forums.netiq.com/member.php?userid=10766
View this thread: https://forums.netiq.com/showthread.php?t=54637


Labels (1)
0 Likes
9 Replies
Knowledge Partner
Knowledge Partner

Re: workorder driver


As you already suspected it seems to be related to rights.
Try to use admin as security equivalent and see if you get the same
result.

How was the old driver set up? If you do the same it should work.

Or did you forget the ou with the workorder objects?


--
joakim_ganse
------------------------------------------------------------------------
joakim_ganse's Profile: https://forums.netiq.com/member.php?userid=159
View this thread: https://forums.netiq.com/showthread.php?t=54637

0 Likes
ahidalgo1 Absent Member.
Absent Member.

Re: workorder driver


Maybe something is wrong with my admin account. I made driver security
equivalent to another admin account and it worked.

Al


--
ahidalgo
------------------------------------------------------------------------
ahidalgo's Profile: https://forums.netiq.com/member.php?userid=10766
View this thread: https://forums.netiq.com/showthread.php?t=54637


0 Likes
Knowledge Partner
Knowledge Partner

Re: workorder driver


Hi Al,
Do you know which admin account you used for "old" IDM 3.x driver?

Alex


--
If you find this post helpful, please show your appreciation by clicking
on the star below :cool:
------------------------------------------------------------------------
al_b's Profile: https://forums.netiq.com/member.php?userid=209
View this thread: https://forums.netiq.com/showthread.php?t=54637

0 Likes
ahidalgo1 Absent Member.
Absent Member.

Re: workorder driver


I had the same admin user that I made security equivalent with the new
driver in the authentication box for both drivers (since I had imported
it). Is that actually needed for the workorder driver?


--
ahidalgo
------------------------------------------------------------------------
ahidalgo's Profile: https://forums.netiq.com/member.php?userid=10766
View this thread: https://forums.netiq.com/showthread.php?t=54637


0 Likes
Knowledge Partner
Knowledge Partner

Re: workorder driver

No driver object ever really needs 'admin' (meaning Supervisor to [Entry
Rights] at the root of the tree, inheritable), but your driver object will
need rights to do whatever you told it to do. For example, delete from
the source of the move (source people container) and create at the target
(disabled users container). It may need rights to create WorkOrders,
depending on how you create those (this driver object or another) and will
need rights to at least modify WorkOrder objects, and possibly to create
WorkToDo objects, again depending on your implementation.

As always, post a level three trace leading up to the -672 and we'll see
what errors and tell you the asnwer.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Knowledge Partner
Knowledge Partner

Re: workorder driver


> I had the same admin user that I made security equivalent with the new
> driver in the authentication box for both drivers

Hi Al,
Are we talking about same things?
Are we talking about *driver security equivalent*?

You need driver security equivalent to allow driver to manipulate with
your eDir objects. Depend from your business cases you can make it
equivalent to account with R/O access, R/W access, etc.

Alex


--
If you find this post helpful, please show your appreciation by clicking
on the star below :cool:
------------------------------------------------------------------------
al_b's Profile: https://forums.netiq.com/member.php?userid=209
View this thread: https://forums.netiq.com/showthread.php?t=54637

0 Likes
ahidalgo1 Absent Member.
Absent Member.

Re: workorder driver


The old driver is security equivalent to the OUs where the users and to
the workorder OU. I did the same with the new driver but I could not get
pass the -672 errors until I made it security equivalent to an admin
account.

Al


--
ahidalgo
------------------------------------------------------------------------
ahidalgo's Profile: https://forums.netiq.com/member.php?userid=10766
View this thread: https://forums.netiq.com/showthread.php?t=54637


0 Likes
Knowledge Partner
Knowledge Partner

Re: workorder driver

Without a trace we'll never know why; the rights you granted were not what
you needed, and likely differed from what you granted before (maybe
because of other inherited rights in the other structure).


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
ahidalgo1 Absent Member.
Absent Member.

Re: workorder driver


I'll get back to you within a couple days with a trace.

Thanks,

Al


--
ahidalgo
------------------------------------------------------------------------
ahidalgo's Profile: https://forums.netiq.com/member.php?userid=10766
View this thread: https://forums.netiq.com/showthread.php?t=54637


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.