Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Dirxml.nlm wont stay loaded
8 views
Skip to first unread message
Gary Clarkson
Jan 27, 2004, 7:54:20 PM1/27/04
to
I'm testing the DirXML starter pack. I have built a new NW 6.5 server into
an existing test tree. I've built a new Win2k server and set up AD on it.
The Win 2k server has all service packs and security updates. The NW 6.5
server has not had sp1a installed on it yet. I have intsalled the DirXML
engine on the NW server per the directions. I then installed the remote
loader and Password sync on the Win 2k server. It I go through console 1 to
try to add a user to AD it will not work. The driver does not stay started.
It goes from stoped to started to stoped. When I try to load DirXML.nlm I
get the following error in the DirXML.log.
an existing test tree. I've built a new Win2k server and set up AD on it.
The Win 2k server has all service packs and security updates. The NW 6.5
server has not had sp1a installed on it yet. I have intsalled the DirXML
engine on the NW server per the directions. I then installed the remote
loader and Password sync on the Win 2k server. It I go through console 1 to
try to add a user to AD it will not work. The driver does not stay started.
It goes from stoped to started to stoped. When I try to load DirXML.nlm I
get the following error in the DirXML.log.
[2004/01/27 13:43:01]: DirXML Init: Unable to get EntryID for Driver Set.
Err: failed, no such value (-602)
[2004/01/27 13:43:01]: DirXML Init: DirXML Driver Multiplexer initialization
failed, unloading DirXML Module
Any help would be greatly appreciated.
Father Ramon
Jan 28, 2004, 9:37:50 AM1/28/04
to
See http://support.novell.com/cgi-bin/search/searchtid.cgi?/10064449.htm
--
Father Ramon
The Patron(izing) Saint of DirXML
Gary Clarkson
Jan 28, 2004, 11:19:57 AM1/28/04
to
That was not it. I'm pretty sure I'm doing something fundementaly wrong.
I've installed the DirXML starter pack on the NW 6.5 server and on the W2k
server but I have no drivers running on the NW server. I'm just trying to
sync eDir to AD. In previous versions you could run the DirXML engine and
the driver all on the AD server. I was able to make that work but it was not
a very clean installation. I had to use DirXML 1.1a from NAM 3 and the
password sync from AM 2.1 So I thought I'd start over and just keep it
simple by using the DirXML starter pack from NW 6.5. One of the threads
here says that is the way to go. When I started the installation I was
planing on running all of the componets on one server as I had before (the
single server configuration is illustrated in the documentation of some
version of DirXML) but there is only the option of installing the remote
loader and password sync on the 2k server. So I installed the engine on the
NW server. The documentation for the starter pack does not seem to even
consider that you will not be running a driver on the NW server. But from
looking through the documentation if you are just sync'ing AD to eDir there
is no driver to run on the NW server.
I've installed the DirXML starter pack on the NW 6.5 server and on the W2k
server but I have no drivers running on the NW server. I'm just trying to
sync eDir to AD. In previous versions you could run the DirXML engine and
the driver all on the AD server. I was able to make that work but it was not
a very clean installation. I had to use DirXML 1.1a from NAM 3 and the
password sync from AM 2.1 So I thought I'd start over and just keep it
simple by using the DirXML starter pack from NW 6.5. One of the threads
here says that is the way to go. When I started the installation I was
planing on running all of the componets on one server as I had before (the
single server configuration is illustrated in the documentation of some
version of DirXML) but there is only the option of installing the remote
loader and password sync on the 2k server. So I installed the engine on the
NW server. The documentation for the starter pack does not seem to even
consider that you will not be running a driver on the NW server. But from
looking through the documentation if you are just sync'ing AD to eDir there
is no driver to run on the NW server.
As you can tell from above I'm very confussed at this point and would
appreciate any help.
"Father Ramon" <devf...@novell.com> wrote in message
news:2PPRb.1702$Wh....@prv-forum2.provo.novell.com...
Father Ramon
Jan 28, 2004, 2:59:14 PM1/28/04
to
The only thing that ever causes the problem you are seeing is what was
described in the TID, which is that the server you are trying to run the
driver on is not associated (or not fully associated) with a driver set.
Are you sure you are assigning the right server to the driver set? Are
you sure you have a writeable replica of the driver set partition on
that server? When a server is properly associated, you should never have
to manually load DIRXML.NLM (unless you manually unloaded it) because it
will load automatically at the point when the server becomes associated
and every time DS loads after that.
described in the TID, which is that the server you are trying to run the
driver on is not associated (or not fully associated) with a driver set.
Are you sure you are assigning the right server to the driver set? Are
you sure you have a writeable replica of the driver set partition on
that server? When a server is properly associated, you should never have
to manually load DIRXML.NLM (unless you manually unloaded it) because it
will load automatically at the point when the server becomes associated
and every time DS loads after that.
Gary Clarkson
Jan 29, 2004, 8:03:04 PM1/29/04
to
Well not that I doubt you but the fix in the TID didn't work. I think the
problem was that I had installed NAM 2.1 for AD and then installed DirXML
1.1a and then uninstalled them and went with the DirXML starter pack. I
don't think the uninstall cleaned everything up. For some reason I was
thinking that to move from NT 4.0/NAM 2.1 to AD/NAM 2.1 for AD would be the
simplest way to go. It was not. After I reloaded the W2k server the
install of DirXML went fine it is now working well.
problem was that I had installed NAM 2.1 for AD and then installed DirXML
1.1a and then uninstalled them and went with the DirXML starter pack. I
don't think the uninstall cleaned everything up. For some reason I was
thinking that to move from NT 4.0/NAM 2.1 to AD/NAM 2.1 for AD would be the
simplest way to go. It was not. After I reloaded the W2k server the
install of DirXML went fine it is now working well.
Thanks for the help.
"Father Ramon" <devf...@novell.com> wrote in message
news:mwURb.2104$Wh....@prv-forum2.provo.novell.com...
0 new messages