Hi,

We have a Powershell task on a job that has been working fine on all of our VC installations (dev, QA, etc). Today we imported the jobs to our regression environment and all of the powershell tasks began failing with this error:

Execute path: C:\Program Files (x86)\VisualCron\\TaskPowerShell.exe
Server->Executing Task process
Server->Executing Task process exited with exit code: -532462766

We have confirmed that our Powershell script is not getting called at all. Each instance of the VC server is running Powershell 4.0.-1.-1. From our searches we have found only that "-532462766" is a general error with not specifics as to what might be wrong. Is there a way in VisualCron to debug this? We are running Visual Cron 7.5.1.

Thanks,

Ben

What version of VisualCron did you migrate the jobs from, to the 7.5.1 server? 7.5.1 was a pretty major change from 7.2.x. x86 Execution mode, etc... for powershell.

Brian

Hey Brian,

Each VM instance is running the same version, 7.5.1, build 19717. The jobs were imported using VC's import feature. The other software on the server should be the same as well, for example PowerShell is the same version on each. I'd like to know more about how the PowerShellTask works and whether there is any additional logging to find.

So far the only clues we have are this output on the powershell task:

07:24:50: Server->Execute path: C:\Program Files (x86)\VisualCron\\TaskPowerShell.exe
07:24:50: Server->Executing Task process
07:24:51: Server->Executing Task process exited with exit code: -1073741502

This output on the powershell task's error output:

Exception in Task: Non zero exit code
Exception in Task: Non zero exit code

And these two errors on the Application event log:

Faulting application name: TaskPowerShell.exe, version: 1.0.0.0, time stamp: 0x5469c687
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532954fb
Exception code: 0xe0434352
Fault offset: 0x0000000000005bf8
Faulting process id: 0x1218
Faulting application start time: 0x01d1b287755f70f1
Faulting application path: C:\Program Files (x86)\VisualCron\TaskPowerShell.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: b32afbe8-1e7a-11e6-80c7-005056a17bf4
Faulting package full name:
Faulting package-relative application ID:

Application: TaskPowerShell.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.CommunicationObjectFaultedException
Stack:

Server stack trace:
at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(System.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
at VisualCron.ITaskService.ProcessLog(Int32, System.String, Boolean, System.String)
at cyUrojopSXmvOETD2i.hLMG7L8DnIx3s3NWAG.wSsqaE7VP(Boolean, System.String)
at TaskPowerShell.ProcessTaskService.CreateService(System.String)
at cyUrojopSXmvOETD2i.hLMG7L8DnIx3s3NWAG.wc2R3slHv(System.String[])

I appreciate any guidance,

Ben

If you clone the Job and replace script content with just:

write-output "hello world"

Does it fail then? This will tell if is a general problem or script specific.

---

After further investigation we resolved the issue by simply rebooting the machine. We aren't quite sure why that worked but suspect it had something to do with other changes made to the machine that I wasn't aware of at the time we were testing. I appreciate the prompt responses with suggestions.

We have modified this Task for 8.1.2. So if you encounter this again please test this beta or official when released: http://www.visualcron.co....aspx?g=posts&t=6721 

---