FME Flow Troubleshooting: Repositories

Full Guide: FME Flow Troubleshooting Guide

Are you encountering issues accessing the FME Flow Repository folders? Please read below for some common troubleshooting tips, questions, and resources.

In 2023, FME Server underwent a name change and is now known as FME Flow. Since this article discusses features present in previous versions of FME, it will refer to both names interchangeably, using the appropriate product name based on the year the feature was introduced. For more information on the rebranding, see our website. 
 

Content Overview

Initial Troubleshooting
Common Issues
Known Issues
Are you still experiencing issues? ​​​​​​​
Have ideas on how to improve this? ​​​​​​​

Initial Troubleshooting

• Does the FME Flow User have proper permissions to access (or run) the Repository / Workspace?
• Is the User able to create an empty Repository using the web interface?
• There are many Log Files that may help identify errors related to issues with FME Flow Repositories. Start by checking those listed below.
  <FMEFlowSystemShare>\resources\logs\core\current\fmeserver.log
  <FMEFlowSystemShare>\resources\logs\core\current\fmesharedresource.log
  <FMEFlowSystemShare>\resources\logs\engine\current\*.log

Common Issues

“After installing FME Flow, the Repository page is blank in the web interface.”

This may occur if the post-installation configuration scripts have not been run. Please see this article for more information.

“Repository home directory is not a directory’ error when using a network share for FME Flow Repositories.”

This error might be encountered if the user account running the FME Flow Windows Services does not have proper network permissions. Please see this article for more information.

"I can't rename my repositories on FME Flow?"

This is not an option on FME Flow. You would need to create a new repository for your workspaces to be published to.

Known Issues

"My Excel spreadsheet is written incorrectly into my repository when there is a space in my output path."

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. This issue has been fixed in FME Server 2021.1.2 b21784. The workaround would be to use two double quotation marks around the path. Example: ""C:\Path Space\file.xlsx"".
 

Are you still experiencing issues?

Please consider posting to the FME Community Q&A if you are still experiencing issues that are not addressed in this article. There are also different support channels available.

Have ideas on how to improve this?

You can add ideas or product suggestions to our Ideas Exchange.