AX 2012 SSRS REPORTS ERRORS AND SOLUTIONS

AX 2012 SSRS REPORTS ERRORS AND SOLUTIONS

If  you call a report from a job some times you will get this kind of error
Error1:Parameter executionInfo cannot be null or empty.
Solution:
Add  the following  line to your job you will get the out put
salesInvoiceController.parmReportContract().parmReportExecutionInfo(new SrsPrintMgmtExecutionInfo());

Error2:
A call to the Microsoft Dynamics AX SRSFrameworkService service failed. The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.
Solution:
Open  AOT and register the following services:
1)SRSFrameworkService
2)SSASFrameworkService

Error3:
“Your browser does not support scripts or has been configured not to allow scripts.”
Solution:
1) go to (from its menu) Tools/Internet Options
2) go to Security tab
3) select Trusted zone from the list of available zones
4) click Sites button
5) Add your Reports Manager URL in the trusted sites

Error4:
Report labels does not show up in report.
Solution:
I got this issue after upgrading my sql server from 2012 to 2014 in an existing environment
If you face this issue in ax reports first of all check your configuration files
Follow this link and modify the rsreportserver file as per the instructions and restart the AOS once check the issue.
https://technet.microsoft.com/EN-US/library/hh389762.aspx

After modifying the file if you face same problem please modify theweb configuration file also and then restart the AOS and check the issue.

Error5:
Exception of type ‘Microsoft.Dynamics.AX.Framework.Services.Metadata.Exceptions.MetadataItemException`1[Microsoft.Dynamics.AX.Framework.Services.Metadata.Contracts.QueryDataSourceMetadata]’ was thrown.
Solution:Restart the service Reporting Service.

Error6:
The ‘ParameterName’ parameter is missing a value.

Solution:
Set the following properties of a report parameter to true in visual studio.

1)Allow Blank  2)Nullable

1)Open Report manager URL in browser

2)Find the report in the reports folder.

3)Select the report and click on manage option of a report

4)go to the parameters section.

5)go to the specified parameter and select the Nullable check box to True.

These two properties are not reflecting on the Repor server.

Error7:

The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameterhttp://tempuri.org/:queryBuilderArgs. The InnerException message was ‘Element ‘http://tempuri.org/:queryBuilderArgs’ contains data from a type that maps to the name

Solution:

The solution is simple. You need to restart the AOS.

Error8:

http://schemas.datacontract.org/2004/07/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.

Solution:

The solution is simple. You need to restart the AOS.

Error9:

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 65.52.168.70:8201

Solution:

1)Run the command prompt as a administrator

2)Flush the DNS by using ipconfig /flushdns command.

First try the above  solution.

if it is not working  you need to restart all the services including reporting server also.

Stop all AOS’s

Stop Reporting Service

Start AOS

Start Reporting Service.

Error10:

Changes are not reflecting on ax 2012 SSRS Report.

Solution:

1)If you maintain more designs for a single report you will face this issue.

Better maintain less number of designs for a report.

2)Clear the cache from ax

3)Delete particular report completely from DynamicsAX  report folder .

4)Deploy the report from management shell and then check the report.

Incase of failure

1)If you maintain more designs for a single report you will face this issue.

Better maintain less number of designs for a report.

2)Clear the cache from ax

3)Delete particular report completely from DynamicsAX  report folder .

4)Deploy the report from AOT

Error11:
AX 2012 Pre-requisite checker sees both the OLD SQL and the upgraded SQL instance

Performing a Microsoft SQLServer Reporting Services existence check for prerequisite ‘Microsoft SQL Server Reporting Services’.
11.0.3000.0
MSSQLSERVER
*** ERROR ***
Provider load failure
Provider load failure
*** END ERROR ***
Check failed.
Resolution: Install a supported version of the Reporting Services component of Microsoft SQL Server.

Solution:

  1. Run command wbemtest (Run this tool as a administrator)
  2. Click “Connect “and connect to “ROOT\Microsoft\SqlServer\ReportServer”(type this path in the Namespace textbox)
  3. After connecting to the name space, click “Query” to query “SELECT * from __namespace”. There SHOULD be one data in the record window (while the server only have one RS instance).
  4. Double-click the record, in the new properties windows, get the path value such as “\\<server>\ROOT\Microsoft\SqlServer\ReportServer:__NAMESPACE.Name=”RS_MSSQLSERVER” ”
  5. Now, close all sub dialogs, and then re-connect to “ROOT\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER”. “RS_MSSQLSERVER” is the Namespace.Name in step4
  6. Query “SELECT * from __namespace” again.

7.Above query will show Entire list Avable and Orphan instances of reporting.

8.Select orphan instances  and click on delete button

9.Verify your installation of Axapta reporting service extension.

Error:

“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&#8217; contains data from a type that maps to the name ‘http://schemas.datacontract.org/2004/07/XppClasses:SRSQueryBuilderArgs&#8217;. 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”.

Reason:
This happens quite frequently when AOS serving the reporting server crashes, or someone restart the AOS server without ending client user sessions.

Solution:

To overcome this problem and to make things straight, kindly follow the below steps;

Manually end client’s session,  AX> System Admin > Users> Online user> End session.
Stop AOS.
Open SQL, Select the record from SysClientSessions, take the backup of the records just to be on a safe side.
Delete all the records from SysClientSessions table from the databse.
Restart SSRS services

Start AOS

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s