We are having the same issues!

Hi @ShanaBaker 

Thank you for posting in the Community. We are currently researching the issue wit e signature. Here is a knowledge base that may or may not help with your specific situation:
How to use eSignature in ProSeries
The issue is specific to the OneClick feature (Authorization forms only) when used for a Married Filing Jointly (MFJ) combination that requires a spouse's signature and the 8879TA from is included in the e-signature request. A temporary solution is to use the regular request widget (Authorization forms & other documents) as an alternative to Authorization forms only. If this does not relate to your specific situation please contact ProSeries Support.

@ShanaBaker  My apologies! I misread your product and the above issue listed as affecting ProSeries. Here is a help article on using E-Signature with Lacerte and how to contact Lacerte Support. Let us know if you were able to resolve sending e signatures  after contacting us.

Thank you for sharing the article, however, we know how to use Lacerte E-Signature. We have used this product for over 20 years. This is a new issue and we are not the only experiencing the lag with requesting esignatures. I posted on social media and 2 other firms are having the same issue, mostly with newer computers. We have a case number open: 15153653918

As a troubleshooting step, can you unclick the option to send a PDF copy of the tax return with the e-signature? What may be taking time is Lacerte creating a PDF of the tax return. 

If that's the case, you could run the PDF fix tool and, as a temporary fix, send the e-signature without the tax return PDF.

Thank you for the suggestion.  I'm open to any right now.  I tried it and it did not help at all unfortunately.

Thank you for the idea.

We have run the pdf repair took kit. Interestingly, it would not run in the Tool Hub, so we had to initiate the PDF repair tool from inside Lacerte.

Next, we will try to do a component repair, but as with the PDF Repair Tool option, it is not running in the ToolHub. 

Jeez, I'm sorry that didn't help. If it is fritzing at that point, it's definitely something Lacerte should handle, not blaming your IT staff.

I am sorry. I read that too quickly. It is actually after that screen. We did test unchecking the copy of the tax return, but it did not make a difference. 

I spent 20 minutes on hold then a little over an hour on the phone with a rep named Chris.  He ran through everything he could think of.  He asked me to contact our IT department about the firewall on my computer.  IT did as he requested and it is still an issue.  He stated that he would call me back this morning.  I haven't heard from him yet, so no resolve to this issue yet. 

Yes, I was going to mention the firewall, but I was thinking of the one in your wiring closet. That's at least an easy thing to troubleshoot before contacting Intuit AGAIN.

Same here. Our IT guy completely disabled the Firewall and Antivirus and we still had the issues; again only on the new computers. 

If our IT guy disabled the firewall, would that be the same as "the one in your wiring closet"? Or should we test it after literally "unplugging" the firewall. The issue we have is that 3 computers are operating just fine in the current set up; firewall and all. We are only have issues with the Requesting E-signature lag with our 2 new computers. 

No, it is different. I'd disable the Windows Firewall to troubleshoot the issue on one of the machines having the issue.

https://support.microsoft.com/en-us/windows/firewall-and-network-protection-in-the-windows-security-...

I would not recommend doing anything to your other firewall without consulting someone. We would reach out to the firewall management company we use and work together to see if the issue is related to that.

You're lucky it's working, mine does not...

So frustrating. Our IT team spent a considerable amount of time on the phone with a Lacerte support representative. They were able to resolve the issue on my laptop by uninstalling OneNote, yes, OneNote, which is difficult to understand how it was related. Our IT team also confirmed that our firewalls were not causing the problem. I work through a remote server as well, and we followed the same steps there, but it did not resolve the eSignature issues.

That is wild.