Finally and with the help of SAS Technical Support, we found something. We first tried to schedule our SAS EG project with a VBS script and no powershell : the error was still there. Then we focused on the fact that our file SEGuide.exe.config contained redirected variables for temporary directories (http://support.sas.com/kb/62/237.html), but the project elements seemed to stay in the default TEMP directory. We modified the Windows environment variables (TEMP and TMP) for the user running the powershell script. After that, the project completed successfully and did not encounter conflict anymore. The conclusion is that the workaround in SAS Note 62237 works but since the SAS EG powershell API do not take into account the parameters in SEGuide.exe.config, you have to change the windows environment variables too.
... View more