Update VCron to 11.1.1 Errors on remote Powershell Task - VisualCron

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.

Welcome Guest! To enable all features please Login or Register.

IT ServicDesk
Paid support Topic Starter

2024-03-25T13:15:09Z

Hello!
Since we update VCron to latest version 11.1.1 we having troubles on different Jobs with Remote Powershell

Receiving following messages

 Exception in Task: ExecuteProcess(D:\VisualCron\PowerShell\TaskPowerShell.exe 2154732)->Unhandled execution error: System.InvalidProgramException: Common Language Runtime detected an invalid program.
   at TaskPowerShell.PowerShellTaskClass.Run(ProcessPowerShellTaskInfoClass ti, StringBuilder& sbStandardOut, StringBuilder& sbStandardError, Boolean& bolResult)
   at imdRr04LtRtfi0IBAD.XGmcORYY3IAWat5qLo.Ecowj0hI2(String[]  )

also with SSH-Task
Receiving folling Error when we are trying to connect the SSH devices
Error 103
Exception in Task: SBSocketClient.EElSocketClientConnectionLostError: Connection lost due to error 96258
at VisualCronService.ProcessTaskSSHClass.Run()

Everything worked fine with version VisualCron11.0.0

Is a downgrade also possible to VisualCron11.0.0

Sponsor

Forum information

Wanna join the discussion?! Login to your Forum forum account or Register a new forum account

Robert Pressley
Paid support

2024-03-26T11:46:42Z

Having the same issue here.
Edit: Not quite the same issue, but may be related.
Exception: The 'connect-azuread' command was found in the module 'AzureAD', but the module could not be loaded. For more information, run 'Import-Module AzureAD'. ---> System.Management.Automation.CmdletInvocationException: The member 'FileList' in the module manifest is not valid: The path is not of a legal form.. Verify that a valid value is specified for this field in the 'C:\Users\datatel\Documents\WindowsPowerShell\Modules\AzureAD\2.0.2.182\AzureAD.psd1' file.

We've Imported the module and verified through Get-Module, so not sure what is causing this error.

Edited by user 2024-03-26T11:54:48Z | Reason: Not specified