Finance | Project Operations, Human Resources, ...

how to use the Dynamics 365 Finance WCF service.

(0) Share

Report

Posted on by dongwoon

350

I'm working on a DevVM created for development in MS LCS.

I created a service and a service group.

Custom service development - Finance & Operations | Dynamics 365 | Microsoft Docs

And I am trying to create data in the Test table using the Service I created with WCF test client.

https://tymbuild59019c08b8add779devaos.cloudax.dynamics.com/en/api/services/TYM_AxApiServiceGroup/TYM_WCFService/CreateTest

Error Message : Error: Cannot obtain Metadata from tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../CreateTest If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. For help enabling metadata publishing, please refer to the MSDN documentation at go.microsoft.com/.../ Exchange Error URI: tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../CreateTest Metadata contains a reference that cannot be resolved: 'tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../CreateTest'. An error occurred while receiving the HTTP response to tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../CreateTest. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The underlying connection was closed: An unexpected error occurred on a receive. The client and server cannot communicate, because they do not possess a common algorithmHTTP GET Error URI: tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../CreateTest There was an error downloading 'tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../CreateTest'. The underlying connection was closed: An unexpected error occurred on a receive. The client and server cannot communicate, because they do not possess a common algorithm

What do I need to set up in Dynamics 365 Finance to use WCF Service?

In ax 2012 there is a setting.

dynAmiX : Export Data with Outbound ports in AX 2012 (msdynamix-ax.blogspot.com)

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Martin Dráb 239,057 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

You're using a wrong URL.

tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../... is the JSON-based endpoing, while you want the SOAP endpoint: tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../TYM_AxApiServiceGroup

Was this reply helpful? Yes No
dongwoon 350 on at

Like (0)

Report
Copy link

Link copied!

thanks.

I did the url you told me, but the following error occurs.

Error: Cannot obtain Metadata from tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../TYM_AxApiServiceGroup. If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. For help enabling metadata publishing, please refer to the MSDN documentation at go.microsoft.com/.../ Exchange Error URI: tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../TYM_AxApiServiceGroup. Metadata contains a reference that cannot be resolved: 'tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../TYM_AxApiServiceGroup. An error occurred while receiving the HTTP response to tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../TYM_AxApiServiceGroup. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The underlying connection was closed: An unexpected error occurred on a receive. The client and server cannot communicate, because they do not possess a common algorithmHTTP GET Error URI: tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../TYM_AxApiServiceGroup. There was an error downloading 'tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../TYM_AxApiServiceGroup. The underlying connection was closed: An unexpected error occurred on a receive. The client and server cannot communicate, because they do not possess a common algorithm

Was this reply helpful? Yes No
Martin Dráb 239,057 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Please try it with a standard service group instead. Maybe yours isn't implemented correctly.

Was this reply helpful? Yes No
dongwoon 350 on at

Like (0)

Report
Copy link

Link copied!

ok. I had test for services group, 'usersessionservice'.

But there is still an error.

tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../UserSessionService

--------------------

Error: Cannot obtain Metadata from tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../UserSessionService If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. For help enabling metadata publishing, please refer to the MSDN documentation at go.microsoft.com/.../ Exchange Error URI: tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../UserSessionService Metadata contains a reference that cannot be resolved: 'tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../UserSessionService. An error occurred while receiving the HTTP response to tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../UserSessionService. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The underlying connection was closed: An unexpected error occurred on a receive. The client and server cannot communicate, because they do not possess a common algorithmHTTP GET Error URI: tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../UserSessionService There was an error downloading 'tymbuild59019c08b8add779devaos.cloudax.dynamics.com/.../UserSessionService. The underlying connection was closed: An unexpected error occurred on a receive. The client and server cannot communicate, because they do not possess a common algorithm

Was this reply helpful? Yes No