I have been trying out VisualCron 6.1.8 for a few days now. I am having problems executing Powershell tasks that use the SQL Server 2008 R2 snapins. I am pretty sure this is related to VisualCron requiring and using the .Net 4 framework (which, by the way, would be really nice to know beforehand--the system requirements documentation really needs to be updated to reflect this).
The problem is that when running a script that loads the snapins from a Powershell task, the task fails with the message:
Exception in Task: Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information. Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.
If I run the same script from an Execute task with "powershell" as the command the script executes properly without error if the "Run Task as" is run under the same credentials used in the Powershell task and it is set to "Run with API code".
If I run the Execute task as "Managed Code" I get a "non zero exit code" error.
After scouring the forums what little information I could find seems to indicate that the API is still using the .Net 2 framework while VisualCron itself now uses the .Net 4 framework.
Can you please let me know how to fix this so that I can actually run the Powershell task? While running Powershell via the Execute task is a valid workaround, my concern is if and when the API code is recompiled to use .Net 4 this workaround will no longer be valid.
VisualCron is installed on a Windows 7 Professional workstation. The Powershell script lives and is executed on the same machine.
Thanks.