LOL...Yeah, Ivan is right, there were some structure changes in the last update of the security.  So that could be what is getting in the way, but generally you get a different error.  But that is definitely a possibility.

Yes, if I'm not mistaken the Security tables had a new field or something, so if you had the Security tables already in Deployment Data, that could be it. As Trent said, deleting the packages and generating them back again should do it. This boy is learning a lot...

I'm just deploying permissions and roles (and associated links).



So, if SF made changes then yes. I haven't.



I about to do a meeting, then finish a bug fix...so I'll get back to this tomorrow am.



Thanks for the ideas!

Hey Greg, have you changed the structure of a table that you already had in the Deployment Data node?

It looks like something may be fishy about your Deployment Data items.  Just looking at the code and the stack trace isn't cluing me in as to what is causing the issue...other than it is possible that the error may be occuring due to a recursive call that attempts to get the children records based on the level specified...or the server cannot be accessed...or something along those lines. 

You might try removing the deployment data items and adding them back one at a time to see where the error is coming from so that we can at least trouble shoot what is causing the error.

I'm getting a 1026 message ID error when I try to create a package. It indicates there is "No row at position zero". Screen shot attached.