<?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-01-02T16:15:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with DataPRO v.4.0.999
 
Running as administrator (Command Prompt) I issued the following commands:
 
 
Opened DataPRO 4.0.999
 
and it opens correctly. Checking logs:
 2023-10-02 15:38:10.613 IsInHighPowerMode
 Profile name: balanced GUID: 381b4222-f694-41f0-9685-ff5bb260df2e
  
 2023-10-02 15:38:10.613 Active Power Schemes  Existing Power Schemes (* Active) ----------------------------------- Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e  (Balanced) * Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c  (High performance) Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a  (Power saver) 
  
 2023-10-02 15:38:10.613 ModalWindow: Warning, system appears to not be in high (or max) performance mode.  High performance mode is recommended.
  
 2023-10-02 15:38:28.394 User navigated to Login Page
  
 2023-10-02 15:38:28.409 Results of using stored procedure sp_DbVersionGet are version: 94 &amp; remarks: 
  
 2023-10-02 15:38:41.705 User  pressed MainWindow_HighPerformanceModeWarningOK
  
 2023-10-02 15:38:51.195 Logged in  Admin
  
 2023-10-02 15:38:52.247 User navigated to Home Page
  
 2023-10-02 15:38:52.442 User Admin navigated to: Info
  
 2023-10-02 15:38:52.554 User navigated to Home Page
  
 2023-10-02 15:38:54.813 User Admin pressed PageButton:MainWindow_ConfirmUnLicensed_OK
  
 2023-10-02 15:38:54.813 User Admin pressed MainWindow_ConfirmUnLicensed_OK
  
 2023-10-02 15:41:00.163 ModalWindow: Are you sure you want to close DataPRO? Press Yes to close or No to continue. 
  
 2023-10-02 15:41:01.424 User Admin pressed PageButton:MainWindow_ConfirmDataPROExit_YES
  
 2023-10-02 15:41:01.424 User Admin pressed MainWindow_ConfirmDataPROExit_YES
  
 2023-10-02 15:41:01.460 DataPRO Closing ==========================
  
 2023-10-02 15:41:01.462 DataPRO Closed ===========================
  
 2023-10-02 15:42:26.002 DataPRO Started ==========================
  
 2023-10-02 15:42:26.018 License file does not exist.
  
 2023-10-02 15:42:26.034 Load any arguments
  
 2023-10-02 15:42:26.377 DbType is 1
  
 2023-10-02 15:42:26.377 Environment.Program Files is C:\Program Files
  
 2023-10-02 15:42:26.377 envProgFilesNoDrive is Program Files
  
 2023-10-02 15:42:26.377 highestVersionInstalledPath before Replace is C:\Program Files\Microsoft SQL Server\120\LocalDB\Binn\
  
 2023-10-02 15:42:26.377 highestVersionInstalledPath after Replace is C:\Program Files\Microsoft SQL Server\120\LocalDB\Binn\
  
 2023-10-02 15:42:26.393 Environment.Program Files is C:\Program Files
  
 2023-10-02 15:42:26.393 envProgFilesNoDrive is Program Files
  
 2023-10-02 15:42:26.393 There is no ODBCToolsPath subkey in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\120\Tools\ClientSetup
  
 2023-10-02 15:42:26.393 pathValue before Replace is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:26.393 pathValue after Replace is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:26.393 Looking for C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\SQLCMD.EXE
  
 2023-10-02 15:42:26.393 ODBCToolsPath is 
  
 2023-10-02 15:42:26.393 Environment.Program Files is C:\Program Files
  
 2023-10-02 15:42:26.393 envProgFilesNoDrive is Program Files
  
 2023-10-02 15:42:26.393 There is no ODBCToolsPath subkey in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\120\Tools\ClientSetup
  
 2023-10-02 15:42:26.393 pathValue before Replace is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:26.393 pathValue after Replace is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:26.393 Looking for C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\SQLCMD.EXE
  
 2023-10-02 15:42:26.393 ODBCToolsPath is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:26.393 ODBCToolsPath is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:26.393 SqlDbPath is C:\Program Files\Microsoft SQL Server\120\Tools\Binn\; ODBCToolsPath is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:26.627 Result of Stop DataPROInstance command is: 
  
 2023-10-02 15:42:27.190 Result of Delete DataPROInstance command is: 
  
 2023-10-02 15:42:30.158 Result of Create DataPROInstance command is: LocalDB instance "DataPROInstance" created with version 12.0.2000.8.  
  
 2023-10-02 15:42:32.237 Result of Start DataPROInstance command is: LocalDB instance "DataPROInstance" started.  
  
 2023-10-02 15:42:32.237 ODBCToolsPath is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:33.518 Result of attach DataPro using db\DataPro.mdf and db\DataPro_log.ldf is:
  
 2023-10-02 15:42:33.518  C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;rem sqlcmd -E -S (localdb)\DataPROInstance -Q "ALTER DATABASE [DataPro] SET SINGLE_USER WITH ROLLBACK IMMEDIATE"   C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;rem sqlcmd -E -S (localdb)\DataPROInstance -Q "sp_Detach_db DataPro"   C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "CREATE DATABASE [DataPro] ON ( FILENAME = 'C:\DTS\DTS.Suite\4.0.999\DataPRO\db\DataPro.mdf'), ( FILENAME = 'C:\DTS\DTS.Suite\4.0.999\DataPRO\db\DataPro_log.ldf' ) FOR ATTACH"   C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "sp_configure 'clr enabled', 1"  Configuration option 'clr enabled' changed from 0 to 1. Run the RECONFIGURE statement to install.  C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "RECONFIGURE"  
  
 2023-10-02 15:42:33.518 ODBCToolsPath is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:34.737 Result of attach ISO using db\ISO.mdf and db\ISO_log.ldf is:
  
 2023-10-02 15:42:34.737  C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;rem sqlcmd -E -S (localdb)\DataPROInstance -Q "ALTER DATABASE [ISO] SET SINGLE_USER WITH ROLLBACK IMMEDIATE"   C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;rem sqlcmd -E -S (localdb)\DataPROInstance -Q "sp_Detach_db ISO"   C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "CREATE DATABASE [ISO] ON ( FILENAME = 'C:\DTS\DTS.Suite\4.0.999\DataPRO\db\ISO.mdf'), ( FILENAME = 'C:\DTS\DTS.Suite\4.0.999\DataPRO\db\ISO_log.ldf' ) FOR ATTACH"   C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "sp_configure 'clr enabled', 1"  Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.  C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "RECONFIGURE"  
  
 2023-10-02 15:42:35.221 Environment.Program Files is C:\Program Files
  
 2023-10-02 15:42:35.221 envProgFilesNoDrive is Program Files
  
 2023-10-02 15:42:35.237 There is no ODBCToolsPath subkey in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\120\Tools\ClientSetup
  
 2023-10-02 15:42:35.237 pathValue before Replace is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:35.237 pathValue after Replace is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:35.237 Looking for C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\SQLCMD.EXE
  
 2023-10-02 15:42:35.237 ODBCToolsPath is 
  
 2023-10-02 15:42:35.237 Environment.Program Files is C:\Program Files
  
 2023-10-02 15:42:35.237 envProgFilesNoDrive is Program Files
  
 2023-10-02 15:42:35.237 There is no ODBCToolsPath subkey in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\120\Tools\ClientSetup
  
 2023-10-02 15:42:35.237 pathValue before Replace is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:35.237 pathValue after Replace is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:35.237 Looking for C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\SQLCMD.EXE
  
 2023-10-02 15:42:35.237 ODBCToolsPath is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:35.237 ODBCToolsPath is C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\
  
 2023-10-02 15:42:36.377 Result of attach DASFactory using C:\DTS\DTS.Suite\4.0.999\DataPRO\db\DASFactory.mdf and C:\DTS\DTS.Suite\4.0.999\DataPRO\db\DASFactory_log.ldf is:
  
 2023-10-02 15:42:36.377  C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;rem sqlcmd -E -S (localdb)\DataPROInstance -Q "ALTER DATABASE [DASFactory] SET SINGLE_USER WITH ROLLBACK IMMEDIATE"   C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;rem sqlcmd -E -S (localdb)\DataPROInstance -Q "sp_Detach_db DASFactory"   C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "CREATE DATABASE [DASFactory] ON ( FILENAME = 'C:\DTS\DTS.Suite\4.0.999\DataPRO\db\DASFactory.mdf'), ( FILENAME = 'C:\DTS\DTS.Suite\4.0.999\DataPRO\db\DASFactory_log.ldf' ) FOR ATTACH"   C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "sp_configure 'clr enabled', 1"  Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.  C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "RECONFIGURE"  
  
 2023-10-02 15:42:36.440 Database versions: Native: 94/Actual: 94
  
 2023-10-02 15:42:43.596 Failure in InitializeUser: Value cannot be null. Parameter name: cipherText
  
 2023-10-02 15:42:43.799 ConnectedPrimaryDb: True
  
 2023-10-02 15:42:43.893 Results of using stored procedure sp_DbVersionGet are version: 94 &amp; remarks: 
  
 2023-10-02 15:42:44.158 IsInHighPowerMode
 Profile name: balanced GUID: 381b4222-f694-41f0-9685-ff5bb260df2e
  
 2023-10-02 15:42:44.158 Active Power Schemes  Existing Power Schemes (* Active) ----------------------------------- Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e  (Balanced) * Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c  (High performance) Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a  (Power saver) 
  
 2023-10-02 15:42:44.174 ModalWindow: Warning, system appears to not be in high (or max) performance mode.  High performance mode is recommended.
  
 2023-10-02 15:42:50.846 User navigated to Login Page
  
 2023-10-02 15:42:50.846 Results of using stored procedure sp_DbVersionGet are version: 94 &amp; remarks: 
  
 2023-10-02 15:42:54.158 User  pressed MainWindow_HighPerformanceModeWarningOK
  
 2023-10-02 15:43:01.311 Logged in  Admin
  
 2023-10-02 15:43:01.901 User navigated to Home Page
  
 2023-10-02 15:43:02.061 User Admin navigated to: Info
  
 2023-10-02 15:43:02.159 User navigated to Home Page
  
 2023-10-02 15:43:04.377 User Admin pressed PageButton:MainWindow_ConfirmUnLicensed_OK
  
 2023-10-02 15:43:04.378 User Admin pressed MainWindow_ConfirmUnLicensed_OK
 
 
 
