Skip to main content
Participant
September 5, 2024
Question

Acrobat causing Active Directory User Lockouts

  • September 5, 2024
  • 1 reply
  • 1312 views

Hello,
We are currently facing an issue where Adobe Acrobat v24.003.20054 with an install date of 27/08/2024 is continously causing Active Directory user accounts to be locked out. 

 

AdobeCollabSync.exe is contiously causing Application Errors with the exception code 0xc0000409. Every error coincides with the bad password request being made against our Domain Controllers. When the AdobeCollabSync.exe process is stopped, the bad password requests stop. When it is resumed, the requests restart. There are no credentials configured in the Windows credential manager, the users are not signed into Acrobat, we have no form of SSO/LDAP/Any Authentication for Adobe Acrobat. 


We currently have 350+ machines on this Acrobat version, but this is only happening on around 5% of machines. 

 

Below is the full application error:
Event 1000, Application Error
Faulting application name: AdobeCollabSync.exe, version 24.3.20054.0, time stamp: 0x66c82c26
Faulting module name: AdobeCollabSync.exe, version 24.3.20054.0, time stamp: 0x66c82c26
Exception code: 0xc0000409
Fault offset: 0x00000000004d0d61
Faulting process ID: 0xb90


Thank you. 

This topic has been closed for replies.

1 reply

Participant
October 14, 2024

Hello,

 

We're having a similar issue with a few of our users, and very similar numbers as well. Did you find any resolution to this other than uninstalling Acrobat?

 

Thanks,

Tom

SIL1969Author
Participant
October 14, 2024

Hi Tom,


We have been unsuccesful in finding a resolution for this. The issue still crops up now and again but we have resorted to just uninstalling Adobe Reader and using Chrome/Edge to view PDFs. Please do let us know if you get any further!

Thanks

Participant
October 14, 2024

Hi,

 

That's unfortunate as that is what we have been doing thus far.

In my most recent case this morning I have attempted to repair acrobat to see if that resolves this (it hasn't locked the user out yet, touch wood, although it has only been an hour...).