SBX - Search With Button

SBX - Forum Post Title

SSRS error: There was an error while trying to deserialize parameter http://tempuri.org/:queryBuilderArgs

Microsoft Dynamics AX Forum

Oleksandr Nazarov asked a question on 25 Sep 2013 1:40 AM
My Badges

Question Status

Verified

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 '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 1.1.5.0.
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."


Thank you

Reply
Oleksandr Nazarov responded on 25 Sep 2013 3:50 AM
My Badges
Verified Answer

After everything possible was restarted, re-deployed and refreshed, the error is gone.

Thanks

Reply
UMESH PANDIT responded on 25 Sep 2013 4:06 AM
My Badges

try re-deployment and restart...

Reply
venkatesh vadlamani responded on 26 Sep 2013 2:11 PM
My Badges

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

Reply
Tommy Skaue responded on 19 Dec 2013 1:08 AM
My Badges
Suggested Answer

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.

Reply
venkatesh vadlamani responded on 19 Dec 2013 9:08 AM
My Badges
Suggested Answer

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.

Reply
Tippawan Kreangkraiwanich responded on 6 Jan 2014 11:47 PM

Hi Venkatesh,

I got this problem and follow your instruction by stop AOS process, and deleted all records in SysClientSession table. But the error still existed.

We already

- Restart AOS

- Delete records in table SysClientSession

- Restart SSRS service

- Compile and Full CIL generate

If you have other solution, kindly suggest.

Thanks,

Koong

Reply
venkatesh vadlamani responded on 7 Jan 2014 5:31 AM
My Badges

Hi Koong,

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.

C:\Users\venkatesh.vk\AppData\Local\Microsoft\Dynamics AX\VSAssemblies

Stop and start the service.

I din't need a CIL since i was sure that there were no changes made in the environment.

Reply
Tippawan Kreangkraiwanich responded on 7 Jan 2014 6:03 PM

Hi Venkatesh,

Thank you so much, its work now with your instructions. Super thanks for your help ^ ^.

Best regards,

Koong

Reply
Phileus responded on 3 Feb 2015 5:39 AM
Suggested Answer

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.

Reply
Angelika Wurz responded on 27 Aug 2015 4:48 AM
Suggested Answer

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.

Reply
Camilo Alfonso Virguez serrano responded on 25 May 2016 1:59 PM
My Badges
Suggested Answer

HI All  in our case  we restarted all AOS and SSRS  and it worked.

Reply
Didi Iswadi responded on 22 Jun 2016 3:12 AM

1. Clear all chace

2. AOT-->Service Groups-->Klik kanan BLService-->Deploy Service Group

Reply
Ghetz responded on 29 Mar 2017 6:03 AM
My Badges

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?

Reply
Ismael Utitiaj responded on 29 May 2017 2:50 PM
My Badges

Only Disable BIServices service and then enable again. It work for me.

Path. Adiministration - setup - AIF - Entry port

Reply
Rudi Hansen responded on 16 Jun 2017 4:48 AM
My Badges

Ismael Utitiaj

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.

Reply
Oleksandr Nazarov responded on 25 Sep 2013 3:50 AM
My Badges
Verified Answer

After everything possible was restarted, re-deployed and refreshed, the error is gone.

Thanks

Reply
Tommy Skaue responded on 19 Dec 2013 1:08 AM
My Badges
Suggested Answer

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.

Reply
venkatesh vadlamani responded on 19 Dec 2013 9:08 AM
My Badges
Suggested Answer

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.

Reply
Phileus responded on 3 Feb 2015 5:39 AM
Suggested Answer

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.

Reply
Angelika Wurz responded on 27 Aug 2015 4:48 AM
Suggested Answer

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.

Reply
Camilo Alfonso Virguez serrano responded on 25 May 2016 1:59 PM
My Badges
Suggested Answer

HI All  in our case  we restarted all AOS and SSRS  and it worked.

Reply
Vinai Varghese responded on 7 Aug 2017 3:58 AM
My Badges
Suggested Answer

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. :)

Reply
Martin Winkler responded on 30 Jan 2018 7:53 AM
My Badges
Suggested Answer
Muzzafar Jahangir responded on 2 May 2018 7:47 AM
My Badges
Suggested Answer

Thanks Ismael. It solved the problem for me also. any Idea why this issue is occurring.

Reply

SBX - Two Col Forum

SBX - Migrated JS