kyle_wolff asked a question.
ARL failed to upload: The system cannot find the file specified
We are seeing a similar error after recently upgrading a customer to 2022 R1.
2022-06-27 01:02:26,531 [ecognition.Recognition] [INFO ] Executing SQL file D:\ProgramData\Flexera Software\FlexNet Manager Platform\DataImport\Content\ARL\.temp-extract\ARLCreateTables120.sql2022-06-27 01:02:26,594 [ecognition.Recognition] [INFO ] Executing command: -S <SERVERNAME> -d FNMSCompliance -b -i "D:\ProgramData\Flexera Software\FlexNet Manager Platform\DataImport\Content\ARL\.temp-extract\ARLCreateTables120.sql" -E
2022-06-27 01:02:26,640 [Recognition.Program ] [FATAL] An unhandled exception occurred.
System.Exception: Error running command: sqlcmd.exe -S <SERVERNAME> -d FNMSCompliance -b -i "D:\ProgramData\Flexera Software\FlexNet Manager Platform\DataImport\Content\ARL\.temp-extract\ARLCreateTables120.sql" -E ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at ManageSoft.Recognition.Recognition.ExecuteCommand(String command, String commandParams, String[] argumentsForSanitization)
--- End of inner exception stack trace ---
at ManageSoft.Recognition.Recognition.ExecuteCommand(String command, String commandParams, String[] argumentsForSanitization)
at ManageSoft.Recognition.Recognition.ExecuteSQLFile(String filename)
at ManageSoft.Recognition.Program.ExecuteSQLFile(Recognition arl, String sqlDir, String sqlFile)
at ManageSoft.Recognition.Program.Main(String[] args)
We are able to download the RecognitionAfter82.cab, and when we view the contents of the .cab, we do see the ARLCreateTables120.sql file that the log is stating it cannot find.
@kyle_wolff - this is actually a different/unrelated error to what is being discussed in the thread you posted against, so I've taken the liberty of moving your post to a fresh thread.
The "The system cannot find the file specified" error here likely means that sqlcmd.exe cannot be found in the system path.
Check that appropriate SQL Server tools are installed on this server, and you can run sqlcmd.exe without specifying a full path in a cmd shell (or PowerShell) window.