Share
Report
105It was brought to my attention that users were refrained from using certain standard reports in production control and I wanted to confirm with users in the forum if they have been seeing this in their installation. We are running AX2012 CU2
The reports are
1. Under transactions --> Production Overview
2. Under Balance --> Work in Process
The strange thing about this is when I ran for example these reports with more criteria in the optional parameters it works.
But when I ran them with empty optional parameters it crashed the AOS with the following event viewer errors. The users said that at one point these reports were working but now they don't which leads me to believe its got to do with the accumalation of a larger dataset being returned and the AOS is not able to handle it.
Application: Ax32Serv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF931A55C (000007FEF8F00000) with exit code 80131506.
Faulting application name: Ax32Serv.exe, version: 6.0.1108.2423, time stamp: 0x50b725fa
Faulting module name: clr.dll, version: 4.0.30319.18444, time stamp: 0x52717f9a
Exception code: 0xc0000005
Fault offset: 0x000000000041a55c
Faulting process id: 0xc88
Faulting application start time: 0x01cf9740e2e117b1
Faulting application path: D:\Program Files\Microsoft Dynamics AX\60\Server\AX2012_DEV1\Bin\Ax32Serv.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 68d4f5bb-0338-11e4-a50a-005056ab0007
I then whet over to the SQLReporting log to dig deeper and here is what it reported from that side. Believe me this is frustrating one has to go through to identify that this issue might be due to the fact that the amount of data returned might be causing the AOS to crash.
library!ReportServer_0-34!8a0!07/02/2014-10:26:25:: i INFO: RenderForNewSession('/DynamicsAX/ProdOverview.Report')
library!WindowsService_35!1134!07/02/2014-10:34:36:: i INFO: Call to CleanBatch()
library!WindowsService_35!1134!07/02/2014-10:34:37:: i INFO: Cleaned 0 batch records, 0 policies, 1 sessions, 0 cache entries, 1 snapshots, 5 chunks, 0 running jobs, 0 persisted streams, 10 segments, 10 segment mappings, 0 edit sessions.
library!WindowsService_35!1134!07/02/2014-10:34:37:: i INFO: Call to CleanBatch() ends
processing!ReportServer_0-34!8a0!07/02/2014-10:36:27:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'ProdOverviewDS'. ---> System.TimeoutException: Timeout error occurred will calling AOS service. Use Dynamics AX client configuration utility to change WCF configuration values. Exception details: The request channel timed out while waiting for a reply after 00:09:59.9844002. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> Microsoft.Dynamics.AX.Framework.Services.Client.QueryServiceException: The request channel timed out while waiting for a reply after 00:09:59.9844002. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The request channel timed out while waiting for a reply after 00:09:59.9844002. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The socket transfer timed out after 00:10:00. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.IO.IOException: The read operation failed, see inner exception. ---> System.TimeoutException: The socket transfer timed out after 00:10:00. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.Sockets.SocketException: 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
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.ServiceModel.Channels.SocketConnection.ReadCore(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, Boolean closing)
--- End of inner exception stack trace ---
at System.ServiceModel.Channels.SocketConnection.ReadCore(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, Boolean closing)
at System.ServiceModel.Channels.SocketConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.DelegatingConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionStream.Read(Byte[] buffer, Int32 offset, Int32 count, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security.NegotiateStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.NegotiateStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.NegotiateStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
--- End of inner exception stack trace ---
Please advise in the next steps. Again the reports work when you put in parameters that returns a smaller result set.
Best.
Tony
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
