Some learnings with Linx on a Client's server and CommandLine

On a current project I had to spend a lot of time trying to get a solution working on a server with Linx, but these hints will help myself and hopefully others going forward to not get stuck:

  • When running an executable file that require specific rights, change the Linx Service startup user to a specific username and password under Services.exe. This will allow the Linx Server to act as if it was that user that was logged in.
  • When you need to install any of the Microsoft redistributes (like “vc_redist.x64.exe”) make sure you first disable the antivirus. Especially McAfee. Otherwise the install will fail.
  • If you run an executable in a temporary “bat” file that you generated, and the executable is on a different drive, first go to that drive (i.e. “D:”) before running the executable. Some programs (like Tessaract OCR) do not use drive letters in their references, and will fail.
  • If you add a “PAUSE” in a bat file during testing to debug any errors, remember to remove it. Otherwise your server will PAUSE and the process will never finish.
  • Increment the bat file name each time you create it, and use the output value of the File Write to make sure you execute the correct bat file.