Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Invalid driver object password

64 views
Skip to first unread message

Novell

unread,
Dec 7, 2006, 11:31:12 AM12/7/06
to
Anyone any ideas, I've already tried the obvious Google Novell things to try
but ..

p.s - I've re-installed it all twice and installed the driver set twice, and
used different accounts in different configurations on different servers and
they all come back with this error. I'm going to lab it at home tomorrow to
see if I can create the same error.

Using IDM3.0.1 on a Windows 2003 R2 STD sever running eDirectory 8.7.3.8,
connecting to a Windows 20003 R2 Enterprise domain controller running DirXML
Remote Loader. When I start the AD driver in iManager 2.6, on the remote
loader trace screen I get the following error: DirXML: [12/07/06
15:16:21.59]: DirXML Log Event ------------------- Thread = Subscriber
Channel Level = error Message = Invalid driver object
passwordDirXML: [12/07/06 15:16:21.59]: Loader: Waiting for DirXML to
connect on 'TCP server socket, port 8092, address localhost'...DirXML:
[12/07/06 15:16:36.59]: Loader: Received 'handshake' documentDirXML:
[12/07/06 15:16:36.59]: Loader: XML Document:DirXML: [12/07/06 15:16:36.59]:
DirXML: [12/07/06 15:16:36.82]: Loader: Received 'handshake' documentDirXML:
[12/07/06 15:16:36.82]: Loader: XML Document:DirXML: [12/07/06 15:16:36.82]:
Invalid driver object password We have a r/w of root on the
edir server and objects are at the top of the tree, both accounts we use are
admin (both for netware and ms). we can telent to the port for the loader
and until the vault tries to contact it there are no errors. tried with
different passwords etc and different installations/remote loaders on
different servers. Same error on each.

Bruno Guay

unread,
Dec 7, 2006, 3:09:41 PM12/7/06
to
There are 3 passwords you can input in the driver configuration. Try using the same value for all three. Also make sure the remote loader uses the same value. Your problem is with the driver object password, which (if I remember correctly) is used by the remote loader for communicating with the driver.
 
-------- Message d'origine--------
De: dirxml-de...@forge.novell.com de la part de Novell
Date: jeu. 2006-12-07 11:31
À: dirxm...@forge.novell.com
Cc:
Objet: Invalid driver object password

Novell

unread,
Dec 8, 2006, 4:28:32 AM12/8/06
to

Yeah tried that, set everything the same on both sides, even dropped ad passwords to low security but still did not work

 

Any more ideas?

Shon Vella

unread,
Dec 8, 2006, 9:14:54 AM12/8/06
to
You may have a policy (usually input transformation or publisher event
transformation) that is vetoing the the chech-password command from
going through.
--

Shon

0 new messages