egp project problem with task scheduler

[mazinga76]

Hi all,

this is my first post.

I hope that someone can will help me 😊.

I created projects in 32 bit enterprise guide and I scheduled them in windows 10.

A few days ago I changed pc, switching to enterprise guide 7.15 64 bit always with windows 10.

I copied the projects folder in c: \ exactly as on the other pc, I re-imported the schematic tasks (which I had exported from the other pc). The problem is that now the tasks remain in the running state even if the project is finished and has successfully exported the files. I eliminated the old tasks, and from enterprise guide I created the new tasks (thinking of a problem between the 32 and 64 bit version) but the problem was not solved. Remaining in running, the instance of the next day is not started and therefore the project does not produce the files.

I hope I have explained well 🙄.

Anyone have any idea on how to fix 😚?
Thanks

[SASKiwi]

What version of EG did you have on your original computer? It couldn't have been any later than 7.15 as EG can't open projects created in later versions, only current or earlier versions. Is the behaviour of the tasks the same running them manually versus with scheduling?

I suggest you open a Tech Support track for this problem is going to require some diagnosing.

[mazinga76]

There is a method to view with which version the project was created?

[Sajid01]

Hello

When a user schedules a task in SAS EG, it creates a script EGScript.vbs and configures the Windows task scheduler to run this script. The script in turn runs the EG Project.
Here are some steps you can take to trouble shoot your issue.

1. The EG Project runs without error.

2.Schedule a test run of the project and see if the EGScript.vbs is still present on the task scheduler even aafter the proejct is done. In normal course once the project is over, WGScrip.vbs will not be present in the list of running processes.

3.Run the script manually on the command line. Check if there is an error.

4.If the above are all good and no error, then as a work around, you can force the program to stop after running for a specified time in the task scheduler.