I'm using the LDAP adapter to attempt to report off our AD tree. Any time I attempt to create a JOIN using the LDAP data source as the cross-reference file I get the error "(FOC36721) Failure to perform LDAP search". I have no issues if I use the LDAP data source as the source file for the JOIN. Searching for the specific error message didn't yield any results.

Is this a limitation in the software, or perhaps something I'm doing? Maybe the way I generated the metadata? This is our first attempt at using the LDAP adapter.

My task is to determine which users are missing from a particular OU in AD, so using AD as the cross-reference file seems like the logical approach.

Thanks in advance for any insight.

This message has been edited. Last edited by: brjohnson,

Though this is not really an answer to why you can't JOIN to the master file created on the LDAP adapter (I'll leave that up to the experts), there may be a way around it.

As it seems as if you can actually query it, why not do that, HOLD the results and then join to that HOLD from your "users" table?

That's how I would do it anyway. I am always skeptical about JOINing disparate data sources even if WebFOCUS syntax allows me to. I prefer the read1/hold1-read2/hold2-readn/holdn-join/match approach which has proven to be easier to debug and tune than trying to put all together in a single structure.

As the sources are disparate, WebFOCUS will still need to break it in separate requests anyway (or worse, looping in some cases) in order to get you the results.

TABLE FILE LDAP_AD_MASTER
PRINT OU
      ..any_relevant_fields_from_AD..
BY USER
ON TABLE HOLD AS HLDAPINF FORMAT FOCUS INDEX USER
END

Then JOIN to/from HLDAPINF on HLDAPINF.USER as you see fit.

Hope that helps!

Thanks so much!

This approach works well.