Skip to main content
  • EN

You shouldn't notice anything but lots has changed under the hood.

Encryption, private and public… New in FME 2017 is how encryption is used with the database connection file where your connection information is stored.

We now encrypt for public access as well as private access. In the past anyone with FME installed could read the connection file as FME contained a global encryption key to access the database connection file. This didn’t give them access to see passwords but they could use the connection information in FME.

Now, public access to the connection file is controlled by giving FME access to a public key file. By default this public key is stored in the same location as the database connection file so we do recommend moving that to a secondary location where FME can be pointed to in order to access it. This ensures that if someone locates the connection file they won’t have the key file so they can’t decrypt the information.

In regular FME use, any user with the database connection file and access to the public key can use any of the named connections that are public. This is helpful when sharing a common connection file on a network share. The settings are configured in the FME Options>FME Paths.

Image 1: Notice the public and private key file locations

New file name: In FME 2016 and older the database connection file was called ‘namedConnections.data’. In FME 2017 this file is now called ‘fme_connections.data’. If you’ve had an older version of FME installed, FME 2017 will automatically migrate the old file to the new file when it first opens and finds a valid database connection file. FME leaves the old file unaltered. FME 2017 will only migrate the old file the first time it opens where it doesn’t find the fme_connections.data file in the connection storage location.

Sharing Database Connection file on the network.

Just like before, if you store your connection file in an UNC location FME automatically exposes an option to make a connection public. Otherwise it will be private to you (in this public database connection file) and only you will be able to use those connections with your private key file (which you should never share).

Let us know if you have any questions.

If anyone experiences migration issues from 2016 to 2017 do let us know.

Hi,

i have problems with public database connections

2017-09-22 15:20:53| 3.7| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file
2017-09-22 15:20:53| 3.7| 0.0|ERROR |unable to open database file

if i start the process insise workbench it works, if i try to start it via batch it doesnt work

Hi,

i have problems with public database connections

2017-09-22 15:20:53| 3.7| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file
2017-09-22 15:20:53| 3.7| 0.0|ERROR |unable to open database file

if i start the process insise workbench it works, if i try to start it via batch it doesnt work

Hi @sebastiangoerck

 

Are you able to share the entire log file? Which version of FME are you running?

ha-to-sst-kopie.txt

Hi,

is use FME 2017.1 (17539 WIN64)

Here the error Message form Log:

 

2017-09-24 14:00:13| 10.5| 8.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp

(The system cannot find the path specified).

2017-09-24 14:00:13| 10.5| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file

2017-09-24 14:00:13| 10.5| 0.0|ERROR |unable to open database file

ha-to-sst-kopie.txt

Hi,

is use FME 2017.1 (17539 WIN64)

Here the error Message form Log:

 

2017-09-24 14:00:13| 10.5| 8.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp

(The system cannot find the path specified).

2017-09-24 14:00:13| 10.5| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file

2017-09-24 14:00:13| 10.5| 0.0|ERROR |unable to open database file

@sebastiangoerck Thanks for the log.

 

 

My guess is that your E drive is mapped and the command window knows nothing of this mapped drive. How are you running the command window to run the batch? What user? Are you using Windows Task Scheduler?

 

 

Could you use a UNC path to point to the public database connection file? Then if you are running the batch file in a command window that was opened by you (the logged in user) it should have permissions to get to location on the network.

 

ha-to-sst-kopie.txt

Hi,

is use FME 2017.1 (17539 WIN64)

Here the error Message form Log:

 

2017-09-24 14:00:13| 10.5| 8.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp

(The system cannot find the path specified).

2017-09-24 14:00:13| 10.5| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file

2017-09-24 14:00:13| 10.5| 0.0|ERROR |unable to open database file

 

Hi,

 

is start the bench via SQL Server Job Manager by Username "S2SQLAgent".

 

fme.exe <path and filename from bench>

 

 

if i change the default path in fme 2017.1 to an UNC path on the server i got the same error:

 

2017-09-26 08:38:43| 3.3| 2.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp (The system cannot find the path specified).2017-09-26 08:38:43| 3.3| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file2017-09-26 08:38:43| 3.3| 0.0|ERROR |unable to open database file

 

 

then i changed the path for dbconnections to c:\\FME_DBConnection\\ on the server...i always got the same error:

 

2017-09-26 08:38:43| 3.3| 2.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp (The system cannot find the path specified).2017-09-26 08:38:43| 3.3| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file2017-09-26 08:38:43| 3.3| 0.0|ERROR |unable to open database file

 

Hi,

 

is start the bench via SQL Server Job Manager by Username "S2SQLAgent".

 

fme.exe <path and filename from bench>

 

 

if i change the default path in fme 2017.1 to an UNC path on the server i got the same error:

 

