It could be. Lacerte and ProSeries share that eSig component, and the underlying 3rd party component that it runs in. That 3rd party component is causing the issue referenced in the thread (which is also unfortunately impacting some Lacerte customers). It's conceivable it could also be causing this. I will investigate further.