COmanage Users List

[Scott Koranda <>]

Hi John,

Thanks for confirming those first simple troubleshooting steps.

I don't have a COmanage Registry deployment with LdapSource
installed/configured, but I do have a number of LDAP servers at my
disposal so I can spin one up tomorrow.

Then I will do a sanity check test. If I find a bug I will let you know.
If not I will send you (off list) an instrumented version of the
LdapSource code so you can get more logging information about what might
be going on.

In the meantime, if you can send me (off list) your LdapSource
configuration that would be helpful. If you have access to the database
you can just dump the table cm_ldap_sources (and XXX out the password if
it is not encrypted).

Thanks,

Scott

> Ah okay, thanks for the clarification.
> I went through the steps again and I still get the same 'Database save 
> failed: OrgIdentity saveAssociated' error when trying to import a single 
> record.
> 
> Thanks,
> John
> 
> 
> On 3/15/22, 1:12 PM, "Scott Koranda" <> wrote:
> 
>     [You don't often get email from . Learn why this 
> is important at http://aka.ms/LearnAboutSenderIdentification.]
>     
>     Hi,
>     
>     > Loading schema from file 
> /srv/comanage/comanage-registry-4.0.1/local//Plugin/LdapSource/Config/Schema/schema.xml...
>     
>     The line above means that the plugin and its schema were found and
>     processed.
>     
>     > Possibly failed to update database schema
>     
>     That line is a "red herring". The schema management tool used in
>     COmanage Registry 4.x (Adodb, which will be replaced in the 5.x series)
>     will output that line even if the schema was processed correctly. You
>     can safely ignore it.
>     
>     Please continue by deleting the cache (again) and then trying to import
>     a single source record and let's see if you get the error again.
>     
>     Thanks,
>     
>     Scott
>     ** This email originated from an EXTERNAL sender to CHOP. Proceed with 
> caution when replying, opening attachments, or clicking links. Do not 
> disclose your CHOP credentials, employee information, or protected health 
> information to a potential hacker**.
>     
>