Hi, I have an application with several workflows that work ok in my local computer (testing with few records), but when I deploy the workflows to a server and the workflow gets approximately 1,500,000 records that match the criteria the workflow service crashes with the following error:
----------------------------------------------------------------------
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: BestTime.Service.exe
P2: 1.0.5756.30725
P3: 561301eb
P4: DevExpress.Data.v15.1
P5: 15.1.5.15211
P6: 55ba692e
P7: 17a5
P8: d9
P9: 10IEODV4TCLSIDYTIJZW0DD4R5TBIMWB
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_BestTime.Service_5cf6d5ef294430fbafd52ea9bd8205fbd1683_f32672a2_4e2245e7
Analysis symbol:
Rechecking for solution: 0
Report Id: aa2287e5-6c48-11e5-80d6-00155dfd2d78
Report Status: 0
Hashed bucket:
----------------------------------------------------------------------
I've done some testing and this only happens when the workflow needs to deal with a lot of data, workflows that deal with less records don't have a problem. I've been looking for an alternative like XPCursor or something similar to ask the workflow to page the records that meet the criteria but I haven't found any.
Any suggestions?
Hello Pablo,
We need some additional time to research this scenario. We will get back to you once we have an answer. Please bear with us.
Hi Dmitry, I made some changes to the workflow to test:
- Changed the criteria to trigger the workflow, now it looks for a record in a new class created just to trigger the workflow.
- Moved all the criteria to look those million records within a process within a class and used XPCursor, then I go through a foreach recreating what the workflow is supposed to do.
With these changes the workflow works, obviously I have some draw backs as I need to recompile if the criteria is changed and don't have the detail on the execution for each record that was used in the workflow, but on the other hand, I got the process to work as a workflow.
I wanted to mention this because this makes me think it is definetely a memory issue.