Entourage refuses correct password after incorrect one is entered

M

Mike

Hi All,

Entourage 11.3.3 061214, we see this error consistently.

When you don't have a password entered in the account settings, it
will ask you each time you check mail. If you launch Entourage, and
enter the wrong password, it will never accept the correct password
until you login / logout. Killing the db daemon doesn't work.

Anyone see this?
 
D

Diane Ross

Entourage 11.3.3 061214, we see this error consistently.

When you don't have a password entered in the account settings, it
will ask you each time you check mail. If you launch Entourage, and
enter the wrong password, it will never accept the correct password
until you login / logout. Killing the db daemon doesn't work.

Anyone see this?
Click to expand...

No. I've seen problems where the password gets corrupted and you get error
messages. Running Keychain FirstAid or deleting the account and re-entering
it fixes that.

You can correct password errors in the Apple Keychain. Deleting an account
and re-entering the info also works.

--
Diane Ross, Microsoft Mac MVP
Entourage Help Page
<http://www.entourage.mvps.org/>
One of the top five MS Entourage resources listed on the Entourage Blog.
<http://blogs.msdn.com/entourage/>
 
M

Mike

yea we deleted the keychain entry, rebooted, and same behavior.

the AD is just saying it's a bad password...

Thanks for the reply,

-Mike
 
D

Diane Ross

yea we deleted the keychain entry, rebooted, and same behavior.

the AD is just saying it's a bad password...
Click to expand...

It's very possibly a sign of early database corruption. Not a usual sign,
but worth exploring.

Test in a new Identity to see if the account works there. If yes, then it's
indicative of your current database being corrupted.

Be sure to make backups frequently.

--
Diane Ross, Microsoft Mac MVP
Entourage Help Page
<http://www.entourage.mvps.org/>
One of the top five MS Entourage resources listed on the Entourage Blog.
<http://blogs.msdn.com/entourage/>
 
M

Mike

Thanks again Diane,

if its a corruption issue, then we have found a way to corrupt it, as
the problem is reproducable across machines, accounts, users, etc.

-Mike
 
M

Mike

here is the error from the AD:

"
Description:
The SAM database was unable to lockout the account of user due to a
resource error, such as a hard disk write failure (the specific error
code is in the error data) . Accounts are locked after a certain
number of bad passwords are provided so please consider resetting the
password of the account mentioned above.
"

turns out it was not just a bad password error, as I was led to
believe. My AD admin says "The database says it is a HD write falure
but I am sure that is not the case. It has something to do with how
many login attempts happen in a give time period."

just putting this out there :)
 
D

Diane Ross

if its a corruption issue, then we have found a way to corrupt it, as
the problem is reproducable across machines, accounts, users, etc.
Click to expand...

Then it something else. I would look to your next message where you mention
SAM as the culprit for the problem.
here is the error from the AD:

"
Description:
The SAM database was unable to lockout the account of user due to a
resource error, such as a hard disk write failure (the specific error
code is in the error data) . Accounts are locked after a certain
number of bad passwords are provided so please consider resetting the
password of the account mentioned above.
"

turns out it was not just a bad password error, as I was led to
believe. My AD admin says "The database says it is a HD write falure
but I am sure that is not the case. It has something to do with how
many login attempts happen in a give time period."

just putting this out there :)
Click to expand...

Can you test without SAM (I'm assuming this is virus software) disabled?

In addition, exclude the Microsoft User Data folder from virus scans. Users
have reported their entire Microsoft User Data folder was hidden when a
virus was found. The virus were Windows attachments and would not affect
your mac as an attachment.

There are no known Mac virus AFAIK.

--
Diane Ross, Microsoft Mac MVP
Entourage Help Page
<http://www.entourage.mvps.org/>
One of the top five MS Entourage resources listed on the Entourage Blog.
<http://blogs.msdn.com/entourage/>
 
W

William Smith

Mike said:
here is the error from the AD:

"
Description:
The SAM database was unable to lockout the account of user due to a
resource error, such as a hard disk write failure (the specific error
code is in the error data) . Accounts are locked after a certain
number of bad passwords are provided so please consider resetting the
password of the account mentioned above.
"

turns out it was not just a bad password error, as I was led to
believe. My AD admin says "The database says it is a HD write falure
but I am sure that is not the case. It has something to do with how
many login attempts happen in a give time period."

just putting this out there :)
Click to expand...

The Windows Server logs can't report hard drive failures for your Mac
clients. It must be referring to a failing hard drive on your server and
the account of the user is being affected. Check for failing hardware on
your server. This would also explain why you're seeing this from machine
to machine and user to user. The SAM database is having problems.

Hope this helps! bill
 
M

Mike

Thanks William,

My AD admin insists it is not an HD issue, and I'm going to believe
him.

I will probably escalate this to a Premier case (as we have for
Entourage problems in the past, the outcome invarialbly has been MS
agreeing it is a bug and tells us they will get back to us ....)
 
T

tylerjp

Thanks William,

My AD admin insists it is not an HD issue, and I'm going to believe
him.

I will probably escalate this to a Premier case (as we have forEntourageproblems in the past, the outcome invarialbly has been MS
agreeing it is a bug and tells us they will get back to us ....)


Hello,

I have been having this problem myself, and it was not an Entourage or
Active Directory issue. It was with my Mac. I posted a solution on my
page below which may work for you. Let me know how it turns out.

http://techsynopsis.typepad.com/techsynopsis/2007/03/solution_keep_o.html
Click to expand...
 
Top