Solved

Execute SSIS from SQL agent job and mysterious error

Posted on 2010-11-16
5
740 Views
Last Modified: 2012-05-10
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.
0
Comment
Question by:Rainbow002
  • 3
  • 2
5 Comments
 
LVL 16

Expert Comment

by:EvilPostIt
ID: 34144348
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
 

Author Comment

by:Rainbow002
ID: 34144381
That's what the problem is...none of the connection managers' ID matches with the one returned by the job history.
0
 
LVL 16

Accepted Solution

by:
EvilPostIt earned 250 total points
ID: 34144399
Ahhhh, ok. What about if you export it from SSIS and open in BIDS?
0
 

Author Comment

by:Rainbow002
ID: 34145170
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
 
LVL 16

Expert Comment

by:EvilPostIt
ID: 34145185
Glad i could help.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Occasionally there is a need to clean table columns, especially if you have inherited legacy data. There are obviously many ways to accomplish that, including elaborate UPDATE queries with anywhere from one to numerous REPLACE functions (even within…
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question