2017-09-26 08:38:43| 3.3| 2.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp (The system cannot find the path specified).2017-09-26 08:38:43| 3.3| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file2017-09-26 08:38:43| 3.3| 0.0|ERROR |unable to open database file

 

 

then i changed the path for dbconnections to c:\\FME_DBConnection\\ on the server...i always got the same error:

 

2017-09-26 08:38:43| 3.3| 2.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp (The system cannot find the path specified).2017-09-26 08:38:43| 3.3| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file2017-09-26 08:38:43| 3.3| 0.0|ERROR |unable to open database file
Hi @sebastiangoerck, thank you for the information.

 

I'll check in with the Dev team for some ideas on this.

 

The way you are running it from S2SQLAgent certainly could be a problem.

 

Can I clarify when you moved the file to the C drive was the S2SQLAgent running locally on the system and what user it was running as?

 

ha-to-sst-kopie.txt

Hi,

is use FME 2017.1 (17539 WIN64)

Here the error Message form Log:

 

2017-09-24 14:00:13| 10.5| 8.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp

(The system cannot find the path specified).

2017-09-24 14:00:13| 10.5| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file

2017-09-24 14:00:13| 10.5| 0.0|ERROR |unable to open database file

@sebastiangoerck, I spoke with our Developer and they think there may be an issue with the path for the public encryption key. I'm attaching a screen grab of my settings for Connection Storage. Notice the Public Key File.

On your system can check something for me in FME Options?

 

In Default Paths under Public Encryption Key group could you confirm the path for the Public Key File?

 

In the log yours appears to include '.data': "E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks"

 

It should be:

 

"E:\\file_ressource_geo\\04_FME\\namedConnections\\fme_publicKey.jceks.tmp" (the .data is removed).

 

This path and file should coincide with your Connection Data Directory path.

 

 

If the path was already correct then I think I'd like to make a case and have a screen share with you.

 

ha-to-sst-kopie.txt

Hi,

is use FME 2017.1 (17539 WIN64)

Here the error Message form Log:

 

2017-09-24 14:00:13| 10.5| 8.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp

(The system cannot find the path specified).

2017-09-24 14:00:13| 10.5| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file

2017-09-24 14:00:13| 10.5| 0.0|ERROR |unable to open database file

The Job on the Server were started from the SQL Server Agent by the Username "S2SQLAGENT"

 

I also tried to put the db connectionfiles into the Username Folder:

 

C:\\Users\\S2SQLAGENT\\AppData\\Roaming\\Safe Software\\FME ....but i got also the same error.

 

The Settings for the Default path Looks like so:

 

 

 

On the Server is also the Version 2016.1 installed and the older Jobs works fine.

 

 

ha-to-sst-kopie.txt

Hi,

is use FME 2017.1 (17539 WIN64)

Here the error Message form Log:

 

2017-09-24 14:00:13| 10.5| 8.3|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp

(The system cannot find the path specified).

2017-09-24 14:00:13| 10.5| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file

2017-09-24 14:00:13| 10.5| 0.0|ERROR |unable to open database file

 

 

...i forgot the screenshot

Hi,

we still have the problem...do you have any new findings?

 

although the default path on the server is set to "E:\\file_ressource_geo\\04_FME\\connections", the logfile throw an error:

2017-10-10 15:19:53| 3.5| 2.5|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp (The system cannot find the path specified).

 

2017-10-10 15:19:53| 3.5| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file

2017-10-10 15:19:53| 3.5| 0.0|ERROR |unable to open database file

Hi,

we still have the problem...do you have any new findings?

 

although the default path on the server is set to "E:\\file_ressource_geo\\04_FME\\connections", the logfile throw an error:

2017-10-10 15:19:53| 3.5| 2.5|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp (The system cannot find the path specified).

 

2017-10-10 15:19:53| 3.5| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file

2017-10-10 15:19:53| 3.5| 0.0|ERROR |unable to open database file

I also have a customer with the same issue any update on this would be useful

 

 

Hi,

we still have the problem...do you have any new findings?

 

although the default path on the server is set to "E:\\file_ressource_geo\\04_FME\\connections", the logfile throw an error:

2017-10-10 15:19:53| 3.5| 2.5|INFORM|Error generating new encryption key. Error: E:\\file_ressource_geo\\04_FME\\namedConnections.data\\fme_publicKey.jceks.tmp (The system cannot find the path specified).

 

2017-10-10 15:19:53| 3.5| 0.0|WARN |Internal Error: Encountered named connection database error: unable to open database file

2017-10-10 15:19:53| 3.5| 0.0|ERROR |unable to open database file

the problem has not been solved yet, we have not received any further help or suggestions from safe.

 

our workaround is = use of version 2016.1 :-(

 

 

I'd like multiple users to be able to run a workbench containing a database connection, but not allow them to use this database connection in their own workbenches. Is this possible?

Reply


Community Stats

30,108
Posts
114,295
Replies
37,743
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.