Essentials Workflows no longer work after upgrading Essentials 4.5.1 to 4.14.2

We are in the process of upgrading our Geocortex Essentials from version 4.5.1 to 4.14.2.  We have the new Geocortex Essentials 4.14.2 set up in new development and production environments that have not yet gone live pending the resolution of a few remaining issues.  In our current live production Geocortex Essentials 4.5.1 environment, our maps use several workflows to provide additional functionality for our users.  These workflows are working perfectly in the Geocortex Essentials 4.5.1 environment.

In our new Geocortex Essentials 4.14.2 environments, we have set up our new servers and sites.  The sites are essentially the same sites as are running in the live 4.5.1 environment, with necessary changes made for Essentials 4.14.2.  The sites are working as expected and all functionality is working except for the Essentials workflows, which we migrated from the 4.5.1 environment to the 4.14.2 environments.  When we migrated the workflows, the workflow files were checked and paths were updated for the new environments.  We believe that the migrated files are installed in the correct locations for the new environment.

But when we test these migrated workflows in our migrated maps in Geocortex Essentials 4.14.2, they fail with two different messages seen.  We have maps that allow public access, the workflows in these maps fail with this message:  

There was a workflow error running activity: Exception has been
thrown by the target of an invocation.
Unable to load specified workflow from instance store.
Unable to load workflow running instance data.
Padding is invalid and cannot be removed.

The Geocortex servers serving the public access maps are in a secure domain running behind a reverse proxy server.  The permissions on these public Geocortex maps allow Anonymous access.

The other workflow error seen is in our new maps which are restricted for access by our internal users only.  The Geocortex servers reside on an internal domain accessible by our internal users.  The Internal maps use Windows Authentication to access.  The workflow error seen on the new internal maps: 

There was a workflow error running activity: The current user cannot
access the desired resource. 

We have tried recycling the Geocortex Essentials App Pool, but this has not affected the error messages.  Any ideas?