Introduction
This article walks through some troubleshooting steps for working with Remote Engines in Snowpark. For full details on how to do this, see Getting Started with FME Remote Engines Service in Snowflake and Authoring for Snowflake Remote Engines.
Troubleshooting
Can’t Register Remote Engines
Example 1: Error 404 Not Found
The user must be assigned the correct role for this step to work.
GRANT APPLICATION ROLE FME_REMOTE_ENGINES_SERVICE_2025_1.APP_USER to ROLE FME_APP_ROLE.
This role, FME_APP_ROLE, is then assigned to the service user being configured to access the Remote Engine Service.
The above grants will allow the FME Flow Core environment to connect to the Remote Engines Service and submit jobs.
Example 2: Error 404 Not Found
Probable causes are related to the URLs used to register the Remote Engines Service. Carefully review the URLs and the Account Name value used in Part 4, Step 3 in Getting Started with FME Remote Engines Service in Snowflake. The Account Name should be contained within the URL provided by the Snowflake App when you launched the FME Remote Engines Service App in Part 3: Launching Container.
Illegal Argument Exception: Illegal base64 character
This is likely caused by the private key requiring a passphrase or by another issue related to decrypting it. Review how the public and private keys were created, ensuring that you followed the instructions in the Section called Requirements and Prerequisites, bullet 7.
Invalid Credentials
This error could be caused by an incorrect username and password for the connection to the Snowflake Account hosting the FME Remote Engines Service, as specified in the Snowflake Authentication panel in Part 5, step 5.
You may also encounter this error if you attempt to reuse an existing Remote Engines Service configuration with a new container instance. Please remove the configuration from FME Flow and recreate it from scratch. When creating a new configuration, several background configuration actions are set during the establishment of a new connection. When editing an existing connection, the same events do not run, and thus, the edited configuration will fail to connect to the new container.
Remote Job Submission Failed
When submitting a job to the Remote Engines Service, the 207 response is received, accompanied by the ‘can’t find key to decrypt’ message. Please remove the Remote Engines Service configuration from the FME Flow Core environment and recreate it.
Failed to exchange JWT for OAuth token
Make sure that everything in the Snowflake Authentication section is filled out accurately. In particular, the Endpoint field should not include https:// at the start and shouldn’t end with a slash. Sample Endpoint URL: abcde-mycompany-az.snowflakecomputing.app
Remote Engine Job Failed: “Role '<Role Name>' specified in the connect string is not granted to this user.”
Make sure the Role parameter of your Snowflake database connection is empty. The Snowpark Database Connection relies on grants given directly to the FME Remote Engine Service Application, as discussed in Part 8.
Remote Engine Job Failed: “Connection established with no current schema.”
If the job fails with an error like this when trying to access Snowflake data:
Connection established with no current schema. Make sure that the schema 'SCHEMANAME' specified in the connection settings exists and is accessible by the user
Then make sure you have granted schema permissions to the Remote Engines application. See Part 7.
I’ve changed my Snowflake database connection, but old values are still being used in the job when run on Snowflake remote engines.
Reset the Snowflake Remote Engines Service cache. This is done in the FME Flow instance with which you registered the Remote Engines Service. Please see the Administering Remote Engines Services Documentation.