Bogus Error can't define Precedence Constraints between different containers

Question

Bogus Error can't define Precedence Constraints between different containers

Welsh Corgi

SSC Guru

Points: 116520
More actions
May 12, 2012 at 12:25 pm

#143486

I get this Bogus Error that I can't define Precedence Constraints between different containers.
I'm just trying to define a constraint from one task to another within the same sequence container?
I do not get it?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 1

I've only had this happen when I had a component that only looked like it was in the same container. I moved them around and it resolved the issue.

CEWII

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

Thank you Elliot.

I running it for now for I'm trying to get it loaded.

I'm not expected to work today but I would like to keep things moving.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 3

I had to take a time out from that package.

In one of the containers where I'm having this issue I attempted to drag all of the tasks outside the container.

"When I attempted to drag one of the task I get this strange error I get an error message.. The element cannot be found in the collection. This error happens when you attempt to retrieve an element from a collection during execution of the package and the package is not there."

The package is not in execution mode.

Very weird.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 4

I had to delete the task and recreate and and the problem went away.

My guess is that there was some corruption.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/