<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-24T00:13:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-08T15:53:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Tested and Verified using Datapro versions....4.0.1171.50996,4.2.452.50996 and 4.3.206.50891..



Tested as follows.

Test 1:
1) Disconnect and turn off all computer network. No hardware needed.
2) Open data pro, In the Data Recorders -&gt; Discover hardware -&gt;  Either manual add the IP address or AutoDiscovery
3) click query selected


Result: Query Selected finishes and no das are shown in add/Update Das section , since the das is not connected.


Test 2:

1.Dissconnect all network  connection on PC
2. Navigate to Data Recorders tab with autodiscovery button enabled and click to Scan All .

Result: Modal Pop up shows up  indicating "Udp discovery currently unavailable"    which is expected ...

Test 3: 
Manually add Ip of Das to  hardware db. repeat steps to  Query  the selected das  just added..



Result:Query Selected finishes and no das are shown in add/Update Das section , since the das is not connected.


Test 4 :

1. Start with Network  Connected to PC .
2. Open datapro and run autodiscovery 
3. Disconnect All networks from Pc  .
4. Run autodiscovery again   verify datapro does not crash ..

Result:
 
after 1st autodiscovery&gt;  Datapro  shows discovered das as expected...
After 2nd autodiscovery &gt; Datapro  gives message " "Udp discovery currently unavailable"  
and user can continue after clicking OK.



 




</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-07-08T15:53:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-05-09T16:27:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-04-16T17:44:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>re-opened for testing</Comment>
    <StatusString>Reopened</StatusString>
    <TimeStamp>2024-04-16T17:44:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with dp versions 4.0.1125.50323,4.2.340.50324, and 4.3.36.50324.

1.Tested by  adding  a Ecm to the hw db then disconnecting all network interfaces and running scan all.

2.Tested selecting existing hw from the hw db and running scan selected .

In all cases datapro gives pop up message "UDP Discovery currently not available " and user is able to click ok and resume using datapro as expected.

 </Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-02-03T00:17:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-02-02T22:39:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-02-02T22:02:30Z</TimeStamp>
    <ReleaseNote>Corrects an issue with discovery when no networks are available</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.2/4.3@50274</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-01-18T00:19:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>from Jerry:
 
had to add an ECM with an IP Address to the database to reproduce the problem without the 4.0 patch, so this step should be added to the description of how to test, as well as to the SQA test.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-18T00:00:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-17T22:05:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-16T21:20:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-01-16T21:17:09Z</TimeStamp>
    <ReleaseNote>Corrects an issue with discovery where datapro could freeze or crash</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-01-16T21:17:00Z</TimeStamp>
    <ReleaseNote>Corrects an issue with discovery where datapro could freeze or crash.</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>with this patch I fixed a couple of things,
 
1) SetProgressValue, a double is passed in but the value can be Infinite or NaN, or greater than 100%, it handles all of these cases now.
 
2) there was a crash in getavailablenetworkinterfaces when there was no network interfaces available, it no longer crashes here
 
3) when there are no network interfaces available I flag that and warn both in run test or discover hardware
 
4) when there are no UDP network interfaces I include a separate warning for that, however in practice I could never duplicate having any network interfaces that weren't included as UDP interfaces (there's a bool param to getavailablenetworkinterfaces) - I tried just using npcap loop back, etc</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-16T19:18:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-16T18:45:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>there's a couple of variations of this;
 
1) all network devices disabled before starting datapro
 
2) all network devices disabled after running discovery once
 
3) using scan selected
 
4) using scan all
 
I was able to get different behavior by using different variations.
 
now only displays when there are no network interfaces available, it'll do this in discovery or in run test.
 
won't crash in either.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-16T16:51:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-16T16:22:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Tested with Datapro 4.2.322.50036 And datapro crashes when running scan all with auto discovery selected and all networks disconnected from pc .

If I choose to not use autodiscovery and enter an Ip address manually and query , it functions as expected (with a ping failure after a few seconds since there are no network devices ) 

But with autodiscovery  on datapro displays message "Datapro has expierienced an issue"




To reproduce:

1.Dissconnect all network  connection on PC
2. Navigate to Data Recorders tab with autodiscovery button enabled and click to Scan All .
3. Data pro Modal Message pops "Datapro has experienced an issue And will now shut down ". 
4. log file is attached ..
 
  




024-01-11 09:09:07.410 User Admin pressed Hardware_DataRecorders_HardwareDiscovery_Page_PingPingAllButton
 
2024-01-11 09:09:07.679 !!  An exception of type: System.OverflowException occurred Module: mscorlib.dll, Name: ToInt32Message: Value was either too large or too small for an Int32. StackTrace:    at System.Convert.ToInt32(Double value) StackTrace:    at DataPROWin7.Controls.HardwareDiscoveryControl.SetProgressValue(Double v)    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)
 
2024-01-11 09:09:07.683 DataPRO has experienced an issue.  The issue has been recorded.  DataPRO will now shutdown for safety.
 
2024-01-11 09:09:07.940 Starting ping process
 
2024-01-11 09:09:07.940 192.168.3.195,192.168.6.64,
 
2024-01-11 09:09:09.637 Ping function complete
 
2024-01-11 09:09:09.643 status:  192.168.3.195 UNKNOWN
 
2024-01-11 09:09:09.643 status:   UNKNOWN
 
2024-01-11 09:09:09.643 status:  192.168.6.64 UNKNOWN
 
2024-01-11 09:09:14.598 User Admin pressed OK
 
2024-01-11 09:09:14.605 ModalWindow: Are you sure you want to close DataPRO? Press Yes to close or No to continue. 
 
2024-01-11 09:09:14.620 DataPRO Closing ==========================
 
2024-01-11 09:09:14.620 DataPRO Closed ===========================
</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2024-01-11T17:17:04Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-11T15:52:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-02T22:09:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>The new method added in 49999, ValidNIC returned the wrong boolean value, so was renamed InvalidNIC.
Additionally, the check for
                if (ni.Description.Contains("Npcap")) { continue; }
was restored to it's original position so that it would be always checked, not just when supportMulticastOnly was true.

50000 is 4.2</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-21T23:53:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49999 is 4.2</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-12-21T23:36:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-21T20:08:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-20T23:40:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-19T22:00:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-19T21:20:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-19T21:02:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-19T16:25:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-07T00:44:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>reproduce step:
1) Disconnect and turn off all computer network. No hardware needed. 
2) Open data pro, In the Data Recorders -&gt; Discover hardware -&gt;  Either manual add the IP address or AutoDiscovery 
3) click query selected

expect:
   ping start and time out in 30 sec or whatever duration appropriate.

happened:
   version 4.2.220 , ping never stop and stuck at 0 %. I can navigate to other tab. And mouse would always show the circle indicate app busy. The ping show in progress when come back the Discover hardware screen.

   version 4.0.729 software exception posted in log. foreground still functional.

reproduce rate: 100%

Note: version 4.2.220 waited a minute then reconnect network. DataPro did not able to pass pinging.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-12-07T00:44:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>