We have a particular application that needs to have the following in Visual Cron to execute.

It is scheduled as a Execute Task

Logged on User.
1) Foreground Execution
2) Tied to a Session

Failure
1) If it is tied to a session and the user is not signed on, it complete without executing the application
2) If the user is signed on and background execution then the you can see the application pull up on the task bar and it just hangs.

Success
If you run it as a session and the user is signed on, then the application runs.

Any Ideas?

1. is there any reason that you want it tied to a specific session. I think it only can produce problems in the end as session numbers tend to change
2. maybe you are using a Credential as well? When using foreground execution no Credential should be used - or maybe you are using wrong arguments for the application?

---

Excellent...

I think that the Foreground/Background understanding was the answer.

The combination of Foreground with credentials was the issue, when the credentials were removed then the service account setup under Visual Cron ran the application without issue.

However in background, if I remember correctly, we needed to specify the credientials in order to execute particular applications.

Thanks for your help.

Excellent...

I think that the Foreground/Background understanding was the answer.

The combination of Foreground with credentials was the issue, when the credentials were removed then the service account setup under Visual Cron ran the application without issue.

However in background, if I remember correctly, we needed to specify the credientials in order to execute particular applications.

Thanks for your help.

Yes, when running in background the default user is the one of the VisualCron service, the LocalSystem account. When running in the foreground you use the same user as you logged on as.

---