Unpredictable Pauses during Report Processing (BC14)

Heinrich
Member Posts: 7
Hi one of our customer complains about delayed output of RDLC-reports printed on local or network printers. This happens at unpredictable times, but several times a day (per user). Often a customer of our customer is waiting to get the paper report (shipment or invoice). The time varies from some seconds up to 10 minutes.
In some cases we saw that another user starts processing a different customer and finishes the process and gets his printout in a few seconds (on the same printer) prior the one who already waits some minutes. The first started printout arrives minutes later...
First we enhanced the C/AL code of some reports to collect log information (which report was printed at what time, which trigger was executed and some report data information. We put this log-code on some OnPre and OnPost triggers. The logs showed that the delay occured always either between “OnPreReport” and the first “OnPreDataItem” or / and between the last “OnPostDataItem” and “OnPostReport”.
We were able to connect the debugger to some waiting processes. The debugger sits and waits for minutes - not showing anything. If it came to live its always the beginning of the first “OnPreDataItem”- or the “OnPostReport”-trigger.
Has anyone experienced such a behaviour and/or can give some advice how to further hunt the issue or resolve it?
The customer is on BC 14.0.44327
Thanks in advance
Heinrich
In some cases we saw that another user starts processing a different customer and finishes the process and gets his printout in a few seconds (on the same printer) prior the one who already waits some minutes. The first started printout arrives minutes later...
First we enhanced the C/AL code of some reports to collect log information (which report was printed at what time, which trigger was executed and some report data information. We put this log-code on some OnPre and OnPost triggers. The logs showed that the delay occured always either between “OnPreReport” and the first “OnPreDataItem” or / and between the last “OnPostDataItem” and “OnPostReport”.
We were able to connect the debugger to some waiting processes. The debugger sits and waits for minutes - not showing anything. If it came to live its always the beginning of the first “OnPreDataItem”- or the “OnPostReport”-trigger.
Has anyone experienced such a behaviour and/or can give some advice how to further hunt the issue or resolve it?
The customer is on BC 14.0.44327
Thanks in advance
Heinrich
0
Answers
-
We already asked microsoft:
Regarding the question What does the system between the mentioned triggers thy wrote:
Basically, when the AL code has completed the code that is running is "Platform code" inside the NST.
This platform code is doing lots of stuff we can't easily have visibility to. Much of it is interacting with the Operating System and this is where the problem likely lies.
Unfortunately they were unable to deliver more information how to get closer to the root cause.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions