On a multi-node web farm behind a load balancer, with affinity set to NONE, http requests can end up switching between nodes at any time. If this happens during module install or enable time, the Orchard run time will throw an error. Perhaps this is due to Orchard being dependent on Session data for the user?
The standard way of dealing with this is to install the module on a dev box and then deploy. The part that needs to be checked here is the enabling part.
morrisonbrett created: https://orchard.codeplex.com/workitem/18260
On a multi-node web farm behind a load balancer, with affinity set to NONE, http requests can end up switching between nodes at any time. If this happens during module install or enable time, the Orchard run time will throw an error. Perhaps this is due to Orchard being dependent on Session data for the user?