This has been happening to us as well on 10.15.6. We're seeing this error after upgrading the extension, where nesessionmanager will refuse to load the new version. Killing nessessionmanager solves this problem, but it doesn't look like a good solution.
SnoopyT
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Seattle, WA, United States