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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / .NET Assembly Transfor...
Microsoft Dynamics AX (Archived)

.NET Assembly Transform Malformed XML

(0) ShareShare
ReportReport
Posted on by Ashish langhnoja 80

I have created AIF services with some Out of the box service like item, BOM service and a Inbound .net assembly transform to convert client's XML and pipeline outbound transform to add tages in outbound message.

In our test environment when we test this functionality it works fine for first 15 to 20 minutes after that services starts giving Malformed XML error. If we restart our port then again it works for 15 to 20 minutes. When I see exception log there is only error like error in transform. But I have .net test application which can test same client's xml and it works fine with .net assemble. And after restart of port if I use same xml it works.

If anybody have faced or have solution of this kind of problem please suggest.

Thanks in advance.

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    Martin Dráb 237,965 Most Valuable Professional on at

    Can you tell us exactly when/where do you get these errors? Did you try logging outputs of the transformation? Doesn't it throw an exception?

  • Ashish langhnoja Profile Picture
    Ashish langhnoja 80 on at

    Hi Martin,

    Thanks for reply, We are logging original document, and it throws error randomly, no particular time. is it to do with any temporary folder?

    It throws error like error in transform and malformed XML, but When I use same xml after restarting port it works.

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

    If, for example, your transformation function throws an exception (for whatever reason), observing the original document will tell you absolutely nothing.

    You still have work to do on diagnostics.

  • Ashish langhnoja Profile Picture
    Ashish langhnoja 80 on at

    I am saving original document as log for later use,

    can you give me some idea how to diagnose this kind of issue, like it fails randomly.

  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 237,965 Most Valuable Professional on at

    As I suggested by my questions, I think it would be useful to log the transformed file (to see whether it's malformed or not) and log exceptions, especially in the transformation library (but it might be also useful to identify the place in AX throwing the exception). If I found that the problem is somewhere in the transformation library but failed to identify it exactly, I would write additional trace messages there, log them to a file and analyze after a failure.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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