Introduction
When working with FME, encountering unexpected behaviors or limitations can be frustrating. To help navigate these challenges, this article provides a comprehensive list of known issues affecting all retired versions of FME. For a list of issues in supported versions of FME, see Known Issues in FME.
Each issue includes details on its impact, available workarounds, and whether a fix has been implemented. Our goal is to ensure transparency and provide solutions wherever possible, so you can keep your workflows running smoothly.
This article will not be maintained as these issues are no longer in supported versions of FME.
Known Issues in FME 2022.x and Older
For a list of issues for current versions of FME, see Known Issues in FME.
| Feature | Product | Description | Workaround | Affects | Status |
|---|---|---|---|---|---|
| Tokens | FME Server | Token web service doesn't obtain a new token after expiry on FME Server FMESERVER-19419 |
This only impacts token web services that need to pass the Authorization in the HTTP Header. Use an HTTP Caller in a workspace to obtain the token through a REST API call |
2022.x 2021.x 2020.x |
Resolved 2023.0 |
| Queues | FME Server | If you create a Queue Name that contains a special character (such as ^) engines will not be able to assign themselves to this queue. FMESERVER-17992 |
Create a Queue Name that contains spaces and alphanumeric characters only. Note: Underscore characters can be used as long as it is not the first character. |
2022.x 2021.x |
Resolved 2023.0 |
| Topic Monitoring | FME Server | When stopping the topic monitoring there is a pop-up error message "There was an error connecting to monitoring service". FMESERVER-16202 |
The socket is being intentionally closed, but IE is reporting an error on closure. Despite the error shown everything still works as expected. Optionally ignore this error in IE or proceed using a different web browser such as Chrome, Firefox, Edge or Safari. |
2022.x 2021.x |
Workaround Other |
| FME Server Apps | FME Server | FME Server App won't save when an optional parameter does not have a default value (unhandled exception error) FMESERVER-18230 FMESERVER-19041 |
FME Server may let you save the parameter once or twice before the error occurs. Try recreating the parameter or providing a default value. |
2022.x 2021.2.6 2021.2.5 2021.2.4 2021.2.3 |
Resolved 2023.0 |
| FME Server Installation | FME Server | In a Fault-Tolerant installation when the Core with the 'Active Job Router' fails, the remaining engines do not connect with the second Core Job Router. They will appear available in the Web UI but will not detect jobs in the queue for processing. This issue resolves itself after two hours. FMESERVER-19159 |
In fmeEngineConfig.txt set the RECEIVE_TIMEOUT directive to 90000. Save the file and restart FME Server to apply the change. Setting this directive forces the Engine to terminate itself after it does not receive a translation request for the specified time, effectively breaking out of the hung state. |
2022.x 2021.2.5 |
Resolved 2023.0 |
| FME Workbench | FME Desktop | FME Workbench won’t start on MacOS FMEDESKTOP-10892 |
See Known Issue: FME Workbench Won’t Start on MacOS |
2022.x 2021.2 |
Resolved 2023.0 |
| Microsoft SQL Sever Non-Spatial Writer | FME Desktop | Microsoft SQL Server Non-Spatial (MSSQL_ADO): writing to an existing table with an attribute with type varbinary(max) or nvarchar(max) will result in the following warning: Microsoft SQL Server Non-Spatial Writer: Attribute `geometry_wkb' of feature type `dbo.osf_pois_polygon_NS' has specified type `nvarchar(max)', but existing database table field has type `nvarchar_max'. Information may be lost during conversion OR Microsoft SQL Server Non-Spatial Writer: Attribute `geometry_wkb' of feature type `dbo.osf_pois_polygon_NS' has specified type `varbinary(max)', but existing database table field has type `varbinary_max'. Information may be lost during conversion FMEENGINE-73455 |
Under the Writer parameters > Advanced > Set Bulk Inserts to "No" Use the Microsoft SQL Server Non-Spatial (JDBC) format |
2022.x |
Resolved 2023.0 |
| FME Server Apps | FME Server | When configuring an FME Server App, the Show In App checkbox is missing for all parameters that are within a group box. FMESERVER-18341 |
Move the File parameters outside of the group box. | 2022.x |
Resolved 2023.0 |
| User Parameters | FME Server | When a reader has a source dataset published parameter that’s within a group box, the job will fail with an error such as “No CSV2 dataset name was specified (couldn't find a value for `CSV2_1_DATASET' or `CSV2_DATASET')”. This appears to occur regardless of the format. FMESERVER-18342 |
Move the File parameters outside of the group box. | 2022.x |
Resolved 2023.0 |
| Schedules | FME Server | When creating a schedule, if a file parameter exists that has (1) “Items to Select” set to Geodatabase and (2) “Path Selection” set to Multiple Paths, the schedule will fail to be created and an error will be returned saying something like: “Unexpected value “[“\\\\mynetdir\\folder\\hello_world.gdb”]” for parameter “value,” expected scalar.” Automations and Server Apps are not affected. | Set the geodatabase source dataset parameter from Multiple Paths to Single Path in the Path Selection. Once this change is made in FME Desktop (Desktop), publish the workspace and test creating a schedule. | 2022.x |
Resolved 2023.0 |
| User Parameters | FME Server | When running a workspace with a geometry parameter within a parameter group, the job fails with a JSON syntax error: Unexpected character: 't'. One of the following characters was expected: '"', '}' | Move the geometry parameter outside of the parameter group. | 2022.x |
Resolved 2023.0 |
| Schedules | FME Server | Schedules repository selection and search is limited to first 100 repositories when creating or editing a schedule FMEFLOW-18574 |
Create schedules through REST API calls | 2022.x |
Resolved 2023.0 |
| Users and Roles | FME Server | When trying to delete a user on a filtered list or very large list (where the list is spread out to multiple pages), the pop-up for selecting a user for transferring ownership of items is either empty or the complete list of users is not displaying. FMESERVER-19914 |
Use FME Server REST API call to remove the account from the FME Server instance. | 2022.2.x |
Resolved 2023.0 |
| Users and Roles | FME Server | Deleting the “fmeauthor” role causes FME Server login page to load with no username or password prompt. Loading the login page returns the response “Specified SAML configuration does not exist” . When deleting the default fmeauthor role i.e. deleting the corresponding entry from fme_role table, it causes the child record in fme_samlconfig to be deleted as well, effectively removing the only entry in the table. “fmeauthor” role is the default role assigned to the pre-existing SAML record. FMEFLOW-19917 |
If upgrade is not possible, manually insert a new record in the “fme_samlconfig table” with values from another healthy FME server’s database [would be the same values]. Also, replace the deleted role “fmeauthor”. | 2022.2.x |
Resolved 2023.0 |
| Automations | FME Server | Internal Server Error when looking at a job log that was run from an Automations, Automation Apps or a Streams that has been deleted. These endpoints are having issues: GET /fmeapiv4/jobs/<id> GET /fmeapiv4/jobs<id>/log FMESERVER-19869 |
You can access the job log via the FME Server System Share (File System) or download via the Web UI Files & Connections > Resources > Logs > engine > current|old > jobs |
2022.2.6 2022.2.5 2022.2.4 2022.2.3 |
Resolved 2023.0 |
| Oracle Database Connection | FME Server | When connecting to an Oracle database with a connection that includes the string "G@" in the name, and using a tnsnames.ora file, FME Server tries to connect using the connection name instead of the server name from the tnsnames.ora file. | Do not use "G@" in the database connection name. |
2022.2.6 2022.2.5 2022.2.4 |
Resolved 2023.0 |
| Automations | FME Server | Automation Keys no longer work when placed inside square or curly brackets. See the community post for more details. FMESERVER-19612 |
Remove brackets, do not place Automation Keys in brackets. |
2022.2.2 2022.2.1 2022.2.0 2022.1 2022.0 |
Resolved 2022.2.3 |
| ArcGIS Online Web Connections | FME Server | ArcGIS Online Web Connections created from new ArcGIS Online Web Services do not work on FME Server. When trying to add the URI to the web service after publishing to FME Server, an error "Some of all of the input parameters are invalid" is displayed on the UI. This is due to URLs needed for oauth 2.0 that are missing on FME Server. FMEDESKTOP-13465 |
Upgrade to FME Server 2022.2.1 Upload AGOL webservice from FME Workbench 2020. |
2022.2.0 2022.1 2022.0 2021.2.6 |
Resolved 2022.2.1 |
| Automations FME Server Apps |
FME Server | When trying to set values for parameters within a parameter group box, the new values are not saved. This occurs in Automations and FME Server Apps. FMESERVER-19203 |
Set default parameter values in FME Workbench and publish to FME Server |
2022.2 2022.1.3 2022.1.2 2022.1.1 |
Resolved 2023.0 |
| Python | FME Desktop | If the workspace's Python Compatibility parameter is set to 'Esri ArcGIS Python 3.9', NTLM authentication for Python-based formats (eg. Microsoft SharePoint List, Esri ArcGIS Server Feature Service, Esri ArcGIS Portal Feature Service, OData) fails with the message: Python Exception <ValueError>: unsupported hash type md4 FMEENGINE-76915 |
Change the workspace's Python Compatibility parameter to any of the FME Python options. |
2022.2 2022.1 |
Resolved 2023.0 |
| User Parameters | FME Server | What a choice parameter allows multiple selections, the values are not read as expected on FME Server. For example, [choice1, choice2] instead of choice1,choice2. FMEFLOW-19526 |
Move the parameter out of any parameter groups. |
2022.2 2022.1 |
Resolved 2023.0 |
| JSONValidator Transformer | FME Desktop | JSONValidator is rejecting \n FMEENGINE-74950 |
Update the JSON to \\n |
2022.1.3 2022.1.2 |
Resolved 2022.2 |
| User Parameters | FME Desktop | If a workspace was built in an older version of FME and opened in 2022.1, the initial bounds for map display values can be swapped in the Geometry Parameter. FMEDESKTOP-13160 |
Compare the values in the older version and 2022 to ensure they match. |
2022.1.2 2022.1.1 |
Resolved 2022.1.3 |
| Microsoft Excel Writer | FME Desktop | Excel Writer performance is much slower in 2022.1 compared to previous versions of FME FMEENGINE-74327 |
No known workaround. |
2022.1.1 2022.1.0 |
Resolved 2022.1.2 |
| FME Workbench | FME Desktop | Error dialog pops-up on workbench startup that says "VCRUNTIME140D.dll is missing on your computer". The issue only occurs on Windows Server 2012. FMEENGINE-74482 |
No known workaround | 2022.1.1 |
Resolved 2022.1.2 |
| User Parameters | FME Server | Geometry Parameter: 2022.1 is not backwards compatible with older versions FMESERVER-18903 |
Open the workspace in FME Desktop 2022.1 and publish it to FME Server. | 2022.1.1 |
Resolved 2022.1.2 |
| RCaller Transformer | FME Desktop | When using R 4.2 with FME the following error will occur. ERROR |RCaller (InlineQueryFactory): Failed with exit code 1 when executing R script. Output was: Loading required package: gsubfn Loading required package: proto Loading required package: RSQLite Error in if (fmeOutput != "") dbWriteTable(dbcon, "Output", fmeOutput, : the condition has length > 1 Execution halted 2022-05-20 23:28:11| 0.3| 0.0|ERROR |RCaller (InlineQueryFactory): Failed to execute scripted code. FMEENGINE-73477 |
Downgrade to R 4.1.3 or lower |
2022.1 2022.0 2021.x |
Resolved 2022.2 |
| Directory Watch | FME Server | The Directory Watch trigger will pass an incorrect path when monitoring a network resource with a missing backslash "\" at the end of the UNC path. FMESERVER-17246 |
See Known Issue: Directory Watch truncates network resource paths |
2022.1 2022.0 2021.x 2020.x 2019.x |
Resolved 2022.2 |
| FME Server Apps | FME Server | FME Server app doesn't allow uploading or browsing for a geodatabase resource folder when the file/URL parameter is configured as Geodatabase (only a textbox is shown) FMESERVER-18901 |
In FME Workbench, leave the file/URL parameter's "Items to Select" value as the default Files. Upload the geodatabase as a .zip file. |
2022.1 2022.0 2021.x |
Resolved 2022.2 |
| Schedules | FME Server | If FME Server is hosted in a different time zone, when creating a Basic or CRON Schedule the start and end times are adjusted. For example, if my current Server time: Fri-02-Sep-2022 11:30:00 AM -0700 and I set my schedule to start at 2022-09-02 20:00. After saving the Schedule it becomes 2022-09-02 13:00. Note: In 2022.1+ this is only an issue for a Schedule created in an Automation, but in 2021.2.6 it occurs on the individual Schedules page as well. FMESERVER-18922 |
Build a Schedule using the 'Repeat on Interval' Schedule Type. |
2022.1 2022.0 2021.2.6 |
Resolved 2022.2 |
| Web Connections | FME Server | Web Connections created from Web Services do not work on FME Server. When trying to add the URI to the web service after publishing to FME Server, an error is displayed on the UI. FMESERVER-19652 |
See Known Issue: Web Services on FME Server are Invalid |
2022.1 2022.0 2021.2.6 |
Resolved 2022.2 |
| FMEServerNotifier Transformer | FME Desktop FME Server |
With the FMEServerNotifier, if you include \n in the JSON, the JSON will be Null on FME Server. This has been fixed by FMEENGINE-74950. Please upgrade to FME Server 2022.2 and create the workspace in 2022.2. FMESERVER-19220 |
Replace \n with <br> in a workspace before triggering the topic or use an HTTPCaller to push data to the topic. See /notifications/topics/< topic >/message in the API documentation. |
2022.1 2022.0 2021.2 2021.1.3 |
Resolved 2022.2 |
| FME Server Apps | FME Server | FME Server Apps do not show Azure AD groups. FMESERVER-18367 |
Add each user individually. |
2022.1 2022.0 2021.2 |
Resolved 2022.2 |
| Python | FME Desktop | Running Python in FME 2022.0 on Windows 10 and Windows Server 2019 version 1909 or older may cause a crash. FMEENGINE-71266 |
See Known Issue: Instability Running Python in FME 2022.0 on Windows 10 and Windows Server 2019 Version 1909 or Older |
2022.1 2022.0 |
Resolved 2022.2 |
| Oracle Reader | FME Desktop | Oracle 11g Database Incompatibility (Oracle Spatial Formats) Reader Message : (there may be some success reading if not using a spatial query): WARN |Execution of statement `SELECT table_name, column_name, d.dcount, SRID FROM USER_SDO_GEOM_METADATA OUTER APPLY(SELECT COUNT(*) AS dcount FROM TABLE(diminfo)) d' did not succeed; error was `ORA-00933: SQL command not properly ended'. OR if using Spatial Query may also see ORA-29902: error in executing ODCIIndexStart() routine ORA-13208: internal error while evaluating [window SRID does not match layer SRID] operator Writer Message WARN |Execution of statement `SELECT table_name, column_name, d.dcount, SRID FROM USER_SDO_GEOM_METADATA OUTER APPLY(SELECT COUNT(*) AS dcount FROM TABLE(diminfo)) d' did not succeed; error was `ORA-00933: SQL command not properly ended'. ERROR |Execution of statement `INSERT INTO "<table>" ( "<col1>", "<col2>", "<col3>", "<col4>", "GEOMETRY" ) VALUES ( :"<col1>", :"<col2>", :"<col3>", :"<col4>", :"GEOMETRY")' did not succeed; error was `ORA-29875: failed in the execution of the ODCIINDEXINSERT routine ORA-13365: layer SRID does not match geometry SRID ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 720 ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 225'. FMEENGINE-75065 |
No Known workaround. |
2022.1 2022.0 |
Resolved 2022.2 |
| User Parameters | FME Server | When an input File parameter is within a group box, files can't be uploaded. FMESERVER-18340 |
Move the File parameters outside of the group box. |
2022.1 2022.0 |
Resolved 2022.2 |
| French FME Server | FME Server | FME Server French System Locale failing to start on Windows Server after fresh install. DEVOPS-2470 |
See Known Issue: FME Server 2022.0 French System Locale failing to start on Windows Server |
2022.1 2022.0 |
Resolved 2022.2 |
| Backup and Restore | FME Server | Web connections are not present after the restore process during the upgrade. FMESERVER-19601 |
See FME Server Upgrade Can Fail to Restore Web Connections if Web Service Are Broken |
2022.1 2022.0 |
Resolved 2022.2 |
| User Parameters | FME Server | When running a workspace with an updated text file parameter that was uploaded as a temporary file, the job will not use the updated file. The old file is used and a org.apache.commons.io.FileExistsException is logged in the Catalina log. | Use a different type of file (for example, csv) or rename the text file prior to uploading it |
2022.1 2022.0 |
Resolved 2022.2 |
| Microsoft Excel Reader/Writer | FME Desktop | FME Workbench will crash while trying to access the parameter window in the Excel Reader/Writer after reading or importing from a XLSM dataset. FMEENGINE-75304 |
Add Readers/Writers to the canvas without opening the parameters. | 2022.1 |
Resolved 2022.2 |
| FME Server Web UI | FME Server | When logging into FME Server, the request does not correctly validate the referrer value, which may result in an unwanted redirection. FMESERVER-18288 |
See Known Issue: FME Server missing validation which may result in an unwanted redirect upon login |
2022.0.1.0 2022.0 2021.x |
Resolved 2022.0.1.1 2021.2.6 |
| Security | FME Server | A security scan has reported vulnerabilities on FME Server with two stored Cross-Site Scripting (XSS). See article for CVEs. FMESERVER-14600 FMESERVER-18292 |
See Known Issue: FME Server Unauthenticated and Authenticated Stored Cross-Site Scripting (XSS) Vulnerabilities |
2022.0.1.0 2022.0 2021.x 2020.x 2019.x |
Resolved 2022.0.1.1 2021.2.6 |
| Repositories | FME Server | A user who has been granted access permissions on Repositories as well as Read and Publish permissions on any Repository is able to carry out an XML external entity (XXE) injection attack. FMESERVER-18289 |
See Known Issue: FME Server XXE vulnerability via adding a repository item |
2022.0.1.0 2022.0 2021.x 2020.x 2019.x |
Resolved 2022.0.2 2021.2.6 |
| Automations | FME Server | When running a workspace in an Automation that writes a file to a resource folder, if the resource path contains spaces, the file will fail to write since the path gets cut off. The job will succeed but the file will be written to the wrong location. FMESERVER-18366 |
Add one set of double quotes around the path per space. For example, ""$(FME_SHAREDRESOURCE_DATA)/My Output Data/"". Alternatively, write to a resource path that doesn’t have spaces. |
2022.0.0.x 2022.0 |
Resolved 2022.0.1 |
| User Parameters | FME Desktop FME Server |
Workspaces that use a File Published Parameter may fail when published to FME Server if the file parameter was created within the transformer and it is referencing an FME Server parameter. The error in the log will say something like “File cannot be found”. FMESERVER-18414 |
See Known Issue: FME Server Job Failure when Published Parameters reference FME Server Parameters |
2022.0.0.x 2022.0 |
Resolved 2022.0.1.1 |
| File Upload | FME Server | FME Server is failing to use files uploaded by the temporary upload if they have a space in the file name. FMESERVER-18434 |
Either remove the space in the file name or switch the File Parameter to use Multiple Paths in FME Desktop and reupload the workspace on FME Server. This setting is found in the Parameter Configuration under File/ URL configuration > File Configuration > Path Selection. |
2022.0.0.x 2022.0 |
Resolved 2022.0.1.1 |
| SAML | FME Server | In the FME Server Web UI when SAML Configuration is enable the URLs listed under the SAML Identity Provider Settings are incorrect. FMESERVER-18418 |
Remove /fmeserver from the URLs when copying them over to your SAML provider. |
2022.0.0.x 2022.0 |
Resolved 2022.0.1.1 |
| ArcGIS Online | FME Server Hosted | ArcGIS Online Workspaces running on FME Cloud will fail with the error "simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)" FMEENGINE-73399 |
No known workaround. |
2022.0.0.1 2022.0.0.0 |
Resolved 2022.0.0.2 |
| Automations | FME Server | Building an Automation with an internal action (orange node) if I try and reference an event key from an upstream trigger/action the Automation cannot be saved. FMESERVER-18328 |
See Known Issue: Unable to save an Automation when referencing output keys in downstream action | 2022.0.0.1 |
Resolved 2022.0.0.2 |
| Automations | FME Server | When creating an Automation, with a workspace that contains a password parameter. Once you save it, an error pops up that says "javax.crypto.IllegalBlockSizeException" FMESERVER-18267 |
If you create the automation again and reenter the password in the workspace parameter it will save. | 2022.0.0.0 |
Resolved 2022.0.0.1 |
| ArcGIS Online | FME Desktop | ArcGIS Online Workspaces running on a Ubuntu machine will fail with the error "simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)" FMEENGINE-73399 |
No known workaround. | 2022.0.0.0 |
Resolved 2022.0.0.1 |
| FME Desktop | FME Desktop | Non-ASCII path handling causes FME Desktop applications to crash on startup. Possible paths that could have non-ASCII characters that could cause a crash are: User App Data folder FME Resource folders FME temporary folder Windows font folder FMEENGINE-73388 |
Remove non-ASCII characters from paths or upgrade to FME 2022.0 build 22343 or newer | 2022.0.0.0 |
Resolved 2022.0.0.1 |
| RealDWG | FME Desktop | The loaded plugin's FMEPluginCapabilities 'realdwg/REALDWG' has changed the process locale to 'English_Canada.1252' which is incompatible with FME 'English_Canada.utf8' locale. FMEENGINE-73329 |
No known workaround. | 2022.0.0 |
Resolved 2022.0.1 |
| FME Server Web Connection | FME Server | An FME Server transformer is failing with the error "Reason - credentials for user '<username>' are invalid". FMESERVER-18350 |
See Known Issue: FME Server Web Connection fails with Reason - credentials for user are invalid |
2022.0 2021.x |
Resolved 2022.1 |
| FME Server Apps | FME Server | In an FME Server App, you cannot click OK to run the App. FMESERVER-16186 |
This is likely because the workspace app contains a parameter that is required but is not visible and has no default value. Either set a default value or make the parameter visible. In the fixed versions of FME Server, users will be prompted to select a value for the parameter. |
2022.0 2021.x |
Resolved 2022.1 |
| File Upload | FME Server | An administrator user can write files to any location on the server drive hosting the FMEServer, which could result in unintended or malicious file uploads. FMESERVER-18293 |
See Known Issue: FME Server vulnerability with arbitrary path traversal and file upload |
2022.0.1.0 2022.0 2021.x 2020.x 2019.x |
Resolved 2022.0.1 2021.2.6 |
| FME Server Apps | FME Server | A server app (workspace or gallery) has ‘Require Authentication’ enabled and the allowed user is a user imported from Azure AD. When this user navigates to the app URL they are prompted to log in. After selecting ‘Sign in with Microsoft’ they are redirected to the FME Server home page instead of the app. FMESERVER-17846 |
First, log into FME Server and then go to the server app URL. |
2022.0 2021.2 |
Resolved 2022.1 |
| Automations | FME Server | In an Automation you configure a Schedule with a set End Time, then start the Automation. Once the End Time passes you cannot stop the Automation. The error is: Unable to disable '<AUTOMATIONNAME>': Schedule task (Category: <UUID> Name: <UUID>) must have an end time greater than the scheduler current time. FMESERVER-17998 |
Duplicate the Automation (this will copy it in a disabled state where it can now be edited) and then delete the original Automation. To duplicate the Automation go to 'Manage Automations'. Check the box next to the problem Automation and then select Actions > Duplicate. |
2022.0 2021.2 |
Resolved 2022.1 |
| Python | FME Desktop |
Executing Python scripts that change locale will result in unexpected errors in FME 2022.0 FMEENGINE-72009 |
See Known Issue: Executing Python scripts that change locale will result in unexpected errors in FME 2022.0 | 2022.0 |
Resolved 2022.1 |
| Users and Roles | FME Server | Can no longer use the Guest account to provide unauthenticated web service access. FMEFLOW-18196 |
Please see FME Deprecations. Provide a token to run workspaces without providing user credentials. | 2023.0 |
Deprecated 2023.0 |
| FME Server Apps | FME Server | Automation Apps file parameter does not allow the end-user to access FME Server Resources folder due to lack of permissions on the app token. FMESERVER-19084 FMESERVER-19197 |
Grant the app token permissions to Access and List to Resources’ subfolders of choice. For example, the Data folder, a Network directory, etc | 2022.2 |
Resolved 2023.0 |
| WFS Reader | FME Desktop | Specifying a search envelope for the WFS Reader will cause translation failure in FME 2022.1. The following error will occur: Unknown coordinate system ' ' specified - aborting FMEENGINE-74427 |
Use a Creator transformer to create a bounding box polygon, and then use this bounding box as a spatial filter with the FeatureReader. Set the Spatial Filter parameter of the FeatureReader to Bounding Box OGC-Intersect. | 2022.1 |
Resolved 2022.2 |
| FMEFlowJobSubmitter Transformer | FME Desktop | FMEServerJobSubmitter (version 4) is submitting jobs incorrectly to FME Server, if the child job has a text parameter and the FMEServerJobSubmitter is using an attribute value to submit it. FMEDESKTOP-13280 |
Keep the FMEServerJobSubmitter on version 3 and don't modify it in 2022.1. | 2022.1 |
Resolved 2022.2 |
| Microsoft Excel Writer | FME Desktop | Writing Excel files with a template file selected outputs a corrupt Excel file. Opening the Excel file in Microsoft Excel causes a recovery error to appear. FMEENGINE-74240 |
No known workaround. | 2022.1 |
Resolved 2022.2 |
| Schedules | FME Server | Schedules: The create category button is missing when building a schedule. FMESERVER-18947 |
To create a category, manually type the value into the field. Note this will only temporarily add the category for that particular schedule. Alternatively, click the down button on the right side of the dropdown menu and select an existing category. |
2022.1 |
Resolved 2022.2 |
| FME Workbench | FME Desktop | FME Workbench sometimes crashes when double-clicking the source file path in the navigator on macOS FMEDESKTOP-12415 |
No known workaround | 2022.0 |
Resolved 2022.1 |
| Python | FME Server | A workspace that requires a custom python module may fail " Python Exception <ModuleNotFoundError>: No module named ' '" error, even though the module was uploaded to the Python folders on FME Server. DEVOPS-2156 |
Go to Resources > Engine > Plugins > Python. Create a python39 folder. Then, upload the module to that folder. | 2022.0 |
Resolved 2022.1 |
| User Parameters | FME Server | No results are returned when attempting to search for a value in the Choice (Dropdown) parameter type. FMESERVER-18386 |
Change the Choice configuration in FME Desktop from Drop Down to List and set Allow Multiple Selection: No. Note, with this configuration the display cannot be different from the value. | 2022.0 |
Resolved 2022.1 |
| Jobs | FME Server | In FME Server, an error "There was an error retrieving the jobs" is encountered FMESERVER-16268 |
See Known Issue: There was an error retrieving the jobs in FME Server |
2021.x 2022.x 2019.x |
Resolved 2022.0 |
| Apache Tomcat | FME Server | The default error page, default index page, example JSPs and/or example servlets are installed on the remote Apache Tomcat server. These files should be removed as they may help an attacker uncover information about the remote Tomcat install or host itself. FMESERVER-10753 |
See Known Issue: FME Server Apache Tomcat Vulnerability with Default Files |
2022.1 2022.0 2021.x 2020.x 2019.x 2018.x |
Resolved 2022.2 |
| File Upload | FME Server | FME Server (formerly FME Server) offers the capability to create connections to network resources. The vulnerability, if exploited, allows for an authenticated user with access to an FME Server instance to download sensitive files or upload files, such as a web shell to the instance. FMEFLOW-18627 |
See Known Issue: FME Server Arbitrary File Upload Vulnerability |
2022.2.x 2022.1 2022.0 2021.x 2020.x 2019.x 2018.x |
Resolved 2023.0 2022.2.5 |
| File Upload | FME Server | FME Server (formerly FME Server) offers the capability to integrate various resources, including network-based resources. FME Server validates if a given path for a network-based resource refers to a network-based resource by verifying the string's format. In some situations, a user account with write privileges can bypass the validation by modifying the string, allowing an attacker to break out of the FME Server folder. FMEFLOW-20595 |
See Known Issue: FME Server Directory Traversal Vulnerability |
2022.2.x 2022.1 2022.0 2021.x 2020.x 2019.x 2018.x |
Resolved 2023.0 2022.2.5 |
| File Upload | FME Server | Both vulnerabilities, if exploited, allow for an attacker with access to connect to an FME Server web server, including over the internet, to download arbitrary files. FMEFLOW-18626 FMEFLOW-20800 FLOWHOSTED-2139 |
See Known Issue: FME Server Unauthenticated Arbitrary File Download via Directory Traversal Vulnerability |
2022.2.x 2022.1 2022.0 2021.x 2020.x 2019.x 2018.x |
Resolved 2023.0 2022.2.5 |
| Automations | FME Server | In my Automation, I have two Run Workspace actions, the second is meant to be triggered by a feature output by an Automations Writer in the first workspace. This feature is very large and the second workspace fails to submit. There is no evidence in the Automation Log that the translation request was ever received. FMESERVER-15954 |
See Known Issue: FME Server Automation fails to trigger job after Automation Writer |
2021.x 2020.x 2019.x |
Resolved 2022.0 |
| Engines | FME Server | A workspace contains an FMEServerJobSubmitter with Submission Mode = In Sequence and Wait for Jobs to Complete = Yes. Running a job with this combination launches an additional (child) engine process. FMEFLOW-17099 |
See Known Issue: FME Server Engine continuously restarts with ERROR 'Missing or expired workspace chaining context' |
2021.x 2020.x 2019.x |
Resolved 2022.0 |
| Backup and Restore | FME Server |
Performing a backup and restore where a restored item is owned by a custom username that already exists in the new FME Server installation results in the item token not being imported. Thus, the item is not properly reassigned to the user during restore. The restore may fail. Or, the item(s) may be reassigned to the admin performing the restore. FMEFLOW-18161 |
Assign items to the admin for the backup and restore process, then reassign them to the correct custom users after restore. | 2021.2.2 |
Resolved 2022.2 2023.0 |
| Oracle Spatial Reader | FME Desktop |
The following error messages are displayed for Oracle Spatial Readers and spatial filters. For Oracle Spatial Writing, the following error message is displayed. |
See Known Issue: Oracle 11g Spatial database is not able to return records due to a metadata error |
2022.2.1 2022.2 2022.1 2022.0 2021.x |
Resolved 2022.2.2 |
| FME Workbench | FME Desktop | FME Workbench crashes on startup - Qt6.Gui_fme.dll related error FMEDESKTOP-13325 |
2022.1.2 |
Resolved 2022.1.3 |
|
| Sorter Transformer | FME Desktop | Sorter fails with space in attribute name when passed as a parameter FMEDESKTOP-11986 |
Simply use the attribute name in the Sorter. | 2021.x |
Resolved 2022.0 |
| Automations | FME Server | In an Automation workspace action, the published parameters inside a collapsible Group Box are missing when you try to expand it. FMESERVER-17030 |
The Group Box's Collapsed State has three options that can be configured in FME Workbench's Parameter Manager: Automatic, Open, and Closed. Use the Automatic state to prevent the Group Box from being blank in Automations. |
2021.2 2021.1 2021.0.3 2021.0.2 |
Resolved 2022.0 |
| Google Sheets | FME Desktop | You have a Google Sheets Web Connection under the safe.google-sheets.Google Sheets web service provided with the Sheets package. Upon approving your 2FA, the authentication will not pass the Google verification process, and a 401: disabled_client error will appear in the web service authentication dialog. FMEENGINE-70066 |
See Known Issue: Google Sheets (v4) - Authorisation Error 401: disabled_client |
2021.0 2020.x |
Resolved Upgrade Package |
| Web UI | FME Server | Navigating to the Engines page of the FME Server Web UI and then trying to navigate elsewhere, the entire FME Server Web UI becomes unresponsive. FMESERVER-14953 |
Upgrade to FME 2021.0 | 2020.x |
Resolved 2021.0 |
| Active Directory | FME Server | In FME 2020.0 when trying to browse Active Directory to add new users to FME Server a ‘Duplicate Key <username>’ error pops up in the left-hand corner and the user import cannot be completed. FMESERVER-14730 |
To remedy the issue without updating FME Server: Remove the duplicate user account(s) from FME Server via the Web UI |
2020.0.1 2020.0 |
Resolved 2020.0.2 |
| FME Server Installation | FME Server | During installation, you specified a database password containing a special character and on FME Server login you cannot connect to core. DEVOPS-1037 DEVOPS-1468 |
See Known Issue: FME Server Database Schema Creation Fails When Password Specified During Install Contains Special Character |
2021.2 2021.1 2021.0.3 |
Resolved 2022.0 |
| JDBC Database Connection | FME Server | The JDBC Connection String specified in a distributed/fault-tolerant install is ignored. In the fmeDatabaseConfig.txt the connection string is jdbc:postgresql://:5432/fmeserver. DEVOPS-1721 |
Edit the DB_JDBC_URL in the fmeDatabaseConfig.txt to point to your connection string and restart FME Server to apply the change. | 2021.2 |
Resolved 2022.0 |
| Web Connections | FME Server | Trying to edit an FME Server Web Connection in the Web UI there is an error "Some input parameters are malformed". FMESERVER-17724 |
This error occurs if the FME Server Web Service definition was published to FME Server from FME Workbench 2021.2+. However, if the web service was uploaded by a restore you will not encounter this problem. To resolve the issue, delete the web service definition and publish it from an older version of FME Workbench and you should be able to make changes through the Web UI. Alternatively, edit the Web Connections in FME Workbench and re-publish them. | 2021.2 |
Resolved 2022.0 |
| Web Connections | FME Server | Attempting to publish/upload a user-defined web service you encounter the error "Unable to create derived service from a non system web service". FMESERVER-17883 |
This issue occurs when the associated template web service is already uploaded to FME Server. Go to Files & Connections > Web Connections > Manage Web Services and remove this service. | 2021.2 |
Resolved 2022.0 |
| Users and Roles | FME Server | When creating a new user in FME Server, FME Server does not validate the data on the backend, which can result in the username being overwritten via a POST request. FMESERVER-18291 |
See Known Issue: Lack of server-side validation when creating a new user in FME Server |
2021.2.x 2021.1 2021.0 2020.x |
Resolved 2021.2.6 |
| ArcGIS Portal Service Reader | FME Desktop | When trying to select a Feature Service in a Group in the ArcGIS Portal Feature Service Reader, you receive the error "An unknown error has occurred". FMEENGINE-72228 |
Use the ID to select the layer Open the feature service that you want to add in a web browser, in the web URL, there is an "id=" Copy the value to the "Feature Service" parameter for the ArcGIS Portal Reader inside brackets e.g. (64d00a7c2ed14b0f9da3857d83bd40aa) |
2021.2.3 2021.2.2 |
Resolved 2021.2.4 |
| Users and Roles | FME Server | When deleting a user account and transferring ownership of items, previously shared/granted permissions are revoked once ownership of item is transferred and previous owner account is deleted. FMESERVER-17670 |
See Known Issue: FME Server REST API V4 Deleting User Account Issue |
2021.2.2 2021.2.1 2021.2.0 2021.1 2021.0 |
Resolved 2021.2.3 |
| ArcGIS Portal Service Web Connection | FME Desktop | For ArcGIS Portal, if the password contains special characters such as @,#,$,%,&,* or !. The following error message encountered "Check your credentials and try again. The error code from the server was '400' and the message was: 'Unable to generate token. Invalid username or password.'" is displayed. The issue is encountered with both Web-tier and Portal-tier authentication i.e. Generate Token Basic Digest NTLM / Kerberos FMEENGINE-70895 |
Use Web connection for ArcGIS Portal(Oauth) to connect to the portal instance. (Works for Generate Token or SAML Authentication only) |
2021.2.1 2021.2.0 2021.1 2021.0 2020.2 |
Resolved 2021.2.2 |
| Tokens | FME Server | FME Token Service will hang if concurrent requests are sent to it. Example: http://localhost/fmetoken/ FMESERVER-17522 |
Use the REST API or the UI to create tokens |
2021.2.0 2021.1 |
Resolved 2021.2.1 |
| Automations | FME Server | When connecting an Automation component to a Workspace Action, the Workspace dropdown menu stays disabled/greyed out and you can't select a workspace. FMESERVER-17453 |
Switch the Action parameter to a different type, and revert it back to what you mean to set it as. | 2021.2.0 |
Resolved 2021.2.0.1 |
| Backup and Restore | FME Server | After upgrading to FME Server 2021.x , workspaces containing the FMEServerJobSubmitter fail to submit jobs with 'Reason - unable to connect to FME Server'. FMESERVER-17662 |
Option 1: Import your SSL Certificate via Internet Options Option 2: Remove and re-publish the Web Service Definition Option 3: Embed connection details | 2021.x | Workaround |
| FME Server Installation | FME Server | While installing the 32-bit FME Server, the installation seems successful, but FME Server will not start. In Windows Services, the FME Database Service will not be visible. FMESERVER-17228 |
The workaround is to install the 64-bit version of the C++ runtime before running the installer. It can be download from here. | 2021.x |
Deprecated Other |
| Microsoft Excel Writer | FME Server | When setting an Excel spreadsheet's output path to a local or UNC path with a space, it will be incorrectly written into the repositories folder. Example: C:\Path Space\file.xlsx gets written to C:\ProgramData\Safe Software\FME Server\repositories\Space\file.xlsx | Use two double quotation marks around the path. Example: ""C:\Path Space\file.xlsx"". |
2021.1.3 2021.1.2 2021.1.1 |
Resolved 2021.2 |
| Geocoder Transformer | FME Desktop | Geocoder: Unavailable to add a new Geocoder transformer from the Transformer Gallery or Quick Add. Existing workspaces will still run with the Geocoder, but it may be listed under "Upgradable Transformers" to upgrade to an FME package version. However, the updated Geocoder package is available in FME 2021.2 and is newer. FMEENGINE-70732 |
Copy a Geocoder transformer from a previous build of FME 2021.1 or upgrade to FME 2021.1.3 or newer. | 2021.1.2 |
Resolved 2021.1.3 |
| Web Connections | FME Server | We found an issue with our Web Connections that were stored in FME Server. If you notice a web connection not working in FME Server we advise upgrading. This was found in an ArcGIS Online connection but will affect all connections. FMESERVER-17219 |
Upgrade to FME Server 2021.1.2 or newer. |
2021.1.1 2021.1.0 2021.0 |
Resolved 2021.1.2 |
| FME Desktop Installation | FME Desktop | When trying to license FME Desktop 2021.0 or .1, you get an error message stating “This version of FME Desktop is no longer supported for trial licensing," and you're unable to specify your fixed or floating license in FME Licensing Assistant. IS-9491 |
Move existing licensing files or specify the license through the Command Line. See Known Issue: Unable to License Using FME Licensing Assistant in FME 2021.x |
2021.1 2021.0 |
Resolved 2021.2 |
| Backup and Restore | FME Server | An error similar to the following is returned when you attempt to run an FME Server backup: An error occurred: COM.safe.fmeserver.configuration. migration.FMEConfigurationException: org.apache.commons.compress. archivers.zip.Zip64RequiredException: path/to/file/file.ext's size exceeds the limit of 4GByte. FMESERVER-16787 |
The backup process was unable to zip files larger than 4GB. Manually move the file mentioned to another location, run the backup process, and restore the file manually. |
2021.0.3 2021.0.2 2021.0.1 |
Resolved 2021.1 |
| Database Connections | FME Server | Jobs fail because of a Database Connection error with messages such as ''unable to open database file' or file 'cannot be located'. The connection file is stored in FME Server’s Resources. FMESERVER-16510 |
Edit the database connection to reference the database file path directly.
with: /data/fmeserver/resources/data/MyFolder/MySQLiteFile.sl3 |
2021.0.1 2021.0 |
Resolved 2021.0.2 |
| AttributeManager Transformer | FME Desktop | "Bad variant access" error when renaming numeric attributes. Typically this error has been seen when using the AttributeManager but could occur with the AttributeCreator or other related transformers. FMEENGINE-70052 |
Upgrade to FME 2021.0.3.2 or newer | 2020.2.5 |
Resolved 2021.0.3.2 |
| FME Workbench | FME Desktop | You may experience a workspace hang or "Error running translation". This occurs when FME is building bulk mode feature from regular features in the following options: FeatureJoiner AttributeKeeper (Create Bulk Features=Yes) FFS Writer (Enforce Strict Schema=Yes) SQLite Non-Spatial Writer MapInfo Extended Writer or input features have attributes with missing values for some chunks of bulk mode features and not others resulting in a crash if the schema changes. FMEENGINE-70071 |
Upgrade to FME 2021.1.0.1 or newer | 2021.1 |
Resolved 2021.1.0.1 |
| VertexCreator Transformer | FME Desktop | When using the VertexCreator in Add Point mode to create point features, the output features are lines instead of points. This will most frequently occur with CSV and Excel input data sources. FMEENGINE-70231 |
This is a conflict with intentional behaviour that automatically generates points when latitude/longitude attributes are detected. See Known Issue: VertexCreator creates lines instead of points |
2021.1 2021.0 |
Resolved 2021.2 |
| FME Server Apps | FME Server | The "Run Workspace" page header is visible in FME Server Apps and it overlaps with custom banner images. FMESERVER-17123 |
Upgrade to FME Server 2021.1.0.1 or newer | 2021.1 |
Resolved 2021.1.0.1 |
| FME Workbench | FME Desktop | Selecting feature types to read for a Single Merged Feature Type reader using the Feature Types to Read parameter in the Navigator pane causes "Failed to Retrieve Feature Type" error. FMEDESKTOP-11429 |
Enable Prompt for User Parameters in the toolbar or through the Run menu and select the feature types to read through the Translation Parameter Values dialog. | 2021.0 |
Resolved 2021.1 |
| User Parameters | FME Desktop | User Parameter for Choice missing the option to import values from Reader or Writer formats FMEDESKTOP-11422 |
Upgrade to FME 2021.1 build 21554 or newer | 2021.0 |
Resolved 2021.1 |
| AttributeFilter Transformer | FME Desktop | AttributeFilter version 4: When using attribute values with characters separated by a space, they are not filtered FMEENGINE-70115 |
Upgrade the transformer to version 5 or upgrade to FME 2021.0.3.2 build 21332 or FME 2021.1.0.1 build 21614 or newer. | 2021.0 |
Resolved 2021.1.0.1 2021.0.3.2 |
| Jobs | FME Server | When a job is submitted it does not run and remains in the 'Queued' state. FMESERVER-16503 |
Try either of the following options:
|
2021.0 |
Resolved 2021.0.1 |
| Streams | FME Server | On the Engines page one or more engines are not running jobs and the Queue is Assigned to stream "". The engine cannot be reassigned to a different queue. FMESERVER-16513 |
See Known Issue: Removing a stream does not reassign the engines back to the Default queue | 2021.0 |
Resolved 2021.0.1 |
| Active Directory | FME Server | After creating a new Active Directory Connection and enabling Single Sign-On it fails, in the fmeserver.log there is a WARN message 'No SASL mechanism was specified in configuration' FMESERVER-16571 |
See Known Issue: Single Sign-On fails with WARN 'No SASL mechanism was specified in configuration' | 2021.0 |
Resolved 2021.0.1 |
| Single Sign On | FME Server | You have installed FME Server with a distributed database type Oracle or Microsoft SQL Server and Single Sign-On login fails, while manual Active Directory Login succeeds. FMESERVER-16763 |
Upgrade to FME 2021.1 | 2021.0 |
Resolved 2021.1 |
| Reader Feature Types | FME Server | "After publishing a workspace to FME Server that contains a merged feature type reader it is not possible to run the workspace via the Run Workspace page or Automations. FMESERVER-16357 FMESERVER-16348 |
Upgrade | 2020.2 |
Resolved 2021.0 |
| Custom Transformers | FME Server | Workspaces with linked custom transformers will fail if the custom transformer is in the repository or workspace folder. FMESERVER-15940 |
Upload the custom transformer to a shared resource folder |
2020.2.0 2020.1 |
Resolved 2020.2.1 |
| Installation | FME Desktop | As of FME 2020 and newer, the SQL Server Native Client 2012 will no longer be included in the installation. As such you may encounter issues with connecting to an Enterprise (SDE) Geodatabase. | If you are unable to connect to an SDE Geodatabase after upgrading to FME 2020.X, or newer, please install the SQL Server ODBC client. For more information about supported SQL Server clients for ArcGIS, please see the following page: https://desktop.arcgis.com/en/system-requirements/latest/database-requirements-sqlserver.htm |
2020.x | Workaround |
| Installation | FME Desktop | If attempting to connect to SQL Server on a new system with no previous install of FME Desktop 2020.0, you may encounter a missing driver error. | If you are unable to connect to a SQL Server database, install the MSOLEDBSQL driver that is present in the FME Desktop installer. Searching in your FME install directory for 'MSOLEDBSQL' should bring up the installer. If you run that installer, and re-launch FME Workbench it should connect to SQL Server as expected. | 2020.x | Workaround |
| Database Connections | FME Desktop | As of FME 2020.x, certain JDBC Database formats were split from their original format family, and as a result, no longer share database connection details between Non-JDBC and JDBC database formats. When opening workspaces created in an older version of FME with these types of database connections you’ll notice a message in the Format dropdown “Microsoft SQL Server Non-Spatial (JDBC) (replaced by MSSQL_JDBC_NONSPATIAL_2)”. This will indicate the need to recreate the Database Connection in most cases. |
As such, database connections created in pre-2020.x FME builds will have to be remade for the specific Database format. Eg: A database connection created in 2019 for SQL Server, could be used for both the JDBC and non-JDBC SQL Server format. In 2020.x, you will have to make a new JDBC database connection to use it with SQL Server. |
2020.x | Unplanned |
| Web Connections | FME Server | After upgrading your FME Server to 2020.0 or newer, when users run workspaces that contain any web or database connections the translation will fail with the error “Unauthorized request by user due to lack of proper permissions”. | We made some security improvements regarding Web or Database connections for FME Server 2020. Therefore, after upgrading you will be required to reconfigure the necessary permissions. Please see this article for more information. | 2020.x | Workaround |
| Google Gmail Web Service | FME Desktop | You have a Gmail Web Connection under the Google Gmail (safe.emailer) web service provided with the Emailer package. The email address assigned to this web connection has received an email from Google App developers that FME does not pass the Google verification process and access will be blocked. FMEENGINE-66073 FMEENGINE-66582 |
See Known Issue: Google App Developers report FME will no longer have access to your Gmail data [Emailer v0.1.0 to v1.x.x] |
2020.x 2019.x |
Resolved Upgrade Package Emailer v2.0.0 |
| Engines | FME Server | After install, FME Server continually tries to launch two engines, however I am only licensed for a single engine. This results in errors reported in the fmeserver.log and subsequently System Events. However when I try and change the engine count to one, it always reverts back to two. | Drop the engine count from 2 to 0 first and then change the count back up to 1 and this change should now be applied successfully. | 2020.x | Workaround |
| SMEServerNotifier | FME Server | If the FMEServerNotifier transformer is used in FME Desktop 2019 to notify an FME Server 2020 topic it will not work. This is because the FME Server REST API V1 was deprecated in 2020 and the FMEServerNotifier used V1 in 2019. | If you use FME Desktop 2020 to notify an FME Server 2020 topic it will work. | 2020.x | Deprecated |
| FME Server Web UI | FME Server | When trying to view a file stored in a network-based resource in the FME Server web UI it returns 'Path <sharedresource>/<filename>.ext is not a valid path'. | Edit the shared resource to include a trailing slash at the end of the file path. | 2020.x | Workaround |
| FME Server | If an IMAP email server is only enabled to use TLS1.2, then FME Server will not be able to connect to it. | To fix this modify the FMEProcessMonitorCore file: 1. Find your processMonitorConfigCore.txt file (it should be in your install directory which is by default located C:\apps\FMEServer\Server or C:\Program Files\FMEServer\Server) 2. Create a backup of this file (it's good to have if we want to revert this). 3. Open it as an admin and find # Start FME Server Publisher Plugin (imap) then insert -Dmail.imap.ssl.protocols=TLSv1.2 -Dmail.imaps.ssl.protocols=TLSv1.2 after -Dmail.imaps.fetchsize=1048576 |
2020.x | Workaround | |
| User Parameters | FME Server | On FME Desktop, we create a relative path to find data if the data is located in the same folder as the workspace or a subfolder of the workspace. Once the workspace is uploaded to FME Server, sometimes these relative paths are not removed. One way to check if this issue is affecting you is to open up your workspace in a text editor and see if you can find the parameter value FME_MF_DIR_ENCODED. | 1. Save your workspace in a new location 2. Update your readers to ensure that the relative path is removed. Save the workspace again. 3. Upload the workspace to FME Server. |
2020.x | Workaround |
| FME Server Apps | FME Server | When an SVG image is uploaded into a Workspace or Gallery App it looks ok on the edit page, but once the App is created the image does not load. | Use a PNG or JPG image instead. | 2020.x | Unplanned |
| FeatureReader Transformer | FME Desktop | Reading features fails when using the FeatureReader if feature type names contain spaces. Reading is successful using a regular reader for the same feature type. | Use the regular reader or upgrade to the latest release of FME 2020. | 2020.0 |
Resolved 2020.0.0.1 |
| GML Reader | FME Desktop | GML reader generates the message "xml-geometry-ref Geometry Builder: unable to adopt the below geometry because construction for its own geometry has already been finalized". This is most likely because it contains xlink_href="". We added support to xlinked, referenced geometry in 2019.1. Previous versions of FME ignored this. | Use GML reader's ignore schema mode, or upgrade to the latest release or beta of FME | 2020.0 |
Resolved 2020.1 |
| FME Hub | FME Desktop | Issue affects non-offical packaged formats. For example, in Workbench try to add a reader of type "Japanese Fundamental Geospatial Data". You can find it in the formats list, but when you select it, the formats field doesn't accept it. | No workaround. Upgrade to 2020.0.2.1 b20238 | 2020.0 |
Resolved 2020.0.2.1 |
| FME Workbench | FME Desktop | When accessing Tools>FME Options, FME may become unresponsive and crash. This is a result of an identified issue with FME Desktop 2020.1 (builds 20594, 20596, 20608) and ArcGIS Pro 2.6 | There are a few ways to workaround this issue: Use FME 2020.1 32-bit with ArcGIS Desktop 10.8.1, OR Use FME 2020.0 with ArcGIS Pro 2.6, OR Use FME 2020.1 64-bit with ArcGIS Pro 2.5 |
2020.0 |
Resolved 2020.1.2 |
| FME Workbench | FME Desktop | The correct feature count appears on the Reader feature types with spaces in name but no feature cache will appear in any downstream transformers when using Partial Runs. When this behavior occurs in a workspace where some Reader feature types contain spaces and some do not, features may appear to 'disappear' within the workflow. This behavior affects FME 2020.1 (builds 20591, 20596, all platforms). |
There are a few ways to workaround this issue: Disable Feature Caching Purge feature caches from Reader feature types and perform Partial Runs from a downstream transformer |
2020.0 |
Resolved 2020.1 |
| Environment Variables | FME Desktop | Using FME 2020.1.x and FME_TEMP environment variable set to a root volume (eg. D:\ ), FME Workbench, Data Inspector or Licensing Assistant, will crash when starting up. In the Windows Event Viewer, an application error is logged with the faulting module name: fmeutil.dll |
Please make a top-level directory on the drive (e.g. D:\FMETEMP) and set FME_TEMP to this directory. | 2020.0 |
Resolved 2020.2 |
| Licensing | FME Desktop | Using FME 2020.1 (builds 20594 to 20624) and connecting to a floating license, the FME Licensing Assistant reports "This application cannot be used with the current license". This is error is due to the presence of an expired temporary license. An example of the dialogue you may see: | To resolve this issue, you can remove the temporary license by finding the *.fmelic file in one of the following directories: C:\ProgramData\Safe Software\FME\Licenses <fme-install-folder>/licenses C:\users\<user>\Documents\FME\Licenses You can open the *.fmelic file in a text editor to see if it has an expiry date and then delete the file. You should be able to continue using your floating license. |
2020.0 |
Resolved 2020.1.3 |
| ArcGIS Online/Portal Writer | FME Desktop | In FME Desktop 2020.2.x, when creating a new ArcGIS Online/Portal writer, you can not select an existing feature service within a shared group. For an existing feature service writer shared with a group, you may encounter an error as well. | Use the ID to select the layer Open the feature service that you want to add in a web browser, in the web URL, there is an "id=" Copy the value to the "Feature Service" parameter for the ArcGIS Online writer inside brackets e.g. (64d00a7c2ed14b0f9da3857d83bd40aa) |
2020.0 |
Resolved 2021.0 |
| Google KMZ Writer | FME Desktop | Using FME Desktop 2020.2.x writing out with Fanout Dataset Fanout Expression with the .kmz file extension resulted in an error and no data being written out. Files with “.” at beginning of the filename. | Do not set kml_document attribute on output features. Or do not use “.” in filenames instead use “_” | 2020.0 |
Resolved 2020.2 |
| Publishing | FME Server | When publishing a workspace to FME Server via FME Desktop, if the FME Server username contains international characters or the password contains international characters such as 本å ä ö à, FME Workbench will give an authentication error. | Create an FME Server username and password without these characters, or use a different account to publish. Logging into FME Server is unaffected. | 2020.0 |
Resolved 2021.0 |
| Installation | FME Server | In the FME Server Web UI when I try and view Resources or Broadcast Messages it says “We could not find what you wanted”. In Automations I cannot set the protocol type for triggers or external actions. | You can either upgrade to 2020.0.0.1 or you will need to update a web application config file to correctly reference the database URL. For more information and full instructions on how to do this please see this article: https://knowledge.safe.com/articles/109765/known-issue-fme-server-resourcesautomations-could.html. | 2020.0 |
Resolved 2020.0.0.1 |
| Automations | FME Server | When building an Automations you see 'No Connections Available' while configuring a workspace that contains a database parameter. If you configure the job via the Run Workspace page the connection appears. | Instead of using the default user parameter, create a text user parameter and link it database parameter. Step by step instructions on this can be found here. | 2020.0 |
Resolved 2020.1 |
| Publishing | FME Server | When attempting to re-publish a workspace to FME Server (e.g. a workspace that is already uploaded to FME Server - not just via the re-publish button) if the workspace is registered to the Notification Service and the 'Parameter to Get Topic Message' is set the workspace will fail. Reason was: The following readers or writers are included in an enabled service, but are not present in the workspace: <FORMAT_PARAM> | Delete the workspace from FME Server, and then publish it again. Alternatively, change workflows to no longer use the Notification Service. See the best answer on this Community post for details on how this could be done. | 2020.0 |
Resolved 2020.1.3 |
| FME Server Apps | FME Server | In FME Server 2020.2 when I view my Gallery App there are no browser icons shown. | No workaround. Upgrade to 2020.2.1 | 2020.0 |
Resolved 2020.2.1 |
| Custom Transformers | FME Server | Workspaces with linked custom transformers will fail if the custom transformer is in the repository or workspace folder. | To fix this issue you can upgrade your FME Server or follow one of the workarounds listed in this article. |
2020.1 2020.0 |
Resolved 2020.2 |
| Proxy | FME Server | In FME Server 2020.1.1, if you have enabled a proxy in the UI and set up exceptions for the FME Server, FME Server will respect them, unless there is a Python in the workspace. | If you open fmeServerConfig.txt. Under the heading FME SERVER SETTINGS START, add the following line: ENABLE_ENGINEPROXY=false |
2020.1.x 2020.0 |
Resolved 2020.1.3.2 |
| Merged Feature Types | FME Server | After publishing a workspace to FME Server that contains a merged feature type reader it is not possible to run the workspace via the Run Workspace page or Automations. | Either upgrade or see this article for a workaround. | 2020.0 |
Resolved 2020.2 |
| ArcGIS Online / ArcGIS Portal Feature Services | FME Desktop | When writing to an existing ArcGIS Portal or ArcGIS Online Feature Service layer, there are errors reported in FME log files: Encountered an unexpected error. The error code from the server was '500' and the message was: 'JSONObject[""globalId""] not found.'. Details: '' FMEENGINE-67222 |
See Known Issue: ArcGIS Online / ArcGIS Portal feature services: common errors writing to existing feature services mismatched schema/data types |
2020.x 2019.x |
Resolved 2021.0 |
| Emailer Transformer | FME Desktop | When using the Emailer in FME Desktop, if the SMTP authentication email password contains international characters such as äåø, the workspace will fail with the error: 2020-10-23 15:52:48| 1.3| 0.1|WARN |Emailer: <class 'UnicodeEncodeError'>: 'ascii' codec can't encode characters in position 0-2: ordinal not in range(128). This is caused by an unresolved bug in the Python 3 standard library. For more information on this bug see https://bugs.python.org/issue29750https://bugs.python.org/issue29750. This issue was not present in FME 2018 or older because these versions used the Python 2.7 library which has looser text encoding practices. |
To resolve this issue, please change your email password to remove these characters. If you are unable to change your password, please downgrade to FME 2018 or older to use Python 2.7. | 2019.x | Workaround |
| Installation | FME Desktop | macOS Catalina may identify downloaded installers as a risk, and prevent opening via double-click | There are several ways to get around this! #1 Instead of double-clicking the FME Desktop Installer icon, right click and select "Open". This will present a slightly different dialog which presents a warning, but allows the user to select "Open" anyway and continue with installation after providing password credentials. #2 Go to Settings / Security & Privacy after receiving the error message, and under General / Allow Apps Downloaded From .. select "Open Anyway" next to "FME Desktop Installer" #3 Optionally, you can also get around this from the command line by removing the quarantine Extended Attribute on the file: xattr -d com.apple.quarantine /path/to/file |
2019.x |
Resolved 2020.0 |
| FME Workbench | FME Desktop | Some users may experience application crashes with combinations of older Windows operating systems (specifically Windows 7) and third party applications such as Photoshop and Civil3D after installation of FME 2019.x. | Upgrade to FME 2019.1.3+. Note prior versions of FME (2018.x) do not exhibit this behaviour either. |
2019.1 2019.0 |
Resolved 2019.2 |
| File Geodatabase Writer | FME Desktop | FME 64-bit fails to write to Geodatabase (File and SDE) with ArcGIS Pro 2.4 and 2.5. The following is an error message you may encounter: An error occurred while attempting to insert a row into the table '<tablename>' using a cursor. The error number from ArcObjects is: '-2147418113' The error message from ArcObjects is: {} An error occurred while attempting to insert a row into the table '<tablename>' using a cursor. |
There are a couple of workarounds to resolve this with FME 2019 64-bit: 1. Use ArcGIS Desktop with 64-bit Background Geoprocessing OR 2. To continue using FME with ArcPro, switch the Python Compatibility to “Esri ArcGIS Pro 2.1 to 2.5 Python(3.6)”. For FME 2019.x and higher, iIf you have no user defined Python (start-up/shutdown scripts or Python Caller) in your workspace, then please add a small startup Python script. To do this go to Navigator > Workspace Parameters > Scripting > Startup Python and add one line: print() The option is required as an additional step due to our effort to reduce the workspaces with “Python 2.7” since Python 2.7 is deprecated |
2019.x |
Resolved 2020.0 |
| File Geodatabase Writer | FME Desktop | When creating a File Geodatabase using the latest Esri ArcPro release (2.4/2.5 beta), and writing to it via FME's Esri Geodatabase (File Geodatabase API) format, an error will occur. The error message may look like: ERROR |Geodatabase Error (-2147219115): The row contains a bad value. ERROR |FileGDB Writer: Could not create feature class 'TestPolygon' ERROR |A fatal error has occurred. Check the logfile above for details WARN |Geodatabase Error (-2147418113): Unexpected operation. WARN |FileGDB Writer: Could not disable Load Only Mode for feature type 'TestPolygon' |
Use a File Geodatabase created in ArcGIS Desktop or use the Esri File Geodatabase (FGDB) writer. | 2019.x |
Resolved 2020.0 |
| GeoJSON Writer | FME Desktop | GeoJSON writer produces an invalid GeoJSON root structure if writing more than one feature type. The GeoJSON writer currently wraps the JSON feature collections with an array when multiple feature types are output. The GeoJSON standard mandates a FeatureCollection object as the root so this is incorrect (it is valid JSON but not valid GeoJSON). | Write one feature type per GeoJSON output document. This can be done using one writer per feature type or dataset fanout on feature type name. In this case the root object is a FeatureCollection and our output is valid. |
2018.0 2017.x |
Resolved 2018.1 |
| Database Connections | FME Desktop | A user may encounter an error inconsistently while retrieving database or web connections either via FME Options or within a Reader/Writer: Error message: "Error retrieving connections" Java Virtual Machine (JVM) memory issues on 32-bit Windows may prevent addition of certain readers/writers, or the correct application of web or database connections in FME 2018.0 Desktop x86. |
64-bit FME 2018.0 does not exhibit this issue. Unless you require 32-bit FME for format support, we recommend using the 64-bit installer. If you do require 32-bit formats, setting the following FME environment variables should resolve the issue in 2018.0: SET FME_JVM_MAX_HEAP_SIZE=128M SET FME_JVM_MIN_HEAP_SIZE=128M If you are still experiencing intermittent connection issues, try altering the heap size: Go to the Control Panel > System and Security > System > Advanced System Settings > Environment Variables: Create 2 NEW SYSTEM Environment variables FME_JVM_MAX_HEAP_SIZE=64M FME_JVM_MIN_HEAP_SIZE=64M If 64M doesn't work, try: 32M, 64M, 96M, 96M, 150M, 256M, 512M. |
2018.x |
Resolved 2019.0 |
| FME Desktop Installation | FME Desktop | After upgrading to macOS Big Sur, FME Workbench does not open when trying to launch from /Applications/<FME Version>/ DOT-5737 |
If you need to use previous versions of FME, please launch FME Workbench via the /Library/ rather than /Applications/ |
2020.2.x 2020.1 2020.0 2019.x 2018.x |
Resolved 2020.2.4 |
| FME Workbench | FME Desktop | After upgrading to macOS Monterey, FME workspaces are failing to run. Error messages can vary depending on what action you are trying FMEENGINE-71121 |
See Known Issue: FME fails to run on macOS Monterey |
2021.1.x 2021.0 2020.x 2019.x 2018.x |
Resolved 2021.1.3.1 |
| Autodesk AutoCAD Map 3D Object Data Reader | FME Desktop | "AUTOCAD_OD: Unable to add reader Failed to load object data handling module. No object data will be read" FMEENGINE-66765 |
Upgrade |
2020.x 2019.x 2018.x |
Resolved 2021.0 |