bad variant access

Hi @perry​ ,

Are you able to try the latest version of FME 2021.1.0.1?

There was a known issue where a "bad variant access" error was produced and has been fixed in the latest release.

- Andrea

I thought I had the latest version installed (2021.1.0.0). I did not know there was an issue. Sadly I have more issues with other transformers working fine with fme 2020 and now fail. I will ask to install FME 2021.1.0.1.

Hi @andreaatsafe​  Is this issue solved? I am running against it with a clients FME Server (build 21607) where the workspace uses an SDE connection. This workspace used to work but does not anymore.

With te latest version 1.1 there are no problems or strange issues.

Thanks for responding, which build do you mean with 1.1? (the build I am using is also 1.1)

build 21619. used on server and desktop.

all transformers updated to latest version and system parameter: continue process.

packages renewed (ie Emailer).

I see thx again probably have to upgrade server....😡 Would anybody from Safe mind confirming that this is the only option? @mark2atsafe​ @jennaatsafe​ 

Hi @itay​ ,

I apologize for the inconvenience this may have caused but this is a known issue that was first noticed with the first release of FME 2021.1 build 21607.

The only way to work around this issue is to upgrade to the FME 2021.1.0.1 build 21614 or newer. For some more details, please see the known issues page under the id: FMEENGINE-70052.

- Andrea

Hi @andreaatsafe​ ,

Thanks for getting back to me on the issue. Upgrade it is!

Cheers,

Itay

Is it normal that this issue is suddely happening on my FME Server? It is the build 21607, but the process has been running without issue until yesterday.

Hi @oscard 

Did anything change in regards to the workspaces (updated/republished) or anything else?  

If nothing changed, I honestly don’t know why it would have been working and then suddenly stop.  Unfortunately, the only workaround is to upgrade to a newer version.  

Hi.

The only change has been executing the process in an Automation, but it run perfectly for a week or so before the error appeared. We will upgrade to a newer version in a couple of weeks. Thanks!