Event ID 529

	Home \| Site Map \| How To \| Windows Vista \| Case Studies \| Articles \| Forums \| Services \| Donations \| Careers \| About Us \| Contact Us\|

Event ID 529 - Logon Failure 2/2

Troubleshooting and Causes

Troubleshooting: 1. Check the Logon Type and the possible solutions: Windows Logon Types

2. Check the User or UserName to make sure it uses the correct password.

3. Check the Workstation Name and IP address to find out where the user logon.

Cases:

1. The client created a batch to map network drives with username and added the batch to the Schedulers. However, type the incorrect username.

2. The user just changed the administrator password. Since then, the Event Viewer received many Event ID 529 or 539.

3. The user mapped a network drive with persistent option. Then he changed the password.

4. The company has two domain networks with trust relationship. The password has been changed.

5. The client created RDC over VPN logging on automatically. However, the user password has been changed.

6. The IUSR_Name for IIS access was deleted by accident. Re-creatin the IUSR fixed the problem

7. Quoted from newsgroup: "When a password is changed on the machine hosting the IIS server, the changes do not always propagate through all of the web applications, especially if they are COM-based or ASP-classic applications. Running synciwam.vbs (located in my case in c:\Inetpub\AdminScripts\) may solve the problem".

8. This problem occurs if you use a local user account to run the program and the WMI scripts that you use in the program require Administrators group membership verification. If you use a local user account, the WMI scripts in the program use that local user account to perform the Administrators group membership verification. A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article.

9. When a user logs off, Windows XP or Windows Server 2003 re-reads the user record for updated information to optimize the next logon process. However, Windows ignores the fact that the user is from the local SAM database and instead tries to contact the domain if the computer is a member of a domain. A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article.