Known Issue: FME Server Database Connection Error 'unable to open database file' or 'cannot be located'

Symptom 

FME Server jobs fail because of a Database Connections error. The Database Connection connects to a file uploaded to FME Server.

Examples of errors: 

ERROR |SQLite 3 Reader: Failed to open database '$(FME_SHAREDRESOURCE_DATA)/MyFolder/TestSQLiteFile.sl3'.  SQLite3 Engine error: `unable to open database file'

or

ERROR |OGCGEOPACKAGE reader: file '$(FME_SHAREDRESOURCE_DATA)/MyFolder/TestGpkgFile.gpkg' cannot be located.  Please ensure the file exists and is accessible

Cause 

An FME Server Parameter within the Database Connection is not being resolved by FME Server.
 

Workaround

Edit the Database Connection to reference the database file path directly. 

1. Navigate to FME Server Files & Connections > Database Connections and select the Database Connection. 
2. Replace the Database parameter with an explicit path to the file database's location. FME Server must have permissions to access this location. Example:

$(FME_SHAREDRESOURCE_DATA)/MyFolder/MySQLiteFile.sl3

With:

/data/fmeserver/resources/data/MyFolder/MySQLiteFile.sl3

Troubleshooting

If this doesn't solve your issue, or you're not using FME Server 2021 or newer, consult our FME Server: Troubleshooting Connections for Web and Database guide.  

Beyond connections, refer to our general FME Server Troubleshooting Guide or How to Create a Great FME Server Support Case to get started making a case with us.