Due to a bug in setting the FTP file date on locally downloaded files, we had to upgrade to the test build, version 8.2.8. It successfully fixed the problem (thank you!) however, now Active Directory logins don't seem to be working correctly. And it gets a little weird.
AD login works the first time. However, after logging out, then back in, a message pops up saying "Login failed, reason: User does not exist in Active Directory. Contact support." This, despite the fact that the credentials were unchanged from the successful connection a few seconds ago.
From there, if we log in using the non-AD account, and delete the AD user information, it "resets" the account. Again, the first time, the login is successful, but upon disconnecting and reconnecting, the login fails again. The debug log throws this exception:
CheckLogin->Unhandled error when quering for user: username, domain: domainADServer: domain.com, error: System.DirectoryServices.DirectoryServicesCOMException (0x8007052E): The user name or password is incorrect.
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_Name()
at VisualCronAPI.ActiveDirectoryAPI.GetUser(String strADServer, String strUserName, ADInfoClass& ADInfo, NetworkCredentialClass nc, String strCredentialId) in C:\sourcefiles\code\VisualCronAPI\APIPublic\apiActiveDirectory.vb:line 395
at AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA(LoginClass , String ) in C:\sourcefiles\code\VisualCronService\apiPermissions.vb:line 1323
Note: I edited out our domain name, however, the lack of a space after "
domain: domainADServer:" is not a typo. It is present in the debug log. I also replaced a string of characters in the bottom line with the character A, because I wasn't sure if the original value was possibly an obfuscated password.
Something we observed in troubleshooting is that the account that we're running the VisualCron service under is getting a password failure in Active Directory the
second time we try to log in. (But not the first.) The actual AD account for the user is
not getting a login failure, so it would appear that the failure is in the service account's inability to bind with the AD server.
As a final note, we have another VisualCron server running 8.2.7. It's using the same service account, and from what I can ascertain, it's using the same setup. It is working without a problem. Also, in the debug log, the same step shows "domain: domain" like above, but there
is a space after "domain."
Was something changed in 8.2.8 that may have broken this?
Thanks in advance!