Specifically:
 
C:\DTS\DTS.Suite\4.0.999\DataPRO&gt;"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\sqlcmd.exe" -E -S (localdb)\DataPROInstance -Q "CREATE DATABASE [DataPro] ON ( FILENAME = 'C:\DTS\DTS.Suite\4.0.999\DataPRO\db\DataPro.mdf'), ( FILENAME = 'C:\DTS\DTS.Suite\4.0.999\DataPRO\db\DataPro_log.ldf' ) FOR ATTACH"</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-10-02T23:04:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-21T21:46:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-08-01T18:16:23Z</TimeStamp>
    <ReleaseNote>Addresses an issue with installing in different languages</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-01T18:16:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Added logging to attempt to diagnose multiple "SQL Server LocalDb is not installed" message boxes during installation on foreign-language machines.
49251 is 4.0; 49252 is 4.1; 49253 is 4.2</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-25T21:51:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49211 is 4.1; 49212 is 4.2.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-19T17:48:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-18T22:56:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>To test:

Currently, 192.168.2.125 is set to French, and 4.0.999 is already installed, so it is a suitable platform for verifying that this version works.
In a command prompt window, issue the following commands:
C:\Program Files\Microsoft SQL Server\120\Tools\Binn\SqlLocalDb.exe Stop DataPROInstance.
C:\Program Files\Microsoft SQL Server\120\Tools\Binn\SqlLocalDb.exe Delete DataPROInstance.
Run DataPRO and ensure that it comes up successfully.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-07-18T19:58:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-18T18:33:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-18T18:30:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-18T17:51:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>My theory was incorrect.

