<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Farshid Atashband</User>
    <Comment>It's fixed or not reproducible on
 
DP 4.0.1189
 Tested with customer database
 1. created a new test setup test1Setup
 

 2. Assigned one sensor to a hardware and run the test
 
 
3. The test run is finished with export all successfully no exception 
 
 
 
DP 4.3 Could not install , 4.3 is not used 
 
 
DP 4.4.250.52307
 
Tested same steps as 4.0 and it was successful 
 
 
 
 
Wrote BDD tests to test the patch and test all conditions in the changed code</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2025-05-16T22:11:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Lijuan Pi</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2025-05-15T16:31:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2025-05-15T00:12:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-05-08T15:56:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Lijuan Pi</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-05-06T05:22:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-03-20T21:57:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2025-03-20T17:27:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2025-01-21T21:58:58Z</TimeStamp>
    <ReleaseNote>Addresses a crash that could occur during Run test export step</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>relevant notes from jerry:
 
it seems using the customer db is going to be the route to reproduce as even using the customer db and creating a new setup doesn't duplicate the issue:
 
 
 
The patch works well.  It makes the whole problematic Multiple-ROI feature more bullet-proof, which is a good thing, because the bug fix went through several iterations.
 
Verified that it worked in the customer’s configuration.
 
 
 
Interestingly, using the customer’s database, adding a Test Setup with the setting unchecked, caused a database record to be entered in the TestSetupROIs table, but not one in the ROIPeriodChannels table.  This causes the bug to not occur, but all of the existing Test Setups in the database did not have a record in the TestSetupROIs table.  Maybe from a migration, or from doing Test Setup imports, or ???</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-21T19:54:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-21T18:37:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-21T18:37:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-21T18:36:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-21T18:36:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.2/4.3/4.4@51882</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2025-01-20T22:01:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2025-01-20T21:27:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Jerry,
 
 
 
I’ve submitted a patch into 4.0 MAINT for
 
 
 
43384: Index out of Range Crash in Run Test &gt; Export on 4.0.X - Manuscript
 
 
 
With this ZF complained of crashes in run test in the export data step
 
 
 
I tracked this down to a RegionsOfInterest[0] when there was an empty regions of interest collection.
 
 
 
I addressed this in the patch by checking not making this call if regionsofinterest is null or empty.
 
 
 
After I did this I found a second issue, they export CSV and this would failed too in run test with a similar no regions of interest for export.
 
 
 
I addressed this by looking at the validate function and not performing the validation when the regions control is not shown.  I’m not sure this check ever needs to be made for ROI exports, but this patch will address their issues.
 
 
 
