I have some trouble starting the remote loader service for MSOnline. Tried the following: 1) When configured "the usual way" just using the RL Console to select the DXMLMSOnlineDriver.dll I get two lines in the trace: "Verifying command port..." and "Verifying driver can be loaded..." before it shuts down. 2) Found TID 7015184 (https://www.novell.com/support/kb/doc.php?id=7015184) and changed the config.txt by removing the "-module line" and adding the "-class "DXMLMSOnlineDriver.SPDriverShim" and -assembly "C:\Novell\remoteloader.NET\DXMLMSOnlineDriver.dll" which results in an dialog stating: "Configuration file: Unrecognized command line string 'assembly'" and "The driver did not start. Reason unknown". 3) Removed the "-assembly line" and the the driver almost start but ends up with a "Driver shim class DXMLMSOnlineDriver.SPDriverShim was not found", fatal, unable to create driver...
IDM 18.104.22.168 MSODriver 22.214.171.124
Both RemoteLoader(64-bit) and RemoteLoader.Net is installed on the server. Tried it on a member-server (win2012r2) and a DC (win2008r2) where the ADDriver RemoteLoader runs.
Please tell that I just made a typo or some other easy fix :-)
O365 driver (especially old versions of the driver) was extremely "sensitive" to MS support module versions (Microsoft Online Service Sign-in Assistant, Windows Azure Active Directory Module for Windows Power Shell, .Net, VC , etc). Please follow all steps from documentation (don't skip anything).
> Hi > > I have some trouble starting the remote loader service for MSOnline. > Tried the following: > 1) When configured "the usual way" just using the RL Console to select > the DXMLMSOnlineDriver.dll I get two lines in the trace: "Verifying > command port..." and "Verifying driver can be loaded..." before it shuts > down.
Is this the O365 shim? If so, you have to configure it in the RemoteLoader.NET interface, not the usual RemoteLoader interface.
Also, if you have changed the console font (DOS box, cmd.exe, whatever you want to call it) from the default, you'll need to change it back to successfully configure the remoteloader.
Thank you for the suggestions. When I looked at patches yesterday it was the newest available for IDM 4.0.2. I followed the documentation very carefully and I pretty sure to have meet all requirements.
Yes, of cource, Thank you! I had used the default rlconsole. Using the right interface and manually changing both tho mso-config (to use DXMLMSOnlineDriverShim) and the sharepoint-conf (to use port 8002) makes it running and connecting with the driver.
Now I have some other issues but they looks like driver errors which I understand a little better :-) Thank you again.
Hi Martin, Office365 Driver 126.96.36.199 posted in IDM4.5 branch.
This version include many fixes (compare with "original" 188.8.131.52 version). I was sure, that driver supported for both IDM versions (4.02 and 4.5), but now I can see, that IDM4.0.2 support didn't include in the driver description. > System Requirements > Novell Identity Manager 4.5.1 or higher Support for IDM4.0.2 required more clarification...
> Current Fixes and Enhancements (Included in this patch) > Office 365 Driver 184.108.40.206 > Fixes: > - Design choice effects driver performance in some situations. Bug > 926462 > - O365 driver publisher polling gets restricted to 1000 users. Bug > 940944 > > Previous Fixes and Enhancements > > Office 365 Driver 220.127.116.11 > Enhancements: > - Added support of .NET 4.5 Framework > - Added support of latest MS online modules > - Added two new user types support – UserMailbox and MailUser > - Added native Powershell support – Capable of executing PS > commands by the driver > - Added support of most of Azur and Exchange Schema attributes > Fixes: > - Office 365 shim needs native PS interface. Bug 800676 > - Office 365 - Need support for hybrid mode. Bug 885228 > - Office365 Questions - "TypeInitializationException. Bug 904908 > - Ehn: Full Schema Mapping to Azur. Bug 906780 > - Ehn: multivalue attributes should be handled correctly. Bug 906782 > - Office 365 query for user license returns zero results. Bug 913326 > - Driver fails to set the ManagedBy attribute when a group is created. > Bug 922379 > - No way to set a groups Alias, Display Name and Email Address when > creating a group of Group Type = > MailEnabledSecurity. Bug 922381 > - Adding a user to group fails if user has an apostrophe in the UPN. Bug > 922799 > - Office 365 requires publisher channel to be active. Bug 926456 > - Office 365 Invalid Sync Attribute:LicenseAssignment. Bug 926459 > - Apostrophes in the Department field are not handled properly, Bug > 926460 > - Office 365 issue with spaces in group alias names. Bug 926465 > - Primary SMTP Address overwritten on Modify of Email Address attribute. > Bug 928091 > - Resetting of UserPrincipalName does not correctly escape Apostrophe. > Bug 928672 > - Office 365 driver filter change causes driver anomaly. Bug 930774 > - Investigate driver allowing sub events when rebuilding the cache > files. Bug 930921 > - Remove-all of EmailAddresses fails to remove all the Email ids. Bug > 931752 > - Add EmailAddresses to O365 Driver filter. Bug 934019 > - Office 365 should not have errors/warnings during normal operations. > Bug 934778 > > Office 365 Driver 18.104.22.168
And I am back... The driver and remote loader starts up and connect, but then I get an fatal error: "Exception caused by DriverShim.getPublicationShim() at DXMLMSOnlineDriver.Schema.MSolschema.getClass(String className) at DXMLMSOnlineDriver.SPPublisherShim..ctor(SPDriverShim driverShim) at DXMLMSOnlineDriver.SPDriverShim.getPublicationShim() at DXMLRemote.loader.Driver.startDriver(XmlDocument initDocs)" and then the driver shuts down. I have tried updating with 22.214.171.124 but then RL can not start, stating that "...assembly is built by a runtime newer than the currently loaded runtime..."
On 29/01/16 09:24, moldin wrote: > > Thank you for the suggestions. > When I looked at patches yesterday it was the newest available for IDM > 4.0.2. > I followed the documentation very carefully and I pretty sure to have > meet all requirements. > > - martin > >
We do support the IDM 4.5.x .Net RL running the Office 365 driver with IDM 4.0.2 Patch 7 engine.
cpedersen;264605 Wrote: > On 29/01/16 09:24, moldin wrote: > Hi Martin, > > We do support the IDM 4.5.x .Net RL running the Office 365 driver with > IDM 4.0.2 Patch 7 engine. > > But it would be nice if people would update... > > Casper
Thank you for your clarification, Casper! I remember something about support for IDM 126.96.36.199, but always better to have "official" confirmation! :)
Hi Martin, It can make sense (especially after Casper comments): new 188.8.131.52 driver has "different" pre-requirements: new VC , new .Net and new build of ..Net Remote Loader. End state is: IDM Engine v184.108.40.206 connect to .Net RL v4.5.3.
In your case (I believe) you have IDM Engine v4.0.2.x connect to RL v4.0.2.x.