The change to Local System in the Application pool resolves the issue. As this is a close environment, this will do. Some users have resolved the issue by using the Process.StartInfo.UserName, Process.StartInfo.Password and related properties to assign an account for the execution of the command. That seemed to have worked under certain environments but never versions seems to be more complicated to support that.