The problem was that the result of the “Stop DataPROInstance” argument that we send to
C:\Program Files\Microsoft SQL Server\120\Tools\Binn\SqlLocalDB.exe
returns a string result, which we were comparing against English text, causing us to throw an Exception which stopped the rest of the connection process.
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-18T17:09:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-18T00:16:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-17T23:51:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-17T23:50:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-17T22:47:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>A workaround is to issue the following commands in the command prompt window before initiating DataPRO:

C:\&gt;"C:\Program Files\Microsoft SQL Server\120\Tools\Binn\SqlLocalDB.exe" Stop DataPROInstance


C:\&gt;"C:\Program Files\Microsoft SQL Server\120\Tools\Binn\SqlLocalDB.exe" Delete DataPROInstance

C:\&gt;"C:\Program Files\Microsoft SQL Server\120\Tools\Binn\SqlLocalDB.exe" Create DataPROInstance

49196, 49199, 49200, 49201, 49202, 49204, and 49205 are 4.0</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-17T19:36:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>My latest theory is that the "sqlcmd.exe" file is not in fullSqlcmdPath as we assume.  We should definitely do a FileExists check, and add logging, but also look in alternate locations if it's not found.

In other words, the path that we get from the Registry may be incorrect due to the file being removed, order of installations, etc.

