are there known workarounds, patches, or other methods available (short of changing our a.d. environment) allow livecycle communicate our active directory environment?
our active directory environment set use referrals. according adobe documentation, livecycle not support ldap referrals.
when attempt use ldap search qpac in workflow, receive "unprocessed continuation reference" errors research reveals related ldap referrals.
thanks assistance can provide.
our active directory environment set use referrals. according adobe documentation, livecycle not support ldap referrals.
when attempt use ldap search qpac in workflow, receive "unprocessed continuation reference" errors research reveals related ldap referrals.
thanks assistance can provide.
hi david,
well, ldap qpac kind of...sucks no fun. honestly, in release 7.0572 things improved quite lot.
you may want read following threads:
especially first one.
steve
well, ldap qpac kind of...
you may want read following threads:
-
- adobe forums - ldap qpac weird exceptions
- adobe forums - ldap qpac: output in testing tab , contents of process variable differ significantly
- adobe forums - ldap qpac: how store multiple results in process variable?
especially first one.
steve
More discussions in LiveCycle pre-ES (6.x and 7.x) discussions
adobe
Comments
Post a Comment