This would mean the service account.
I'm not one to regurgitate AI responses, but Gemini surprisingly did a fair job on this one.
When configuring an Active Directory or AD/Hybrid User Source in Inductive Automation Ignition, hitting Error 49 with data 52e typically points to one of two main scenarios: [1]
Scenario 1: The Gateway cannot sync users/roles (Main Service Account Issue)
If you see this error repeatedly in the Ignition Gateway log console (wrapper.log), the Service Account Username or Password configured inside the User Source settings is wrong. [2, 3]
- The "Automatic Suffix" Trap: Go to your AD User Source settings in the Ignition Gateway, scroll to the bottom, and check Show Advanced Properties. Look for Automatic Suffix. If this is checked, Ignition automatically appends your domain to whatever username you typed. If you manually typed
username@domain.comand Automatic Suffix is on, Ignition sendsusername@domain.com@domain.com, causing a52eerror. [1] - Username Format: Try changing the main Gateway Service Account username format. Switch between standard
sAMAccountName,DOMAIN\username, or the full User Principal Name (username@domain.com). - Special Characters: If your service account password contains symbols like
&,<,>, or trailing spaces, Java/Ignition can sometimes struggle to escape them correctly. Try a temporary service password with just letters and numbers to see if it fixes the issue. [4, 5]
Scenario 2: A single operator/user cannot log into a Vision/Perspective Client
If the User Source syncs fine, but a specific user gets blocked when trying to log into an HMI screen or designer:
- Stale Credential Cache: It is remarkably common in Ignition for an operator to change their Windows password, but Ignition continues to throw a
52ebad password error even when they type the new one correctly. [6, 7] - The Fix: Have the user perform a formal domain password reset from a standard Windows workstation. Forcing a fresh password reset syncs the underlying Kerberos/AD state back up with the LDAP provider that Ignition is actively reading. [6, 7]
To help target the right setting, let me know:
- Is this happening when you try to Save/Manage the User Source in the Gateway web page, or when an operator tries to log into a client screen?
- What Ignition version are you running (e.g., v8.1)?
[1] https://forum.inductiveautomation.com
[2] https://forum.inductiveautomation.com
[3] https://industrialmonitordirect.com
[4] https://industrialmonitordirect.com
[5] https://www.manageengine.com