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) / The formatter threw an...
Microsoft Dynamics AX (Archived)

The formatter threw an exception issue....

(0) ShareShare
ReportReport
Posted on by Community Member

Hi all

Please help us find a fix for the following issue:

 The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://tempuri.org/:queryBuilderArgs. The InnerException message was 'Element 'tempuri.org/:queryBuilderArgs' contains data from a type that maps to the name 'schemas.datacontract.org/.../XppClasses:SrsReportProviderQueryBuilderArgs'. The deserializer has no knowledge of any type that maps to this name. Consider using a DataContractResolver or add the type corresponding to 'SrsReportProviderQueryBuilderArgs' to the list of known types - for example, by using the KnownTypeAttribute attribute or by adding it to the list of known types passed to DataContractSerializer.'. Please see InnerException for more details

*This post is locked for comments

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,037 Super User 2025 Season 2 on at

    Hi ITcops,

    Can you provide some background information about what you were starting/running? Which feature is affected here?

  • Sohaib Cheema Profile Picture
    Sohaib Cheema 49,438 User Group Leader on at

    I went through this issue, last week on a client and found that there was "no specific reason" for issue. Our infrastructure for that client was having reporting server based on an AOS that is Batch AOS and users are not allowed to have any RPC sessions on Batch server. We have total of 6 other AOS servers for client sessions.

    doing following fixed issue for us.

    1) restarted Batch server AOS service (in your case you may have single AOS)

    2) restarted Reporting service.

    Please note that reporting works on web services, which are linked to an AOS. so you need to watch which AOS is supporting your Reporting.

    I would recommend following in worst case (if reporting was working already)

    1) stop AOS service for all boxes

    2) delete content of xppil folder

    3) truncate table SYSXPPASSEMBLY

    4) Start AOS service of a single box, on which you intend to rebuild ax.

    5) Build AX

    6) generate full CIL

    7) Restart AOS service of the box on which you generated CIL.

    8) synchronize DB

    9) Restart AOS service of the box on which you updated cil.

    10) restart aos service for the instance on whcih reporting is based. this is for case if you have multiple AOS servers.

    11) restart sql server reporting service.

    12) restart all remaining aos boxes' AOS service (one by one) to get updated CIL.

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