ReportServer Forum

dkwfung

Member

Registered: 2024-04-25

Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

Dear all,

I found a problem in synchronization of LDAP group.  When I removed LDAP group in Active directory and execute ldapimport.groovy, it will be failed to synchronize user and group from Active Directory to reportserver.

The error is as follows:
reportserver$ exec -c ldapimport.groovy
Script execution failed.
error message: javax.script.ScriptException: net.datenwerke.rs.ldap.service.ldap.exceptions.LdapException: net.datenwerke.rs.ldap.service.ldap.exceptions.LdapException: Failed to import user data from directory: Overall nodes in ReportServer: 5236,  Inhibited nodes: 800, Nodes in directory: 4435, 4436 != 4435 (overallNodes - inhibitedNodes != nodesInDirectory)  (net.datenwerke.rs.ldap.service.ldap.exceptions.LdapException)
script arguments:
file: ldapimport.groovy (id: 6041, line 23)
line number: 23 (223, 261, 332)

Grateful if you could let me know how to solve the problem, please.

Thank you

Regards,

David

Last edited by dkwfung (2024-05-23 05:43:42)

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

Hi dkwfung,

this seems to be a bug/an issue when deleting Groups from the Active directory. We raised RS-8414 and will look into this.
In the meanwhile, you can manually delete the group from ReportServer.

Regards,
Eduardo

dkwfung

Member

Registered: 2024-04-25

Re: Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

Hi Eduardo,

I would like to know whether you have targeted date to solve the problem.

Thanks for your help.

Regards,

David

adrian1703

Moderator

Registered: 2021-10-29

Re: Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

Hello,

We do not have targeted dates for certain tickets.
Although this one in particular will probably be resolved in the version following 4.7.

Kind regards,
Adrian

dkwfung

Member

Registered: 2024-04-25

Re: Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

Dear all,

Would you please let me know any tentative schedule for 4.7?

I would like to confirm whether version 4.5 has the same problem or we should use version 4.5 instead of 4.6.

Thank you

Regards,

David

adrian1703

Moderator

Registered: 2021-10-29

Re: Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

To clarify - It will not be solved for version 4.7 but (probably) the version following 4.7

4.5 and other previous version have the same issue.

Kind regards,
Adrian

dkwfung

Member

Registered: 2024-04-25

Re: Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

Hello Adrian,

Thanks for your clarification.

I would like to clarify that the bug will be fixed after version 4.7.  For example, it will be fixed version 4.7.1.

Please let me know if I am misunderstanding.

On the other hand, do you have any workaround except the group was deleted from ReportServer manually?

Thank you for being patient with me

Regards,

David

Felix

Moderator

Registered: 2022-08-01

Re: Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

Hi,

we're currently finalizing v4.7 and haven't planned following releases in detail at this point. Maybe this bugfix is released in a patch version (4.7.X) but can also be part in a next minor release (e.g. 4.8) ... but it will be fixed in the future

For a workaround: may I ask you what Reportserver version you're using?

kind Regards

Felix

---

Softwareentwickler bei Infofabrik

dkwfung

Member

Registered: 2024-04-25

Re: Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

Hello Felix,

Thanks for your reply.

I am using ReportServer Enterprise Edition v4.6.3.

Regards,

David

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Failed to sync from AD to ReportServer Enterprise Edition v4.6.3

Hi David,

as previously noted, you can delete a group in ReportServer when it has been removed from your LDAP. This should be an infrequent occurrence.

We will address this issue and include the fix in an upcoming patch release. Thank you for your patience.

Regards,
Eduardo