December 6, 2012 at 11:22 am
Ok... this might get lengthy... so please bare with me.
I have a DTSX package that has over 30 steps/containers, etc. I'm using Sequencing events, groups, etc. Everything up to now has been on the same server using the same connection. Now I have to pump the data from a table on the server I'm working on to a different server. I do this all the time. We have literally hundreds of packages that do this same thing.
We use the SQL Authentication with a UN/PW. Nothing special. I built the connection, and set everything up and kaboom, RED square on the screen. I've tried redoing all different aspects of it. Now here's where it gets weird. I created a new package on the same Solution, and created the same step from scratch and it works fine. I'm stumped.....
Could it be that I have tooooo much going on in this package? I dunno... I'm stumped, Boss is Stumped, or SSIS "expert" is stumped... dunno...
Please help, any suggestion, regardless of how dorky they might end up being, are still appreciated.....
Thanks again.
Crusty.
December 6, 2012 at 11:31 am
CptCrusty1 (12/6/2012)
Ok... this might get lengthy... so please bare with me.I have a DTSX package that has over 30 steps/containers, etc. I'm using Sequencing events, groups, etc. Everything up to now has been on the same server using the same connection. Now I have to pump the data from a table on the server I'm working on to a different server. I do this all the time. We have literally hundreds of packages that do this same thing.
We use the SQL Authentication with a UN/PW. Nothing special. I built the connection, and set everything up and kaboom, RED square on the screen. I've tried redoing all different aspects of it. Now here's where it gets weird. I created a new package on the same Solution, and created the same step from scratch and it works fine. I'm stumped.....
Could it be that I have tooooo much going on in this package? I dunno... I'm stumped, Boss is Stumped, or SSIS "expert" is stumped... dunno...
Please help, any suggestion, regardless of how dorky they might end up being, are still appreciated.....
Thanks again.
Crusty.
The SSIS meta data does sometimes get corrupted - and this may have happened here. I've had to do the delete/recreate thing several times in the past (thankfully not in the recent versions of SSIS though).
If you have a copy of the faulty package and want to dig deeper, try opening it up in your favourite XML editor and having a rummage.
December 6, 2012 at 11:38 am
I've had to do the delete/recreate thing several times in the past (thankfully not in the recent versions of SSIS though).
Can you elaborate on that a bit more?
Thanks
Crusty
December 6, 2012 at 11:43 am
CptCrusty1 (12/6/2012)
I've had to do the delete/recreate thing several times in the past (thankfully not in the recent versions of SSIS though).
Can you elaborate on that a bit more?
Thanks
Crusty
Sure. I've had times where package objects which were working fine but, when modified, inexplicably did not work as expected. I found that deleting and recreating such objects (with exactly the same settings/config) would fix the issue.
December 6, 2012 at 11:45 am
I guess I'm a little thick... If I delete the package, I'll have hours/days of work ahead of me to recreate the package. What's the work around so I don't have to do that? Sorry, I know.. I'm dense.
December 6, 2012 at 11:54 am
Ok... It's getting weird now. I created a seperate package in the job, then in the original job created an execute package container pointing to the new package and it runs fine...
WHAT IS GOING ON!!!!!!!
Arrrrguh.... someone shoot me.
Crusty
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply