2 Replies Latest reply on Feb 28, 2017 2:41 PM by llemieux

    SW Job Engine v2


      Has anyone encountered an issue where one of the polling processes is polling with an AD user account?  The service itself is set to start use a default sevice account.  However, if the service is enabled, and the polling process or NPM starts, it uses an AD user account as part of it's polling.  I've combed through all the settings and every instance of any defined credentials and am not finding anything.  My AAA server confirms the source of the failed login attempts as coming from our ORION server and I have confirmed that the SW Job Engine v2 has the association but that's as far as I've gotten.  I can't find that any user ID info has been defined anywhere in any of the custom properties or pollers.  Any ideas?  The issue is that the credentials are outdated so the process is locking out the account.