Novell Messenger 3.0.1
With this version of Messenger when a new LDAP profile is created for Messenger, the nmma and nmaa agents will then fail to load.
This will be fixed in the Messenger ConsoleOne snapin called NVLMessenger.jar file. It will be part of what goes out to the public when Messenger 3.0.2 ships.
This file is found in the /usr/ConsoleOne/snapins/messenger/ directory on Linux and on Windows in the :
The fix is in Messenger Linux Server 3.0.2 build 20150811141750. Source revision 6286 and
Messenger Windows Server 3.0.2 build 201508111418 source revision 6286.
A buffer size limitation was reached and the password supplied was being corrupted with a false value, as listed under the properties of Messenger Service object | Ldap container | child Ldap object | Properties , Ldap Profile tab, General, User Settings at the bottom of the dialog, User and Password . This username and password is what Messenger uses to access the ldap server
A work around is to not use an LDAP profile in which a username and password configured was created with the shipping Messenger 3.0.1 consoleOne snapins. If you have no LDAP profile under the properties of Messenger Service object | Ldap container | child Ldap object | Properties , Ldap Profile tab, General, User Settings at the bottom of the dialog, User and Password , then the Messenger agent will, if configured in it's startup, will contact the eDirectory server directly rather than going thru LDAP and port 389 or 636.