Skip to main content
Solved

Connection with SDE File and OS authentification not working in FME Form 2026.2

  • August 5, 2026
  • 1 reply
  • 43 views
felix.pekarek
Contributor
Forum|alt.badge.img+2

Hello 😊

I recently updated FME Form to version 2026.2 and started experiencing an issue when connecting to an Enterprise Geodatabase using an SDE connection file configured for Operating System Authentication.

FME returns the following error:

"Failed to connect to Enterprise Geodatabase using connection file 'path_to_the_sde_file' due to missing credentials. A connection requires either Windows Authentication or both a user name and a password."

The SDE connection itself appears to be valid. If I open the same .sde-file in ArcGIS Pro, it connects successfully and shows the correct authentication type in the connection properties.

This workflow worked without any issues in previous FME versions and only started failing after upgrading to FME Form 2026.2.

Has anyone encountered this problem before? Is this a known issue in 2026.2, or is there a workaround available?

Any help would be greatly appreciated.

Best answer by crystalatsafe

Hi ​@felix.pekarek 

I'm sorry for the inconvenience! This is a known issue with 2026.2 (internal reference: FMEENGINE-98712). This fix is scheduled for the 2026.2.1 release. I will let you know once this version is available.

In the meantime, there is a workaround.

You could enable Override Credentials, and type anything in the username field, and the connection should work.

You could also: 

  1. Create a new SDE connection file 
  2. In Authentication, set SQL Server Authentication 
  3. Add your Windows Username/Password 

    1 reply

    crystalatsafe
    Safer
    Forum|alt.badge.img+30
    • crystalatsafeSafer
    • Safer
    • Best Answer
    • August 6, 2026

    Hi ​@felix.pekarek 

    I'm sorry for the inconvenience! This is a known issue with 2026.2 (internal reference: FMEENGINE-98712). This fix is scheduled for the 2026.2.1 release. I will let you know once this version is available.

    In the meantime, there is a workaround.

    You could enable Override Credentials, and type anything in the username field, and the connection should work.

    You could also: 

    1. Create a new SDE connection file 
    2. In Authentication, set SQL Server Authentication 
    3. Add your Windows Username/Password 

      Community Stats

      32,778
      Posts
      124,274
      Replies
      41,324
      Members
      Terms & ConditionsAccessibility statement
      A product of
      Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.