Linx Help

Linx 64-bit compatibility

When you perform an installation of Linx, the "bitness" of your operating system will determine how the Linx processes (server and designer) are executed.  On a 32-bit operating system, Linx will run as a 32-bit process, while on a 64-bit operating system, it will run as a 64-bit process.  For most of the components in Linx, these different execution environments do not present any problems, but there are some components that do not work in a 64-bit environment. 

The following document contains a list of all the current Linx components and whether they will work in a 64-bit environment: Linx 64-bit compatibility testing

If you are making use of a component that is not supported in a 64-bit environment, but would still like to install Linx on a 64-bit operating system, you have the option of forcing Linx to run as a 32-bit process.  To do this, you can make use of the CorFlags conversion tool (for more information on obtaining this tool, click here).  When you apply these changes, the Linx process will run in the WoW64 subsystem of Windows and will behave like a 32-bit application.  To convert Linx, run the following 2 commands from the command line (path-specific information has been omitted):
  • CorFlags.exe LinxDevelopment.exe /32BIT+
  • CorFlags.exe LinxServerService.exe /32BIT+
Remember to restart the service after this change.  If you now inspect these processes in the task manager, you will see that they are running as 32-bit applications.  To download the full test solution and its accompanying files, click here.