We had an IDM O365 driver up and running. IT was running on a SLES 11
server with IDM 4.0.2. and eDir 8.8 SP8. We use a remote loader on
Microsoft 2012 server.

We were in the process of moving from SLES to MS 2012 servers. We
installed 3 new MS servers and synced them with the eDir on the two old
SLES servers. All 5 servers were up and running and replicating ok for a
few days without any influence on the O365 connectors. At one point (2.
or 3. October), we rebooted the SLES computes. After that, we were not
able to make any of our O365 drivers to work. All other drivers on the
same server worked OK, including an AD driver. We do not know whether
the reboot is of any significance to the problem. Even so, that is the
only thing we can think off between a situation where we had a working
O365 drivers and full stop.
We get the following error message in the Log on Remote Loader:


DirXML Log Event -------------------
Driver = \METAKAT\Tjenester\Metakat Driver Set\O365 - HiL ansatte
Thread = Subscriber
Level = fatal
Message = Exception caused by DriverShim.getPublicationShim()
at DXMLMSOnlineDriver.Schema.MSolSchema.getClass(Stri ng className)
at DXMLMSOnlineDriver.SPPublisherShim..ctor(SPDriverS him driverShim)
at DXMLMSOnlineDriver.SPDriverShim.getPublicationShim ()
at DXMLRemote.loader.Driver.startDriver(XmlDocument initDocs)
DirXML: [10.09.14 15:49:29.831]: TRACE: Remote Loader: Sending...
DirXML: [10.09.14 15:49:29.839]: TRACE:
<nds ndsversion="8.x" dtdversion="3.5">
<output>
<status level="fatal" type="remoteloader" event-id="report
status">Exception caused by DriverShim.getPublicationShim()
at DXMLMSOnlineDriver.Schema.MSolSchema.getClass(Stri ng className)
at DXMLMSOnlineDriver.SPPublisherShim..ctor(SPDriverS him driverShim)
at DXMLMSOnlineDriver.SPDriverShim.getPublicationShim ()
at DXMLRemote.loader.Driver.startDriver(XmlDocument
initDocs)</status>
<init-params event-id="write-state" />
</output>
</nds>


After this, the driver shuts down on the server side.

We have three hypothesis to what can be the problem:


- eDirectory is the problem. eDir on the new serves could be
incompatible with the drivers. This did not take effect on the SLES
servers until reboot were performed.
- Remote Loader is the problem. New Microsoft updates on RL could be
incompatible with NetIQ software.
- The connection between server and RL is not working properly.
Passwords or port definitions or openings might be the cause.


We have tested different things.


- We have moved the O365 drivers to one of the new MS 2012 servers.
- We have changed passwords, both on the server and RL side, several
times.
- We have made sure all service packs and patches are up to date on
drivers, IDM, and eDir.
- A consultant that has the same problem with another customer has
tried to install the drivers fresh on a separate server in a new
driver set.
- We have checked openings in firewalls and the port definitions in
the instances for O365 on RL.


We have googled the error message and related terms. It seems like no
one has documented anything about this problem before. Yet we have to
cases of the same problem in our own neighborhood.

B. Hafstad


--
Bjornulf
------------------------------------------------------------------------
Bjornulf's Profile: https://forums.netiq.com/member.php?userid=8271
View this thread: https://forums.netiq.com/showthread.php?t=51930