I have an SSIS package that is failing when I call it from VisualCron, but it runs ok when I run it directly.

The error I get is:

The SSIS Execution failed
From, GetErrorValues (0)

I have rebooted the server it runs on - no help. I have some other VisualCron tasks that call different SSIS packages and those work. I did try having one of the VisualCron tasks that works call the SSIS package that is failing in this step, and that also failed. The odd thing is that this SSIS package does run when I double click it and run it with the "Execute Package Utility."

Any ideas why this is failing?

Thanks,
Chris

I've done a lot of debugging.

I've found that if I run just the SQL Tasks at the start of my package I get no errors, but once I enable the Data Flow tasks Visual Cron can no longer run it. Keep in mind, I have no problem running this package in debug mode or via the Execute Package Utility.

The Data Flow task used to throw a warning at run time, which didn't cause a problem, but I removed that just in case VisualCron was noticing it. That did not help.

How does VisualCron start the SSIS jobs? It it simply via the command line? Or do you have a .Net library that allows you to integrate to it? I'm asking because I am trying to figure out the next steps for debugging.

Thank you,
Chris

Thank you for your efforts. We are using interop against this class:

http://msdn.microsoft.co...dts.runtime.package.aspx 

If you go to members page you see that there are a lot of properties that can be set. Perhaps you need one of these properties to handle the error?

What settings do you use? Perhaps we can create a debug version for you.

---

Also, please look in the log as well as you only see the last error. Maybe a previous error in the log makes more sense.

---

Henrick,

I looked at the log. I didn't see anything in it... including I didn't even see my error:

The SSIS Execution failed
From, GetErrorValues (0)

I only see this error in the client in the Result & Output (stderr) fields. Isn't that odd?

When you ask what settings do I use - what do you mean? In VisualCron my settings are pretty plain vanilla:

Encoding utf-8
Execution Context: Background execution
Output: Store Standard Output = Yes
Store Standard Error = Yes

Credential: I tried both with a credential as me and with no credential.

Package located in file, with a path.

Thanks,
Chris

Please test this debug version:

http://neteject.com/VisualCron4SSIS.exe 

After executing, please look at the result and output column.

---

Thank you for this version... it shows you the errors returned by the SSIS package. Using this I was able to figure out what was causing my problem.

The answer is a bit anti-climatic, but I'll detail it here for others benefit. My SSIS package uses an ODBC connection - the ODBC connection was a User DSN, and when VisualCron calls the SSIS package it runs it under another user space, one without my User DSN. I was able to solve the problem by removing my User DSN and creating a System DSN.

I would have expected that I could have run my SSIS package with my credentials, thinking it would run in my user space, but, that did not solve the problem.

Also, after I installed this version I had some problems with it... first, it tried to tell me that my 45 day evaluation period had expired, but it has not yet. And second, we have more than one server with VisualCron (we're planning on getting a site license) and the two servers can not be managed by the same clients. Is there any reason I shouldn't upgrade my other server to this version? I have 4.9.11 on the other server, and this one is the new version, 4.9.18. Is 4.9.18 publically available? (Well, I guess it is now, via this forum.) It seems to include some pretty major changes.

Thank you for your time.

Chris

OK,

I am not sure that User DSN are loaded. I also have to check if the Credential is for the SQL connection for accessing files. But I think it generally better to store things like this under SYSTEM - if a user is deleted or similar.

About the trial problem. Please send your license.xml to support@visualcron (located in settings folder). We will investigate that and will send you back a trial extension code.

4.9.18 is publicly available.

---

Henrik,

Thank you.

I was unaware of the many recent releases. I'd love to see an rss feed/blog from you guys - even if it only contained the entries from your change log. There is an rss link on the home page, but, it doesn't work for me.

If not an rss feed, maybe email notifications for releases? Maybe I'll get that once I'm actually a paying customer :)

Thanks,
Chris

I am trying to run ssis package through Visualcron but its failing . While executing through sql server job its working fine. Please let me know what could be the issue and how can i debug it? It is giving no error in error output and log file just showing failed.