Microsoft Dynamics AX (Archived)

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

(0) Share

Report

Posted on by Sasha Nazarov

901

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

*This post is locked for comments

I have the same question (1)

All responses (28)

Answers (1)

Verified answer

Sasha Nazarov 901 on at

Like (2)

Report

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

Thanks

Was this reply helpful? Yes No
Umesh Pandit 9,315 User Group Leader on at

Like (1)

Report

try re-deployment and restart...

Was this reply helpful? Yes No
venkatesh vadlamani 3,180 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Suggested answer

Tommy Skaue Moderator on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Suggested answer

venkatesh vadlamani 3,180 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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

Was this reply helpful? Yes No
venkatesh vadlamani 3,180 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Hi Venkatesh,

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

Best regards,

Koong

Was this reply helpful? Yes No
Suggested answer

Phileus 5 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (1)

Report

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.

Was this reply helpful? Yes No