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'........................................
Some times we get the above error while running reports in Axapta 2012. To resolve this issue we need to delete usage data in the AOSserver.
Solution :
Step 1 -> Connect to sql server and go to axapta database(MicrosoftDynamicsAx) and delete all records in dbo.SYSCLIENTSESSIONS table.
Step 2-> Close the AX 2012 client to clear any in-memory elements.
Step 3-> Stop the Microsoft Dynamics Server service on the Application Object Server (AOS) to clear any in-memory elements.
Step 4-> Delete the application element cache files (*.auc),(*.KTI) from the Local Application Data folder.
C:\Users\AOSAccount\AppData\Local (Delete the all the AUC and KTI files)
Step 5-> Delete VSAssemblies from the Local Application Data folder.
C:\Users\youruserid\AppData\Local\Microsoft\Dynamics AX\VSAssemblies
Step 6-> Start the service
Some times we get the above error while running reports in Axapta 2012. To resolve this issue we need to delete usage data in the AOSserver.
Solution :
Step 1 -> Connect to sql server and go to axapta database(MicrosoftDynamicsAx) and delete all records in dbo.SYSCLIENTSESSIONS table.
Step 2-> Close the AX 2012 client to clear any in-memory elements.
Step 3-> Stop the Microsoft Dynamics Server service on the Application Object Server (AOS) to clear any in-memory elements.
Step 4-> Delete the application element cache files (*.auc),(*.KTI) from the Local Application Data folder.
C:\Users\AOSAccount\AppData\Local (Delete the all the AUC and KTI files)
Step 5-> Delete VSAssemblies from the Local Application Data folder.
C:\Users\youruserid\AppData\Local\Microsoft\Dynamics AX\VSAssemblies
Step 6-> Start the service
Note : Make sure show hidden files,folders,and drivers option enabled
@Rahul Talasila
@Rahul Talasila
Great breakdown! These kinds of issues in Dynamics AX can be tricky to troubleshoot, especially when the error messages are tied to serialization or in-memory session data. Your step-by-step fix clearing AUC/KTI files and resetting the AOS definitely helps streamline the debugging process.On a related note, if anyone is exploring Windows feature flags or enabling hidden UI features, I highly recommend learning how to use vivetool. It's a powerful command-line utility that can unlock experimental Windows features for testing and development purposes.
ReplyDelete