Hi ​@anders.bengtsson 

I better add my response here as well.

In the old program, we would do it with OLE DB provider pointing at the Microsoft Directory Services provider.

 
If you search for Active Directory in the portal you have two options REST and the one from above.

For the old setup, I also had to use queries like this to make it work.

You can make similar queries in the Query table tool. You will not see any tables when you run the Manage Metadata Sync task before you have done this.

Hi ​@anders.bengtsson does the above comment answer your question? Please let us know if you have any follow up questions

Is there an example of the new Microsoft Ole DB provider for directory services? I have the connection properties of the old situation, but donb't know how to transfer this one to the new one…

Regards,

Guido

​@GuidoRitzen which version of TimeXtender are you using?

In TimeXtender 20.10 you can add Any Source OLE DB providers in the Business Unit:

In TDI you can use the below provider, or private data source

Please let me know if you have any follow up questions

Hi Christian,

I'm using (cloud) TimeXtender Data Integration version 6848.1

I don't no what information I need to fill to connect to the on prem AD:

An example would be great.

Regards,

Guido

​@GuidoRitzen can you please send a link to download/documentation for the Microsoft Ole DB provider for directory services?

https://learn.microsoft.com/en-us/office/client-developer/access/desktop-database-reference/microsoft-ole-db-provider-for-microsoft-active-directory-service 

​@GuidoRitzen thanks do you have the download link?

I did it via TX Data Integration. Tools > Add Private Data Source > OLE DB…

Like you suggested above.

Maybe better to have a short call?

Hi ​@GuidoRitzen please send the download link. If the provider needs to be downloaded and installed before it can be used so this is the first step

I don't get it. It is all standard TimeXtender, I didn't download anything...

​@GuidoRitzen 

The provider you are referring to is not a standard TimeXtender provider. It is an external OLE DB driver which TimeXtender can connect to.

For example if I want to use the below SQL OLE DB provider (in this example it is SQL provider but it could also be another OLE DB provider such as the one you mention)

https://learn.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver16

Then I would download the driver and install it, and then create a udl file (make a text file and rename it to include the udl extension e.g. filename.udl)

Then I double click on this file, choose the provider and fill out the necessary connection settings and click OK.

In the TDI portal, create the OLEDB data source and point to the UDL file

Please let me know if I have misunderstood something, or if you have any follow up questions

​@GuidoRitzen does the above answer your question? Please let us know if you have any follow up questions

Hi Christian, 

We have done what you asked and created the UDL File.

But this is not working, we get the following error: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

At datasource we filled in the IP adres of the AD environment and at location the port. Still not working, do you know what we need to fill in there? 

​@GuidoRitzen can you please confirm where you got the error? i.e. When testing the connection from the UDL or when testing the connection from TDI? Can you please send the full error message?

I get the error while testing from the Data estate portal and within TX Data Integration and within the UDL.

Data estate portal:

TX Data integration:

UDL: 

I tested also if I can reach the AD server via Powershell and this is succesfull. So no issue with the firewall

​@GuidoRitzen do you have the download link for the provider you have installed? Which provider have you selected under the provider tab in the UDL file? What happens when you click Yes to the error that appears when testing connection in the UDL file? The UDL file test connection needs to be successful for it to work in TimeXtender

What I did to get the provider:

In TX Date Integration, under Tools > Add Private Data Source > Next > OLE DB Next > I selected the x64 bit version from this Yellow Provider:

Then Next and Finish in this screen:

​@GuidoRitzen  OK please create a Oledb data source in the portal instead of a private data source. Does this fail with the same error when you test the connection for this Oledb data source in TDI? Do you notice any errors in the event viewer?

Please also provide the download link you used to download the provider. As mentioned before, it is an external provider, so it is not provided via TimeXtender and therefore it has to be installed from somewhere

Hi Christian,

I created the OLEDB datasource, same errors in the portal and in TDI. So no change...

As I said, I did not download or install anything for that provider. I have checked my download folders to be sure but nothing there. I'm the only one here working with TX...

​@GuidoRitzen do you see any error messages in the event viewer (under windows logs > application) when you test the connection in the UDL file or TDI?

​@GuidoRitzen the data source location IP address you have provided, is that a different server than the server where you have the udl file currently and running TX from? If so can you please try creating the udl file on that specified location server and testing the connection there?

​@GuidoRitzen I will go ahead and close this, please reply if you have any additional questions/updates :)