This error keeps surfacing. Can we get a root cause so we can globally correct this? is is a Microsoft patch that breaks this or maybe a programming error?
Hi Brian--do you have a screencap of the error message? We will need more information about this issue....is it happening for everyone or just one user....what command are you executing, when the error comes up...can you reproduce this at will, or is it intermittent? This issue should be addressed in our support queue....please contact me at firstname.lastname@example.org or enter a service request at Service Request Manager .