Account Lockout Examiner. Error Windows System Log
Posted 22 September 2014 - 10:29 PM
Two weeks ago install "NetWrix Account Lockout Examiner", the tool is working well but this day check the Windows System Event Log and discovered he had thousands of errors with follow description:
- DCOM got error "2147944122" from the computer PCName.Domain.com when attempting to activate the server:
- DCOM was unable to communicate with the computer PCName.Domain.com using any of the configured protocols.
Could someone please help me solve this problem.
thank you very much
Posted 23 September 2014 - 11:49 AM
With the information provided I'm not sure how this is linked to the Account Lockout Examiner but I can assume some things. The name of the PC is some PC in your environment as Account Lockout Examiner attempts to collect event logs from each workstation for examination purposes. So most likely this error occurs when an attempt is made to connect to the event logs of this workstation.
This may even be generated when a workstation is offline, DCOM ports are blocked or permissions to view event logs is not allowed. See the below:
Posted 23 September 2014 - 08:20 PM
There is a way to configure the "Account Lockout Examiner" to not attempt to examine each workstation.
What is happening is that the errors shown in the System Event log is not because someone run the option "Examine" The errors are automatically appearing.
Apparently the program attempts to examine the workstation automatically and if can not access in that workstation, the application logged this error.
We want the application notify us when an account is locked and examine the workstation only when needed and not automatically. Is it possible to configure the application to do this?
thank you very much
Posted 24 September 2014 - 05:00 PM
This is possible however it will make examinations not possible. Here is a KB article for how to do it: http://www.netwrix.com/kb/1531.
However, if the lockout is re-produceable and keeps happening you could set this registry key back temporarily.
Posted 24 September 2014 - 08:21 PM
Thank you very much. The problem was solved, we have no errors in the system event log.