FME From 2024.2.1 failed to connect to FME Flow 2024.2.1

Hi ​@fei2000,

This error may be related to permission issues and more information is required to further investigate the issue. I recommend submitting a ticket to the FME support team and we are happy to help you there. 

There are a few questions we would like to ask to help us understand the issue better. 

• What is the authentication method you use?
• What is the build number of FME Form?
• Is it a new install with the migration from an older version? If so, did it work before?

There are some changes to connection storage in FME Form 2024. Please check this article for details and let us know if you are using private or public connection. https://support.safe.com/hc/en-us/articles/25407756230669-Changes-to-Connection-Storage-in-FME-Form-2024

I hope that helps.

Skyler

Thanks Skyler, as I am really new to FME Flow in our agency, I don’t know how to raise ticket to FME support team. Is that via our FME retailer or directly sent to FME?

Regarding to your questions:

• I am using admin’s username password to authenticate FME Flow connection in FME Form. As you could see the logs in previous post, it showed successful connection but failed in the following client registration step.
• The FME Form is FME(R) 2024.2.1.0 (20241202 - Build 24801 - WIN64) which matching the FME Flow’s version and build (FME Flow 2024.2.1 Build 24801 - win64)
• No FME Flow upgraded and it works 2 months ago without any change on the FME Flow. We just found out the issue recently.
• As we just new to setup the FME Flow, so no connection items existing at the moment.

And we had 2 FME Flow environments, one for non-prod and one for prod with same build. The weird thing is we could connect to the non-prod without issue but failed in prod environment.

Furthermore, after reviewing the xxxxx_restV4.log from FME Flow web site, I could see following error messages:

• Mon-28-Apr-2025 01:27:45.065 AM   ERROR    https-jsse-nio-443-exec-11   PreparedStatementCallback; bad SQL grammar [SELECT reg_id, machine_code, type, build, platform, last_updated, last_updated_user FROM fme_client_reg WHERE reg_id = ?]; nested exception is org.postgresql.util.PSQLException: ERROR: relation "fme_client_reg" does not exist

And I also compared the difference in our Non-Prod a d Prod FME Flow:

• Non-Prod is Express Installation with local PostgreSQL
  • “fme_client_reg” table found in fmeflow database via pgAdmin
• Prod is Distributed Installation with AWS PostgreSQL RDS
  • “fme_client_reg” table NOT found in fmeflow database via pgAdmin

But I could not find “fme_client_reg” table in postgresql_createSchema.sql file which used to create fmeflow database in separated PostgreSQL db.

I just tried following command and manually create “fme_client_reg” table in our production AWS PostgreSQL RDS. Then I could connect to FME Flow from FME Form without error. But I have no idea why this table was not created or was deleted by some unknown process.

CREATE TABLE IF NOT EXISTS public.fme_client_reg
(
    reg_id uuid NOT NULL,
    machine_code character varying(255) COLLATE pg_catalog."default" NOT NULL,
    type character varying(255) COLLATE pg_catalog."default" NOT NULL,
    build character varying(255) COLLATE pg_catalog."default" NOT NULL,
    platform character varying(255) COLLATE pg_catalog."default" NOT NULL,
    last_updated timestamp without time zone NOT NULL,
    last_updated_user character varying(255) COLLATE pg_catalog."default",
    CONSTRAINT fme_client_reg_pkey PRIMARY KEY (reg_id)
)

ALTER TABLE IF EXISTS public.fme_client_reg
    OWNER to fmeflow;

Hi ​@fei2000,

Thanks for the information and update. Glad to hear you are able to connect to Flow from Form now. 

If you would like to raise an issue in the future, please feel free to contact the FME partner or FME support team directly depending on how you purchased FME. Please choose “submit ticket” option using this link to submit a support ticket. https://support.safe.com/hc/en-us/p/Support

Skyler