error message i don't understand

[AtomicWedgie]

Hi,

I created a package but when i try to run it i get the following error:

"The connection for a task was not specified or was not found."

I have absolutely got no clue what this means. I tested the source (which is a query) in DTS and in query analyser and it works correctly. I have tested every DTS_Transformation task in the package individually and they all work according to DTS.

Does anybody know what the problem is?

Regards,

Atomic Wedgie

 

[AtomicWedgie]

Found it.

 

[itlee]

AtomicWedgie what was the solution?

I am having the same problem after I moved my DTS package to another server, re-created the connection objects, and pointed the ExecuteSQLTask connection to the new connection. When I individually run the task it runs fine, but as a scheduled job it fails with error: "The connection for a task was not specified or was not found."

Any help would be appreciated.

itlee.

ITLee. MCP\Analyst\Programmer\DBA\ITIL

 

[AtomicWedgie]

Hi,

I absolutely don't have a clue anymore what I did wrong and how i fixed it.

Sorry,

Atomic Wedgie

 

[edwardturner]

ITLee, I came across the very same issue about a month ago having moved a bunch of DTS packages to another server.

One solution is to go to Package - Disconnceted Edit. Here you will find a tree structure of all the items that comprise you package. Take a look at each one and see if there is still a reference to the old server name. It is possible that a data pump task or any task for that matter could still be referencing the old server name.

For the future what you can do is use the Dynamic Properties Task option (grey icon, bottom right of tasks list). This allows you to set parameters within the packge to be equal to say a global variable. What you can do there is have a bunch for global variables for server name, database name, sa password, source file location etc... These global variables can be set by right clicking on the package canvas and going to package properties - global variables tab). If you move the package to a new server, just change the global variables to the new settings and you are away.