Search

A Guide to Interpreting the System Information Batch File

Liz Sanderson
Liz Sanderson
  • Updated

Introduction

The system_information.bat file is a valuable tool for diagnosing potential issues within your system that could be causing errors when trying to run or license FME. By running the system_information.bat file, you are provided with a detailed HTML report (FMEReport.html) of the following:

This article outlines what to look for when reading the HTML report and where to find additional resources for common errors encountered when running the system_information.bat file.

System Information

When looking at the system information portion of the HTML report, please take note of the following:

  • Volume ID
  • OS name
  • OS version
  • System Model
  • System Type
  • Available physical memory

Common issues to watch for:

  • If your volume ID has changed, your Registration Key will change, which may prevent FME from starting successfully. This can occur for even small hardware changes. Please request a new license file if you notice that your registration key has changed.
  • If the Available Physical Memory is less than what FME requires, the program will fail to initialize. Please free some physical memory for FME to run.
  • If your System Type says that your computer is 32-bit, but you are attempting to run 64-bit FME, the program will fail to initialize. Please ensure that your version of FME is consistent with your operating system.

Running Processes

Important things to look for in the Running Processes section would be anything with FME in the name, safe.exe, or lmgrd.exe. Please note:

  • You will not see safe.exe or lmgrd.exe when running a fixed-license version of FME, or when running the batch file on the client-side machine using a floating license. For troubleshooting floating licenses, it is best to run the batch file on the floating license server.

Environment Variables

Take note of the following:

  • LM_LICENSE_FILE (shouldn’t exist)
  • SAFE_LICENSE_FILE (shouldn’t exist)
  • ARCGIS_LICENSE_FILE (may exist; ensure it is correct)
  • PATH

The LM_LICENSE_FILE and SAFE_LICENSE_FILE environment variables could be set by other applications or older versions of FME, which may interfere with the licensing process and connect to incorrect servers (if using a floating license). The correct settings should come from the files in <FME>/licenses. If you find these environment variables have been set, please remove them and restart the service (if using a floating license server).

SDE Libraries

This checks to see if SDE Libraries exist – If they exist, sde.dll, sg.dll, and pe.dll will be listed.

Oracle

Check to see if Oracle’s ORACLE_HOME or TNS_ADMIN is set and if tnsnames.ora and oci.dll files exist. It is permissible to install both 32- and 64-bit clients together; for FME purposes, you just have to make sure that ORACLE_HOME is *not* defined, and that the PATH includes both instant clients’ installation directories (in either order). If ORACLE_HOME OR TNS_ADMIN exist, they will be listed in this section.

Autodesk

Lists the contents of the Autodesk plugin directories.

Registry

Take Note of:

  • Anything with License in the name if you have an old FME.
  • "BUILD" will list what FME builds have been installed.
  • "Extensions" will list which FME build extended which extension.
  • Check the ArcGIS license information. Watch for port numbers. It is possible that if you use a floating license server, it is trying to use the same port as ArcGIS, which prevents FME from being licensed. Please visit this page for information on resolving this conflict.
  • If "Borrow" has entries after it, a license has been borrowed.

Machine Key (Registration Code)

This section shows you your Machine Key (Registration Code).

  • Ensure it matches what is listed in the license files below.
  • If you are using a fixed license and want to move it to a new machine, then install FME on the new machine and enter your serial number into the licensing assistant. Full details can be found in the FME Form Administrator's Guide
  • For Machine Key or Registry Key changes using a floating license, please request a new license file from our Floating License Request page.
  • There may be a different registration key listed under the Safe Software debugging section. If you are experiencing an issue with a fixed license, the support team will use it for debugging.

FME Installations

Lists all the FME.exe installations and their paths. If you do not see any FME.exe installations, then FME has not been successfully installed. Please perform the troubleshooting steps found in the Fixed License Troubleshooting page and the Floating License Troubleshooting page. If you are still experiencing difficulty with your installation, please contact our Support Team and include FMEReport.html and FlexNet Report.html (FlexNet Report.html is only necessary if using a floating license).

Non-existent path entries

This section should be blank.

Was this article helpful?

We're sorry to hear that.

Please tell us why.

As of January 14th, 2026, comments on knowledge base articles have been closed. To make sure questions don’t get missed and to enable more community support, we’ve moved discussions to the FME Community. If you have a question or a comment about this article, please create a new post or create a support ticket.