Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We upgraded Qlik NPrinting to May 2023 SR3 in DEV Environment and we can see after the upgrade only Import task were failing.
Import tasks were created to import users from LDAP Connection. Same connections were working fine before the upgrade.
No issues with username and password as we were using same credentials to fetch users in PROD NPrinting also.
ok... and what do you see in logs regarding this issue...?
Hi,
Nothing was changed andot LDAP users import in May 2023 SR3 https://community.qlik.com/t5/Release-Notes/Qlik-NPrinting-Release-notes-May-2023-Service-Release-3/... so I expected that a working import will continue to run correctly.
Please note that Import tasks can be run in Test Mode https://help.qlik.com/en-US/nprinting/February2024/Content/NPrinting/DeployingQVNprinting/Import-Use... I suggest you to do it and download the related log file. In the log file there should be meaningful error message: apply the related suggestions or share the errors here so we could have an idea of what is going wrong.
Best Regards,
Ruggero
In the import log i'm getting the error like below,
Error ERROR: 000004DC: LdapErr: DSID-0C090BA8, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, v3839 ---> An operation error occurred.
Below is the error when i ran in test mode,
:389 declares to support at least one type of paging control, but the paged search failed. System.AggregateException: One or more errors occurred.
Error ERROR: 000004DC: LdapErr: DSID-0C090BA8, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, v3839 ---> An operation error occurred.
But we haven't changed anything after upgrade. the task which was working fine before the upgrade got failed after the upgrade, is there any other logs we need to refer.
Also, we tried to run on other ports secure and Global catalog ports (in 389 which we were using, immediately failed with above mentioned error, when we tried to run on other 2 ports, tasks were keep on running, which causing the services down and also no error coming in the import logs.
Default: 389
Secure: 636
Global catalog: 3268
Hi,
Check that the Windows user that runs the Qlik NPrinting Scheduler service can connect to the LDAP server. You can use a third party tool to check this.
Be also sure that nothing was changed in the Active Directory configuration.
Best Regards,
Ruggero
Hi,
Windows user that runs the Qlik NPrinting Scheduler service can connect to the LDAP server - Yes able to connect, we have four different domains one of the domain which has less number of user (<5), where the task successfully completed but we ran with 3268 port (but the same not running with 389 port)
Ans also same task with not running for other domains has more user i.e 100+ user (we mention the domain in filters)
Hi,
I think we have too few information to understand which is the source of the issue. I suggest you to open a support ticket linking this conversation and with full log files of the failing import tasks.
Best Regards,
Ruggero
We opened a case for this issue 00163858.