web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Multiple aos webservice connection issue

(0) ShareShare
ReportReport
Posted on by 32
We have 4 AOSes (3 + 1 batch aos) based on one database.
There are 3 custom components: ax Class, that calls external c# dll, C# DLL, that calls AOS webservice and AOS webservice, that allows to create new records in ax.
1.AOS -> 2.DLL -> 3.AOS webservice
The logic is to call from ax functionality, get external information, process it and then store into ax.
Since all AOSes based on one database, we want to have a deployed webservice only on batch aos.
So when we call a DLL, we pass to it batch aos webservice endpoint address.
If we make call from batch aos, everything works good by a standard scenario defined before. So it looks like this: BATCHAOS -> DLL -> BATCHAOS
But when we try to make a call from another aos ( AOS1 -> DLL -> BATCHAOS), we get an exception "a call to sspi failed see inner exception", that appears in DLL on ServiceNameClient object, when .create() method is called.
We checked webservice endpoint address and ports, so in dll app.config endpoint address is correct.
The question is: What should we do to be available to call webservice on one from another?
Bellow you can see screenshots of batch aos webservice, deployed dll app config and code block, where communication object is created. Screenshots are from batchaos only since all of aoses uses the same dll. In app config endpoint address is got from webservice URI addres and AOS_SERVICE_HOST is replaced with aosName+URI port
pastedimage1568808157340v1.png
pastedimage1568808179518v2.png
pastedimage1568808238691v4.png

*This post is locked for comments

I have the same question (0)
  • AlexanderZh Profile Picture
    32 on at

    Hope you can help me,

    respectfully,

    Alexander Zharkov

  • Martin Dráb Profile Picture
    237,880 Most Valuable Professional on at

    Why exactly do you want your environment to communicate with itself via web services? It sounds like a waste of resources to me.

    Your requirement "to call from ax functionality, get external information, process it and then store into ax" doesn't require it. The batch could get the external information and save it, which is much simpler.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans