Skip to main content
Solved

Scheduling tasks with AD authentication

  • January 26, 2016
  • 3 replies
  • 25 views
G
Forum|alt.badge.img

Hi

We have a problem running scheduled tasks when we activate AD-authentication on our FME Server 2015. We get the following message in the log:

MEServerJobSubmitter(ServerJobSubmissionFactory): Could not initialize connection to server "localhost". FME Server error: `Authentication failed: Failed to bind to Active Directory with the given username and password.'

Anyone got this to work ?

Kind regards

Guha,

Stockholm Water

Best answer by mark2atsafe

Hallå Guha

I've asked our Server team but I think this is something you should file with our support team (safe.com/support) or the support team of your local reseller.

Looking in the documentation, I did find something that might help diagnose the problem:

  • Ensure that SECURITY_DEBUG=true is set in the fmeCommonConfig.txt. This configuration parameter is located under the 'Security Management' heading. With this debugging flag enabled, all interactions with Active Directory are logged.
  • Look in the fmeServer_* log files for messages with '(Active Directory)' or '(Single Sign-On)'. These files are located in <FMEServerDir>/Logs.

This might provide more clues as to what the problem is.

Sorry I can't be more help. But let us know what you find if you try this.

Regards

Mark

Safe Software Inc.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

mark2atsafe
Safer
Forum|alt.badge.img+57
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • Best Answer
  • January 26, 2016

Hallå Guha

I've asked our Server team but I think this is something you should file with our support team (safe.com/support) or the support team of your local reseller.

Looking in the documentation, I did find something that might help diagnose the problem:

  • Ensure that SECURITY_DEBUG=true is set in the fmeCommonConfig.txt. This configuration parameter is located under the 'Security Management' heading. With this debugging flag enabled, all interactions with Active Directory are logged.
  • Look in the fmeServer_* log files for messages with '(Active Directory)' or '(Single Sign-On)'. These files are located in <FMEServerDir>/Logs.

This might provide more clues as to what the problem is.

Sorry I can't be more help. But let us know what you find if you try this.

Regards

Mark

Safe Software Inc.

FME Evangelist to the Rich and Famous!!
mark2atsafe
Safer
Forum|alt.badge.img+57
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • January 26, 2016

Hallå Guha

I've asked our Server team but I think this is something you should file with our support team (safe.com/support) or the support team of your local reseller.

Looking in the documentation, I did find something that might help diagnose the problem:

  • Ensure that SECURITY_DEBUG=true is set in the fmeCommonConfig.txt. This configuration parameter is located under the 'Security Management' heading. With this debugging flag enabled, all interactions with Active Directory are logged.
  • Look in the fmeServer_* log files for messages with '(Active Directory)' or '(Single Sign-On)'. These files are located in <FMEServerDir>/Logs.

This might provide more clues as to what the problem is.

Sorry I can't be more help. But let us know what you find if you try this.

Regards

Mark

Safe Software Inc.

I'm told it should work. It may just be the password in the FMEServerJobSubmitter.

FME Evangelist to the Rich and Famous!!
helmoet
Forum|alt.badge.img+8
  • helmoet
  • 195 replies
  • August 22, 2016
Hi, I sort of encounter the same problem, which I worked around using HTTPCaller and a REST call to JobSubmit a workspace on FMEServer. This works fine, however, if I try to Trigger a notification using the HTTPCaller, I get the same Error (401, Authentication failed: Failed to bind to Active Directory"). I generate a token first before I submit the HTTP request.

Community Stats

32,100
Posts
121,893
Replies
39,744
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility 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.