Skip to main content

I normally run FME Desktop at the office, where I'm storing named connections and associated files on an office network share, in order to facilitate sharing these between the development and production desktop licenses.

These files are backed up to my local drive every day.

Now, when I'm trying to run FME offline, without access to the office network, FME refuses to access the named connection, and even bars me from reading from a local SQL database although all connection data is entered manually.

This also happens after I change the references in under options to point to the local backup copies of the files in question.

WTF?

Why is FME refusing to work normally in this manner ?

Version 2022.2.2

What error messages come up? What are locations under the default paths in FME Options?

If there are any network paths in the later, then FME will be hung up trying to access them

image 


The error messages were ugly:

error messagesYesterday I may have made the mistake of not changing all three settings at once, assuming that the references to the key files would automagically follow the changed data path. They didn't!

I'm now back at the office, and have restored all three (simultaneously) settings to the network share, and it works normally. Yesterday I was forced to regerate the keys to make something work.


The error messages were ugly:

error messagesYesterday I may have made the mistake of not changing all three settings at once, assuming that the references to the key files would automagically follow the changed data path. They didn't!

I'm now back at the office, and have restored all three (simultaneously) settings to the network share, and it works normally. Yesterday I was forced to regerate the keys to make something work.

The error message seems to indicate the file with the keys cannot be found on your local c drive, maybe something went wrong with the synchronisation?


The error message seems to indicate the file with the keys cannot be found on your local c drive, maybe something went wrong with the synchronisation?

Nope, they were there alright. No problems with the sync.


The error messages were ugly:

error messagesYesterday I may have made the mistake of not changing all three settings at once, assuming that the references to the key files would automagically follow the changed data path. They didn't!

I'm now back at the office, and have restored all three (simultaneously) settings to the network share, and it works normally. Yesterday I was forced to regerate the keys to make something work.

Is it now working as expected?


It was an "error 40" (as in 40 cm from the screen, i.e. me). Is there a similar American expression (e.g. "error 16" as in inches) ?

I mistakenly didn't change all three setting simultaneously, i.e. data path+public key+private key, yielding the ugly errors mentioned. My mistake entirely.

Yesterday I was again offline, and remembered to change all three settings, and everything worked just fine.

Sorry for stirring up some mud here 😒 😓


It was an "error 40" (as in 40 cm from the screen, i.e. me). Is there a similar American expression (e.g. "error 16" as in inches) ?

I mistakenly didn't change all three setting simultaneously, i.e. data path+public key+private key, yielding the ugly errors mentioned. My mistake entirely.

Yesterday I was again offline, and remembered to change all three settings, and everything worked just fine.

Sorry for stirring up some mud here 😒 😓

No worries! At the very least it's an interesting use case that somebody else might benefit from. Glad to hear you got it sorted out.


It was an "error 40" (as in 40 cm from the screen, i.e. me). Is there a similar American expression (e.g. "error 16" as in inches) ?

I mistakenly didn't change all three setting simultaneously, i.e. data path+public key+private key, yielding the ugly errors mentioned. My mistake entirely.

Yesterday I was again offline, and remembered to change all three settings, and everything worked just fine.

Sorry for stirring up some mud here 😒 😓

There's the 1D-10T error, but don't think its applicable in this situation, glad to hear you got it sorted :)


Reply