Skip to main content
Question

FME Workbench Losing Connection Storage Access

  • November 18, 2025
  • 5 replies
  • 46 views

phoeffler
Contributor
Forum|alt.badge.img+7

We have FME Form/Workbench installed on some of our Azure Virtual Desktop (AVD) machines, and it works fine overall. There is this recurring issue where the Connection Storage access is lost between each session. This is disruptive, and not always apparent, which wastes time and effort troubleshooting. 

In 2025.1.2.0, navigating to Web Connections under FME Options shows this each time:

And navigating to the Workspace Defaults section yields:

My connection storage is a Shared Database, which I thought was part of the problem, but I have more recently learned that a colleague of mine is using the default Personal Database connection storage and is also having the same failure to decrypt data between AVD sessions.

I’ve searched around the Community and the web some, and am familiar with Changes to Connection Storage in FME Form 2024 – FME Support Center and the list of known issues, but was unable to find anything related to this. Has anyone else run into recurring connection decryption failures? I’m not certain if this would have happened in previous versions of Form or not, but it has not been an issue for local installs or in a different Citrix environment, that I’m aware of.

5 replies

hkingsbury
Celebrity
Forum|alt.badge.img+64
  • Celebrity
  • November 19, 2025

I suspect its partially due to the AVD not maintaining user data between sessions or a bad encryption key. I bleeive the encryption key for the shared database is based on machine randomness, with AVD you can be logged onto one of many machines.

Its probably a good idea to involve you IT team as they may be able to change settings on the AVD to help resolve this.


redgeographics
Celebrity
Forum|alt.badge.img+61

We’ve had a similar case a while ago where (personal) connection storage didn’t properly migrate between different virtual machines because of the encryption being hardware-specific. The workaround was to have each user create their own shared storage (and just not share it with anybody else). 


s.jager
Influencer
Forum|alt.badge.img+21
  • Influencer
  • November 19, 2025

We are having the same problem as well. For us using FME Flow as storage for Connections helped a bit: you only have to restore the FME Flow connection every morning. It’s why we’re going back to an ‘old-fashioned’ VM instead of an AVD…

What I find strange though is that the list of recent workspaces IS saved in between sessions. So I think there’s more to it than AVD not maintaining user data between sessions, I think part of it is as well where that user data is stored, or something like that.


phoeffler
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • November 19, 2025

Thanks for the responses! I did talk with IT today and have some additional information/thoughts on this.

In our AVD configuration, we’re all assigned specific, persistent VMs, but the profiles are stored separately and not kept 100% intact between sessions, but generally maintain. So, the “hardware” shouldn’t be contributing here, but it’s pretty clear that the user profile is. Conversely, in our previous Citrix environment, the VMs were pooled and profiles were managed similarly, but we didn’t have these problems. Which leads me to wonder if it’s a combination of a change at FME 2025.x and also our change in VDI.

My best guess at this point is that the exact place where FME is storing this in the user profile is no longer being retained in our AVD configuration, that FME 2025 changes where/how this is stored, or both.

Perhaps someone at Safe will be able to speak to this from a more informed position - I’ll report back any more that I can learn, and will test out using FME Flow for connection storage.


phoeffler
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • November 19, 2025

Based on [FME Form 2024.2.] Losing Database- and webconnection on new machines | Community, it seems like the Shared connection storage was working in AVD and OneDrive at 2024.x, but may be a wider problem at 2025.x. It may also come down to details in profile management with AVD/DVI environments.

I will still look at the FME Flow connection storage more closely, but we typically have to connect to Flow using a multi-step MFA process for each Form/Workbench window that we open. I’ll test further; it may be more or less work than reauthorizing the Shared connection store each AVD Windows session.