Page 1 of 1

Creating connection to Active Directory

Posted: Fri Mar 12, 2010 3:12 am
by sreimert
Using PrimalSQL 2009 (1.1.2) I am trying to connect to our Active Directory using the OLE DB Provider for Microsoft Directory Services.I can complete the new connection menu with no errors, and I get a successful test. When I set the connection as the active connection, I get the red check mark.However, when I query the database I get a message stating (exactly):"Current provider does not support schema recordets" (note typo).Is there a way to query Active Directory with PrimalSQL?Thanks!

Creating connection to Active Directory

Posted: Fri Mar 12, 2010 6:21 am
by davidc
This message is generated my the provider and not PrimalSQL.

1. Does this error occur on a particular query or on all queries?
2. Is anything displayed in the database tree? I.e. Tables etc.

Thank you,

David


Creating connection to Active Directory

Posted: Fri Mar 12, 2010 6:59 am
by sreimert
Thanks for the quick response. I understand that the message is passed-through from the provider. In answer to your questions:1) I cannot make any queries at all - I get the message when I try to connect.2) I do not get table or view trees shown.The sequence is basically thus:1) Create the connection (right-click, Create a new connection)2) Select the OLE DB Provider for Microsoft Directory Services provider, then Next.3) Leave Data source empty (or put in domain controller, makes no difference). Leave Location empty. Use integrated security (I'm an Admin -- there are no permissions issues).4) Click Test Connection (succeeds). Click OK. Name connection.5) Double-click connection. Turns yellow, but nothing else happens.6) Select "Set as Active Connection" - also does nothing.7) Select "Query database" - then the "Current provider does not support schema recordets" error comes up. Typo is a little surprising, actually.Let me know if you have any more questions, I'd love to get this working!--Scott

Creating connection to Active Directory

Posted: Fri Mar 12, 2010 8:24 am
by davidc
We will need to investigate further and we have to see if we can recreate the issue.


Thank you for detailing the steps,

David