Welcome to EMC Consulting Blogs Sign in | Join | Help

SSIS Junkie

SSIS: Problems calling SSIS packages from Visual Studio

Over the past couple of days myself and a colleague, Tim Haines, have been grappling with what seemed like an surmountable problem at times. I say we...its been more Tim - he's done a great job in uncovering some inherent problem in Visual Studio (seemingly).

A bit of background. We are building some .net web services that consume and make available data as provided by SSIS packages. This means that the packages are executed from within .net. We were seeing a problem where this code would work on a given machine and then could be ported onto another machine, run in exactly the same way, and cause some inexplicable errors within the SSIS package. To make it even worse we saw examples of running code successfully, making some changes and then CTRL-Zing to get back to the original code - and that same code then failing. On the same machine!!! Bizarre.

Well after much trial and error Tim finally found the problem. It seems that the code would run successfully in Visual Studio until such time as you make an innocent change that causes a failure (e.g. We were passing parameters to the package on which we sometimes got the syntax wrong) and thereafter the package would never again get successfully executed - even by rolling back to the previous successful version of the code. We eventually learned that the only way to fix the problem was to simply shut down Visual Studio and start it up again. The code would then execute successfully again until such time an error occurs and thereafter the code would never work again until a shutdown of Visual Studio.

We certainly can't begin to explain why this should be the case but we are happy that we have uncovered the problem and, crucially, a solution. Perhaps Visual Studio somehow caches execution state, perhaps there's a bug in Visual Studio - who knows? But it works for us now and that's all that matters.

If you experience similar problems - please let me know!



Published Thursday, October 27, 2005 11:18 PM by jamie.thomson



David Russell said:

That "solution", if you can call it that, has been tried many times here; but more often than not, the package is just plan corrupt and sometimes we can delete the container and add a new one, other times it's just as easy to delete the solution, restart VS5, and start over with a new solution. We have given things until shortly after RTM to work and already have a team working on alternate solutions to SSIS. The software has truly been garbage so far. Everybody has nice things to say about it; but at some point, EVEN if it were to turn out to be "operator error", if the software won't work, can't be made to work, etc., it is NOT the tool of choice. And RTM was due two weeks prior to November 7th. That's next Monday and RTM is NOT here. My suspicion is that whatever comes out November 7th isn't going to be any good either.
October 31, 2005 7:01 PM

AJ said:

Hi Jamie,

you are not alone. i got the same issue. mine is even weired. it doesn't happen all the time. and sometimes it does.

because it's ASP.net sometimes when i do an IIS Reset it goes away. (you can't really do this in a production environment).

i get "cannot be written to the property. The expression was evaluated, but cannot be set on the property."

any idea how to get rid of it. i'm not sure if above is a solution. more of how it starts happening? please update this thread if you have a solution to fix the problem.


April 7, 2008 7:36 AM

Sudhakar said:

I am trying to call a fuzzy grouping task with some of the task setup values passed dynamically from visual studio 2003 since our reporting server is still on framework 1.2. Could you send me some solution for this atypical problem!

May 26, 2008 4:52 PM
New Comments to this post are disabled

This Blog


Powered by Community Server (Personal Edition), by Telligent Systems