Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
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 'http://tempuri.org/:queryBuilderArgs' contains data from a type that maps to the name 'http://schemas.datacontract.org/2004/07/XppClasses:SRSQueryBuilderArgs'. The deserializer has no knowledge of any type that maps to this name. Consider using a DataContractResolver or add the type corresponding to 'SRSQueryBuilderArgs' 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.
Yesterday, a new build was released to production. This is what has been done:
:" ... Ax Prod has been updated to build 188.8.131.52.All AOS’es were stopped during deploy of new code (22:30-23:30). No security roles were imported from the USR layer. No services were refreshed. No reports were deployed. EP were not deployed. VS assemblies were deployed on all AOS servers.The build included a MS fix for the batch processing."
After everything possible was restarted, re-deployed and refreshed, the error is gone.
try re-deployment and restart...
Reason is when your report server or reporting AOS crashed or stopped without endding user session related to BC connector ,
OnlineUser's should be drained first before you take down your AOS .If its taking very long and your AOS is completely spiking kill the AOS process and then delete SysClientSessions records related to this AOS instance
and then , start all your services. Server draining should happen prior to AOS restart or else you will definitely end up with such issues. Happened to me several times
Make sure there are no compile errors and generate full CIL. Memory consumption might grow on the AOS Service, so you may want to keep that in mind.
When CIL is generated, memory consumption should drop again, and hopefully the error will be gone.
This happens quite frequently when AOS serving the reporting server crashes .Faced this several times.The way out for this is kill the AOS process (serving reports). Delete the Records in SysClientSessions for this AOS from database. Now start the AOS service . Its good to use.
I got this problem and follow your instruction by stop AOS process, and deleted all records in SysClientSession table. But the error still existed.
- Restart AOS
- Delete records in table SysClientSession
- Restart SSRS service
- Compile and Full CIL generate
If you have other solution, kindly suggest.
My case i have 100+ users accessing reports on an 8gb virtual AOS server where the memory utilization reaching 7.9 gb and caused the AOS to stop responding.
Things i followed was to drain the online users if any present.
Since you have deleted all the SysclientSession records.
Check the Temp files in you AOS server locations and try by deleting them.
C:\Users\AOSAccount\AppData\Local, Delete the all the AUC and KTI files.
Stop and start the service.
I din't need a CIL since i was sure that there were no changes made in the environment.
Thank you so much, its work now with your instructions. Super thanks for your help ^ ^.
I have encountered the same issue on a Prod Environnement.
3 AOS, one dedicated for Reports/Batchs/EP
I've got the message that usually refer to Inbound Port issue. This time it was a problem between SSRS/AOS and SQL.
I have tried - to desactivate/reactivate Inbound POrts as usually- to restart SSRS service and purge AUC.
Once the service restarted, there was no AUC files on SSRS.
I have stopped the AOS, purged SQL Records in sysclientssessions table related to this AOS and stopped ssrs.
After both AOS and SSRS restarted, Reports working properly.
Thanks for the TIPS.
In our case it was the live DB that ran out of disk space
the following steps were done to fix it:
- allocated more disk space on the db
- restarted reporting service
- in AOT we redeployed the "BI Services" Service Group
Fortunately no AOS reboot was necessary.
HI All in our case we restarted all AOS and SSRS and it worked.
1. Clear all chace
2. AOT-->Service Groups-->Klik kanan BLService-->Deploy Service Group
This issue has terrible consequences when a over 200 users are working. Restart AOS???
Is there any official explanation for this issue in order to avoid it from happening or a fix that doesn't require service restart?
Only Disable BIServices service and then enable again. It work for me.
Path. Adiministration - setup - AIF - Entry port
Thanks this actually solved the problem for me also.
Please follow the below steps.
1) Stop the AOS services(if multiple AOS instance, turn off all the AOS services)
2) delete from sysusersessions.
3) delete from sysserversessions.
4) clear the temp folder
4) delete the .auc files in Appdata-->Local-->Microsoft-->DynamicsAX and its sub folders.
5) Start the service.
IT should work. :)
Danke Angelika Wurz!
Thanks Ismael. It solved the problem for me also. any Idea why this issue is occurring.
Business Applications communities