😕 I think Visual Cron have as serious problem with SSIS ‘property expressions’. When you create for example a ‘dummy’ package to read one XML file, you get an error with ‘interactive services’.
To change the property of the ‘XML dataflow task’, for ex. DataSchema property is only possible at the upper level. In my case, a sequence container.
When you execute the package, DTEXEC interprets the expression before the package effectively is executing.
Within Visual Studio, DTEXECUI en SQL agent, this is no problem at all.
But when we’ve launch this package with Visual Cron,… the job just hangs for hours. To detect there is a problem, I’ve started the interactive service detection, and know I can see there is an error. Only the message is unreadable.
Removing the expression from SSIS task, becomes the package running fine.
The only thing is, we really needed the expressions to make the package dynamic.

Please investigate this issue.

Many thanks,

Ronny

Could you upload a sample that just works (but fail in VisualCron) that is as simple as possible and do not require any server configuration?

---

Zip file attached.
Read the readme for installation.

If you need any other information, just let me know.

thanks,

Ronny

any idea's yet? needed more info?

We have not forgotten you. This case has been place in a queue for testing and we will get back to you after testing. Hopefully we are able to do that tomorrow.

---

thanks for the response.Hopefully, we Hear You soon

Hi,

we did test this. We are using a wrapper of the DTS/SSIS libraries from MSSQL. It is not exact thing as DTExec. The problem is that this wrapper crashes internally for an unknown reason and that is not something we can do anything about as we cannot change that code part. We are dependent on the wrappers we get from Microsoft here.

An alternative would be to use DTExec in the background but that is not as efficient as this and take some time to implement.

I am moving this topic to Feature requests to see if we can do anything any workaround in the future. I am sorry if the answer was not what you wanted to hear right now.

---

Indeed, I was expecting another answer.
Any idea's yet for the work-arround ?
We're still hoping not to change every job to background executions...
Anyway, at this moment, thanks for the open communication.
Hope hear something quickly.

Regards,

Ronny

I think the quickest workaround would be to schedule DTExec.exe in the Execute Task. That would close the gap in any current limitations.

---

Hi Support,

We're executing the packages within the process task. And this work fine, but ...
when we do this with remote execute, it always fails with access violations.
Can you explain with special access is needed to execute a remote task?

thanks,

Ronny

Did you try switching between "With profile" and "Network credentials" option?

---

No, don't know it exists. Can you explain where I can change this. I couldn't find it in the remote execute task

thanks,
ronny

Sorry, I misread, I thought you were using the normal Execute Task - remotely. I am not sure what permissions DTExec requires. You could always install the Server part on the remote machine and schedule it from another machine.

---