The alternatives may be at
C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\xxx\Tools\Binn\sqlcmd.exe

I've asked Maugan to investigate the Registry on the non-working PCs.

Additinally, maybe other portions of the path, other than "Program Files" need to be localized...</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-13T23:10:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Code that works on German machine, doesn't on French machines.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-13T22:43:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>The following 4.0 revision numbers have been verified by Kate's German customer.
Verification from Maugan's French customer is pending.
49166, 49167, and 49169 are 4.0; 49174 is 4.1; 49175 is 4.2</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-12T20:29:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-07-05T20:56:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-05T20:54:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-05T20:48:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-05T20:47:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-07-05T15:09:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>https://dtsweb.zendesk.com/agent/tickets/12080

After the French Army a few days ago, I now have people from Alliantech telling me that DataPRO launches when they double click on the icon but then the launch window (blue window with software and db versions) disappears and nothing happens / DataPRO disappears from the task manager.
 
Attached is a DataPRO log file which indicates an error with SQL Server files/registry entry.
I tried:

    To reinstall the software and different 4.0 versions on this PC from Alliantech, but I got the same result. Only 3.3 and below work/open properly.
    To disable the antivirus, but that didn't help.
    To directly install SQL Server via the Prerequisite sub-folder, same result.

 
At some point, I noticed that the DataPRO installer was trying to copy a file to the C:\Users\User_name\Application Data folder, which doesn't exist (the folder is AppData, not Application Data). I tried to create one, but then the installer told me it couldn't copy the file to the Cookies sub-folder, which also doesn't exist in that User_name folder... A bit strange!
 
Since the issue has been seen by the French Army who tried to install 4.0.729 from the DTS USB stick they received with their several brand new SLICE6 AIR units, this is quite urgent...
 
Could you please have a look and let me know why the software behaves like this? I believe it's limited to PCs set up in French language/area as my laptops (US/English) are opening DataPRO 4.0 without any issue.
 
Let me know if you need anything else, I can have remote access to the Alliantech PC.
 
Thanks!
Maugan</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-07-05T15:09:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>