<?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>2025-03-20T21:53:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with the same testing on DataPRO v4.0.1188, 4.3.482</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-10-28T22:12:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with DataPRO v4.2.504
 
 
Logged in remotely into burrito-supreme. Changed Database name = xxx
 
 
 
Back in the config file changed the following 
 
      &lt;setting name="DBName" serializeAs="String"&gt;
         &lt;value&gt;xxx&lt;/value&gt;
       &lt;/setting&gt;
 
      &lt;setting name="UseNTLMAuthentication" serializeAs="String"&gt;
         &lt;value&gt;True&lt;/value&gt;
       &lt;/setting&gt;
 
      &lt;setting name="DBType" serializeAs="String"&gt;
         &lt;value&gt;0&lt;/value&gt;
       &lt;/setting&gt;
 
      &lt;setting name="LocalDbHost" serializeAs="String"&gt;
         &lt;value&gt;burrito-supreme&lt;/value&gt;
       &lt;/setting&gt;
 
 
 
Using a S6A and creating a simple test setup
 
Took event and downloaded
 
Data
 
 
No issue found</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-28T22:03:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-10-22T18:24:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-07T23:46:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>changes have been applied to 4.0@51392</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-09-27T18:01:54Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-09-25T18:21:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2024-09-24T22:13:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>re-opened to backport to DP 4.0</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-09-17T20:55:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-08-27T18:25:35Z</TimeStamp>
    <ReleaseNote>Addresses an issue when using a non standard database name</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-27T18:25:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-27T17:24:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-27T17:24:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.2/4.3@51250</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-08-19T21:10:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-08-19T21:05:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>during reading of logs for this issue I noticed that this sql statement:
 
SELECT TOP (1) [SensorCalibrationId] FROM [DataPro].[dbo].[SensorCalibrations] WHERE [SensorId]=@1 ORDER BY [CalibrationDate] DESC, [ModifyDate] DESC
 
 
 
had the name "[DataPRO]" hardcoded in, if you have a different database name this will throw an exception.  The easiest way I have to duplicate is to collect data with a different database name, then delete your sensors and download.  I also had to correct another issue in the download code. 
 
I'm not sure how the user is able to see the error as ordinarily it only makes this call if it doesn't already have the sensor calibration.  For testing you might not be able to duplicate the original issue, so I would make sure download tab works with a unique database name.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2024-08-19T21:05:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>