Invalid Username / Password

[cadeitstaff]

My programming department started getting odd "Invalid Username / password" errors for no apparent reason.
I checked their accounts and everything appears to be fine, I am good on my licenses ... so I cannot figure out why this would just start happening out of the blue.

Any suggestions would be helpful.

I am running:
SourceGear Vault
Version 4.0.2.15802

Thanks,
Chris

[Beth]

Can you log in with the admin user name?

Do you use Active Directory logins for Vault, or do you have Vault logins and passwords that don't match the Windows logins?

Can you look in you Vault server log at C:\Windows\temp\sgvault\sgvault.log, scroll to the end, and see what error is being logged there?

[cadeitstaff]

Yes I can login with the main Admin account on the server though the "Admin Web Client".
Yes they all use Active Directory accounts, they have worked fine up until this morning. I checked the accounts and they are not locked out or anything of that sort through AD.
Looking into the Log file now:
This is the new common error as of late:
----3/5/2009 1:20:51 PM duryasz--chi-win-wkst17.cade.uic.edu(128.248.232.144)--SSL Disabled Login failed: FailInvalidPassword
Active Directory authorization for user USER@DOMAIN failed: The server is not operational.
Active Directory authorization for user USER@DOMAIN failed: Logon failure: unknown user name or bad password.

[Beth]

Could you look in the web.config that is located under vaultservice? By default that is at C:\inetpub\wwwroot. In there is a section for impersonation. It should list the user Vault is running under and the password. Try logging into a Windows machine with that login name and password. What I'm suspecting has happened is that the password isn't set to never change, and AD is either requesting a new password, or someone changed the password for that account. Check those avenues out first.

[cadeitstaff]

Still does not to appear to be the issue. The user that is being impersonated is fine with both being set to no expire and to no allow the user to change the password. I was able to successfully log into another machine with that username as well. Good thought though, had not gotten that far yet.

Anything else you can suggest?

[Beth]

Has anyone tried to change their password using the Vault Change Password function? Doing that instead of changing their Windows password as the password change method will sometimes break Active Directory logins.

Under the users, are they all still set to use Active Directory logins or was that changed to Vault logins?

In the same web.config file, towards the bottom where your SQL connect string is, does it list the same Active Directory user? If so, then try to login to your SQL Server Management Studio with that username using Windows authentication.

[cadeitstaff]

No one has attempted to change their password through the Vault Change password function that I am aware of. Wouldnt that just screw up one person and not everyone??
I checked the three people that I know are having problems settings and they were all set to "try all domains" under their user AD setup. I adjusted that to be just the one domain and it still didnt seem to work. As they are still claiming the same errors.

The connection string is a little different in that it doesnt show a username / password combination:
<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='true'; Server=SQLSERVERNAME; Database=DBNAME; Integrated Security='true'" />

But again nothing has been changed.

[cadeitstaff]

Currently have changed the immediate needs for people, I have set them to Vault connection .. but would perfer to get them back to the AD ASAP tomorrow.
And that worked.
Please let me know if you have any more idea's.

[Beth]

Send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread. I will want to see what you enter for a domain. Then I will want to know if the users are actually in that particular domain, or whether you are relying on trusts between another domain tree, child-domain, or a trusted domain in another forest, for authentication.

Also, are your users and your Vault server at the same site?

[Beth]

This was resolved offline. The user entered the FQDN into the server for the AD domain instead of just the server name, and then performed an iisreset.

HS: 215353