The easiest way to duplicate the issue is to use their database, however their database has a different file name and the admin password has been changed as well.   Most critically they have turned off the ability to see roi’s in edit test setup info (System settings-&gt;Test settings -&gt; Features-&gt; Enable region of interest (ROI) download options
 
 
 
I think you can duplicate the issue by just turning off this setting with download and export selected in your test setup and a CSV selected for export format.
 
 
 
In their test they have both ISO and CSV selected to export.
 
 
 
I’ll attach their db to the original ticket.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-20T21:26:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>this is exactly the issue [there's no ROI's]
  
 the code in question is looking for an ROI;
  
 
  
 in the case of ZF they have disabled rois (through this setting) Common.SerializedSettings.ENABLE_REGION_OF_INTEREST
  
 we can patch this.</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2025-01-20T17:54:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-20T17:39:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-20T17:38:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-20T17:38:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-01-20T17:37:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2025-01-16T21:33:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment>ZF reports seeing frequent crashing at Export in Run Test on their Central DB facing 4.0.X builds for "a few months."
 
Ticket: DataPro error V4.0.1189 – DTS – Zendesk
 
 
 
 
 
John Genna
 
 •Today 11:53
 
 
 
To: 
 
John Genna, 
 
Gregory Wantin, 
 
Robert Seymour, 
 
Tyler Kohler
 
 
 
 
 
 
 
 
 
 
 
DataPRO has experienced an issue error. The issue has been recorded. DataPRO will now shutdown for safety.
 
I am currently using V 4.0.1189.
 
The error occurs after the test has been complete and the data has been reviewed. The problem occurs when trying to export the data after the test has been run and completed.
 
 
 
 
 
 
 
 
 
 
 
 
 
DataPRO
 
LOG
 
 
 
 
 
 
 
 
 
 
  
 
 
 
 
 
Chris Balogh
 
Internal
 •Today 12:06
 
 
 
 
 
 
 
2025-01-16 13:51:52.097 -&gt; Attribute - SetEventAttribute [00003289], SLS0078, local: 172.16.0.250:54860, Remote: 172.16.0.19:1016 Key: EventHasBeenDownloaded, DataType: UInt32, Length: 4, Overwrite: True Event number: 0, Key: EventHasBeenDownloaded, DataType: UInt32, Length: 4, Value: 1
 2025-01-16 13:51:52.110 &lt;- Attribute - SetEventAttribute [00003289]\[00003289] - (13.0194ms), SLS0078
 2025-01-16 13:51:52.110 SLS0078 has completed service DownloadService
 2025-01-16 13:51:52.110 DownloadService finished - total time (0m 10s 852ms)
 2025-01-16 13:51:52.110 DownloadService.Download: All units are now finished, calling ServiceAvailable
 2025-01-16 13:51:52.112 Setting OverallStatus to Cleaning up
 2025-01-16 13:51:52.251 DownloadService.Download: All units are now finished, calling ServiceAvailable
 2025-01-16 13:51:52.251 DownloadService.Download : calling service available
 2025-01-16 13:51:56.297 User Linear Building 4 navigated to: View all
 2025-01-16 13:52:59.901 This will undo any change(s) to this channel made before saving. Continue? User pressed Yes
 2025-01-16 13:53:29.326 MessageBox: Are you sure you want to skip the remaining graphs? Press OK to continue or cancel to remain on this step
 2025-01-16 13:53:29.331 ModalWindow: Are you sure you want to skip the remaining graphs? Press OK to continue or cancel to remain on this step
 2025-01-16 13:53:31.086 User Linear Building 4 pressed PageButton:MessageBoxButton_OK
 2025-01-16 13:53:31.086 User Linear Building 4 pressed: OK
 2025-01-16 13:53:31.148 User Linear Building 4 navigated to: Export all
 2025-01-16 13:53:31.373 !! An exception of type: System.ArgumentOutOfRangeException occurred Module: mscorlib.dll, Name: ThrowArgumentOutOfRangeExceptionMessage: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index StackTrace: at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource) StackTrace: at System.Collections.Generic.List`1.get_Item(Int32 index) at DataPROWin7.SubControls.Export.CalculateExportTestName(Int32 firstEventNumber, TestTemplate test, Boolean ROI, IRegionOfInterest roi) at DataPROWin7.SubControls.Export.Reset() at DataPROWin7.SubControls.Export.GetPageContent() at DataPROWin7.PageNavControl.SetCurrentStep(NavStep step, Boolean bCheckNextOK) at DataPROWin7.RunTestBase.GoNextStep() at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
 2025-01-16 13:53:31.376 DataPRO has experienced an issue. The issue has been recorded. DataPRO will now shutdown for safety.
 2025-01-16 13:56:08.766 User Linear Building 4 pressed OK
 2025-01-16 13:56:08.777 ModalWindow: Are you sure you want to close DataPRO? Press Yes to close or No to continue.
 2025-01-16 13:56:08.813 DataPRO Closing ==========================
 2025-01-16 13:56:08.816 DataPRO Closed ===========================
 2025-01-16 13:56:31.412 DataPRO Started ==========================
 
 
 
 
 
 
 
 
 
  
 
 
 
 
 
Chris Balogh
 
 •Today 12:10
 
 
 
To: 
 
John Genna, 
 
Gregory Wantin, 
 
Robert Seymour, 
 
Tyler Kohler
 
 
 
 
 
 
 
 
 
 
Hi John,
  
 Thank you for reaching out on the Help Center and thank you for the report.
  
 Is this an isolated incident, does this happen occasionally, or does this happen frequently?
  
 From the logs it looks like this only occurred in the Run Test Tab and not in the Export tab, is this correct?
  
 Talk to you soon,
 Chris
 
 
 
 
 
 
 
 
 
   
 
 
 
John Genna
 
 •Today 12:14
 
 
 
To: 
 
DTS, 
 
Gregory Wantin, 
 
Robert Seymour, 
 
Tyler Kohler
 
 
 
 
 
 
 
 
 
 
 
ZF-Lifetec Confidential
   
 
 
This has happened 3 times for me today. In speaking to a coworker, he has been having this same issue for a few months, but his version is an older version V 4.0.1123.
 
Based on that I would say that it is happening quite frequently.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
~WRD0000
 
JPG
 
 
 
 
 
 
 
 
 
 
   
 
 
 
John Genna
 
 •Today 12:21
 
 
 
To: 
 
John Genna, 
 
Gregory Wantin, 
 
Robert Seymour, 
 
Tyler Kohler
 
 
 
 
 
 
 
 
 
 
 
That is correct it was in the Run test from the test setup page.
 
 
 
 
 
 
 
 
 
 
 
 
  
 
 
 
 
 
Chris Balogh
 
 •1 minute ago
 
 
 
To: 
 
John Genna, 
 
Gregory Wantin, 
 
Robert Seymour, 
 
Tyler Kohler
 
 
 
 
 
 
 
 
 
 
Hi John,
  
 Thanks for the extra information.
  
 I'm checking with the software dev team to see if we've seen something like this yet and have a fix already. If not, I'll try to get you a timeline on when we could potentially have a fix or workaround for you and your colleagues.
  
 Talk to you soon,
 Chris</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2025-01-16T21:33:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>