-
Notifications
You must be signed in to change notification settings - Fork 826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System exception: cannot lock named mutex (abadoned): ExmanProcessMutex #298
Comments
Which version of ExManCmd are you running? And when does this happen? When using ExManCmd to sign or to install...? |
Hi Erin! And it already happens doing a simple /list all |
@ErinFinnegan any updates on this? or any idea where to reach out..? I already posted in the community, without success so far... |
I'm still asking around about this... Did this happen to you using previous versions of ExManCmd, or is this a new problem with 7.10? (If you're a new user of ExManCmd, it's understandable.) Also, how might we reproduce this error internally? |
I think it's a very specific error that happened on my machine (windows on a mac, using Bootcamp). I'm using ExManCmd since years, and never happened to me before. Unfortunately, we couldn't reproduce it on any other machine. |
Hi! If you're still having this issue, can you share your log files? Here's how to get them:
If you don't want to share them here, you can email them to me at finnegan (at) adobe.com. I think one of my coworkers said he faced something like this, but it went away after he re-imaged the machine... but I recognize that is a very undesirable solution! |
Hi Erin! If nothing helps, I'll re-install Windows when I can. Best regards, Ah, the zipped file is much smaller. I'll add it although I've send the email already... |
Thanks, Stefan! A new ExManCmd release will come out in October at the very least, and might be in prerelease sooner. ExtensionManagerCC has been deprecated for some time now. I know it's still possible to install and open it, but I'm not surprised if it doesn't open... |
Thanks for the update. |
Hi @StefanRiedmann, ExManCmd was once part of the Extension Manager, and that just happens to be the path where the database file lives... |
After lots of mails and help from @ErinFinnegan and the team, we found the solution. Simply delete the folder C:\ProgramData\Adobe\Extension Manager CC I just tried it on Windows - because that's where I had the problem. Be aware that the 'ProgramData' folder is invisible by default. So you should make it visible in the explorer... Thanks again for the help! |
This is happening to me when running any exmancmd. I already uninstalled all Adobe applications, including Creative Cloud Desktop, and re-installed it. Still the same issue.
Windows 10 Enterprise, version 10.0.17763
The text was updated successfully, but these errors were encountered: