Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

tMicrosoftCRMInput error v2011 / v2016 odatas

Hello,

 

I use TOS for DI v6.4.1

 

I tried 2 onlines connection :

  • v2011 with SOAP service
  • v2016 odata with REST service.

With v2016 odata (REST servce), we have the following error :

 

[pool-2-thread-1] INFO com.microsoft.aad.adal4j.UserDiscoveryRequest - [Correlation ID: null] Sent (null) Correlation Id is not same as received (null).
[pool-2-thread-1] INFO com.microsoft.aad.adal4j.AuthenticationAuthority - [Correlation ID: xxxxxxxxxxxxxxxxx] Instance discovery was successful
[pool-2-thread-1] ERROR com.microsoft.aad.adal4j.AuthenticationContext - [Correlation ID: xxxxxxxxxxxxxxxxxxxx] Request to acquire token failed.
com.microsoft.aad.adal4j.AuthenticationException: {"error_description":"AADSTS70001: Application with identifier 'xxxxxxxxxxxxx' was not found in the directory 

 

Also, I found that issue in Jira : https://jira.talendforge.org/browse/TDI-38648?_ga=2.76931797.116653292.1509977223-680403763.15023518.... It seems to be in relation with that error. Is the bug known and resolved ?

 

--

With v2011 (SOAP Service), we have the following error :

 

Exception in component tMicrosoftCrmInput_10 
org.apache.axis2.AxisFault: The server did not recognise the action which it received.
	at org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:115)

Also, with the same parameters I can read datas extracted from the discovery service : https://disco.crm4.dynamics.com/XRMServices/2011/Discovery.svc

 

 

--

Thank you for your help on one of the solution or both.

 

Regards

 

Labels (5)
6 Replies
Anonymous
Not applicable
Author

Hello,

This jira issue:https://jira.talendforge.org/browse/TDI-38648 has been fixed on V 6.4.1

Could you please also post your  tMicrosoftCRMInput component setting screenshots on forum which will be helpful for us to address your issue?

Note: Please mask your sensitive data.

Best regards

Sabrina

 

Dewey
Contributor III
Contributor III

Ok, the bug was fixed in 6.4.1 but it was reported in 6.4.1 and I also get it in 6.4.1. 

 

In my case it shows the errors but still returns data.

 

I get the same error in 7.0.1.

 

Maybe not actually fixed?

Passaia
Contributor II
Contributor II

Hello,
I'm facing same error with 7.0.1, any news about this topic?
Thanks
Max

Anonymous
Not applicable
Author

Hello @Passaia 

Did you try v2011 or v2016 odata? Would you mind posting your tMicrosoftCRMInput component setting screenshot here?

Best regards

Sabrina

Passaia
Contributor II
Contributor II

Hello Sabrina,
thanks for your help.
I didn't try to change the API version, I kept all the standard configurations to access dynamics online.

Here the screenshots of my tMicrosoftCRMInput, I left the parameters coming from the context file:

 

0683p000009M3tv.jpg0683p000009M3u0.jpg

 

 


Below is what I see during the execution:

0683p000009M3uK.jpg

It seems to be just a warning due to the ongoing multithreading, but after a while I get a timeout.
Any suggestions?

Thank you very much

Massimiliano

David_Beaty
Specialist
Specialist

Hi,

 

Has anyone been able to resolve this issue?

 

Thanks