I'm running the VRTest server on Windows 2000...
Articles and Tips: qna
01 May 2002
Q.
I'm running the VRTest server on Windows 2000 and the client on Windows 2000 can connect to it okay. I'm running eDirectory 8.5 on NetWare 5.1. I'm trying the Java vrtest driver.
On sys:system\lib, I have the following files:
Directory of T:\system\lib 02/14/2001 06:17p <DIR> . 02/14/2001 06:17p <DIR> . 08/21/1998 03:48p 255,108 collections.jar 12/05/2000 02:46p 514,296 dirxml.jar 12/05/2000 02:14p 233,406 jclient.jar 12/05/2000 02:29p 955,680 nxsl.jar 01/02/1999 08:57a 166,356 xp.jar 05/09/2000 05:08p 215,682 nssl1.1_exp.jar 12/05/2000 02:46p 48,830 NdsToNds.jar 09/25/2000 10:05a 143,030 VRTestDriver.jar 09/25/2000 08:41a 64,208 vrtest_api.jar 09/25/2000 08:41a 5,861 common.jar 09/25/2000 08:41a 50,690 xds.jar
I used the .xml file to bootstrap the driver using the setup wizard running on the Windows 2000 client. When I click the start button for the driver, dstrace and my dirxml log show this error information:
EVLQueueStateChange: Starting driver <\TESTTREE\MyCompany\Driver Set\Hierarchcial> DirXML Driver Subscriber Object <\TESTTREE\MyCompany\Driver Set\Hierarchcial> entryID: 0x8067 DirXML Driver Publisher Object <\TESTTREE\MyCompany\Driver Set\Hierarchcial> entryID: 0x8064 DirXML Driver <\TESTTREE\MyCompany\Driver Set\Hierarchcial> list entry initialized. Starting worker thread. DriverStateChangeEvent returned successfully DirXML Driver worker thread starting. Binding worker thread to DirXML Driver <\TESTTREE\MyCompany\Driver Set\Hierarchcial>. TRACE: Found subscriber: com.novell.nds.dirxml.engine.Entry@1b85b0ab TRACE: Found publisher: com.novell.nds.dirxml.engine.Entry@1b85b0ce TRACE: creating Driver workerThread TRACE: Initializing driver shim TRACE: Reading XML attribute: vnd.nds.stream://TESTTREE/MyCompany/Driver Set/Hierarchcial#DirXML-ApplicationSchema TRACE: Reading driver information from the com.novell.nds.dirxml.engine.Entry@1b85b02c Object TRACE: Loading java shim: com.novell.nds.dirxml.driver.vrtest.java. DriverShimImpl DirXML Driver <\TESTTREE\MyCompany\Driver Set\Hierarchcial> requesting password. Unable to read value of attribute <DirXML-ShimAuthPassword>. TRACE: Reading XML attribute: vnd.nds.stream://TESTTREE/MyCompany/Driver Set/Hierarchcial#DirXML-ShimConfigInfo TRACE:<nds dtdversion="1.0" ndsversion="8.5"> <source> <product version="1.0">DirXML</product> <contact>Novell, Inc.</contact> </source> <input> <init-params src-dn="\TESTTREE\MyCompany\Driver Set\Hierarchcial"> <driver-options> <host display-name="Host name or IP address">128.153.43.14</host> <port display-name="TCP port number">3004</port> </driver-options> </init-params> </input> </nds> TRACE: VRTest/Driver: Initializing driver shim... DirXML Log Event ------------------- Status = error Message = java.lang.ExceptionInInitializerError at com.novell.nds.dirxml.driver.vrtest.java.DriverShimImpl.init (DriverShimImpl. java:133) at com.novell.nds.dirxml.engine.Driver.startShim(Driver.java) at com.novell.nds.dirxml.engine.Driver.run(Compiled Code) at java.lang. Thread.run(Thread.java:466) Error: java.lang.ExceptionInInitializerError Error: at com.novell.nds.dirxml.driver.vrtest.java.DriverShimImpl.init (DriverShimImpl. java:133) Error: at com.novell.nds.dirxml.engine.Driver.startShim(Driver.java) Error: at com.novell.nds.dirxml.engine.Driver.run(Compiled Code) Error: at java.lang.Thread.run(Thread.java:466) DirXML Driver Initialization Error! I've looked at the code, line 133 is the first trace call that shows "TRACE: VRTest/Driver: Initializing driver shim..."
It's quite unclear why the driver fails to load. Seems there is some more stack information that is missing from the trace. Does the driver need to authenticate to the vrtest server? I don't see a userID or password anywhere in the documentation. My driver is NDS equivalent to admin.
A.
Novell's Shon Vella, on the DirXML Development Team, responded as follows:
Get rid of vrtest_api.jar and replace vrtestdriver.jar with the attached version. There was a minor incompatibility between the original and 1.1.7b JVM used on NetWare (or more correctly a bug in the class libraries for that JVM.)
I also noticed that there are few things that you will have to adjust in the rules to get the driver to work that were not prompted for on the import.
On the driver object, you will need to set the IP address of the Windows 2000 server on the Driver Parameters tab.
The placement rule on the publisher channel needs to have DELILAH_TREE replaced with the name of your NDS tree.
This should get you up and running!
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.