The error goes on to complain about not being able to update the registry. Now I went back to the old server and I can see the registry key it is trying to access. On the new server, the registry key is not there so I assume it is trying to create it. The service account used to run eConnect is not only a domain admin account but is also a local admin account. I even went as far as setting the permission on the registry branch explicitiy to full control to this account. Has anyone successfully been able to send data through eConnect on a W2012 server? There were no issues installing eConnect we just cannot send any data through it.
↧