Hi VisualCron,
I've got a pretty simple situation but it's got me stuck.

I've two identical servers running VC 6.0.3 - Windows Server 2003 R2 machines.
I'm attempting to run a Powershell task, and on Server 1 everything works beautifully. But on Server 2, I can click Run Job or Run Task, and the Job switches to a "Running" status but the Powershell task never starts. (The 1 Powershell task is the only one in the job, right now).

I stripped out my Powershell code so that the only thing left was a simple test
Set-Content D:\temp\test.txt "this is a test"
and still the same result. I also tried running the VC task as my own credentials, which are an admin on the machine, as well as made sure Full Control was set on the folders, thinking at first there was an issue on the machine.

Anyone have any ideas on what could be wrong?

Powershell isn't native since it's 2003 R2, and it's not overly complex code - it could be done in a batch file if needed - but I'd prefer to keep it in Powershell and stored in VC.

Thanks!!

I think it starts but hangs for some reason. If you look in the log file log_serverDATE.txt - do you see any errors?

---

8/13/2014 8:42:31 PM Err Error in JobProcess (Run.TaskRunQueue), ex: An error occurred when loading the system Windows PowerShell snap-ins. Please contact Microsoft Support Services.

So I assume this isn't a VC issue?...

8/13/2014 8:42:31 PM Err Error in JobProcess (Run.TaskRunQueue), ex: An error occurred when loading the system Windows PowerShell snap-ins. Please contact Microsoft Support Services.

So I assume this isn't a VC issue?...

It sounds like a reference is missing in the Powershell script or a snap in is not installed on this computer.

---

Gotcha.
Off to my infrastructure team it goes.

Thanks Henrik.