This has happened to me on some returns when I enter a date prior to requesting the esignature from the client. The solution is to leave the signature date blank in ProConnect, when sending out the esignature request then fill in the date they esigned it in ProConnect prior to efiling the return.