Execute SSIS from SQL agent job and mysterious error

Hi,
I need help to figure an error from sql agent's job history. I created an SSIS package to pull data from Sybase into SQL server 2008 64-bit. I installed the appropriate drivers (I think) and the package runs fine when from package properties 32-bit runtime is selected. When I schedule this package in a job, first of all, I cannot get it to work unless I either specify password for sybase connection in the job step or save the connection in config file and specify that in the job. Now the job works but when I look at the job history it shows following message:

Executed as user: server\sqlagentservice. Microsoft (R) SQL Server Execute Package Utility  Version 10.0.2531.0 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  12:36:04 PM  Error: 2010-11-16 12:36:06.18     Code: 0xC001000E     Source:       Description: The connection "{E69B8062-96A8-477A-88FA-25C4746561C9}" is not found. This error is thrown by Connections collection when the specific connection element is not found.  End Error  DTExec: The package execution returned DTSER_SUCCESS (0).  Started:  12:36:04 PM  Finished: 12:36:09 PM  Elapsed:  5.272 seconds.  The package executed successfully.  The step succeeded.

What I really am trying to find out is the corresponding connection to the ID{E69B8062-96A8-477A-88FA-25C4746561C9} displayed in the error. Any idea?

Thanks for your assistance in advance.
Rainbow002Asked:
Who is Participating?
 
EvilPostItConnect With a Mentor Commented:
Ahhhh, ok. What about if you export it from SSIS and open in BIDS?
0
 
EvilPostItCommented:
The connection id you are refering to will actually be specific to your package.

If you look at your package design and select properties for each of your connection manager connection one of the id's should match.
0
 
Rainbow002Author Commented:
That's what the problem is...none of the connection managers' ID matches with the one returned by the job history.
0
 
Rainbow002Author Commented:
Finally, resolved. When I closed the BIDS and reopened and imported the package again, while validating, it threw the same error again. I doubled clicked on the error and the entire package was shown in XML. I searched for the connection ID in question and found that it was for a task which I had disabled. Not sure if this is a bug in SSIS that it has to validate even the disabled tasks...
0
 
EvilPostItCommented:
Glad i could help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.