January 27, 2014 at 10:43 am
I'm using SS 2008.
I have a SSIS package that was running fine. Then, a server change out was made on 12/10, and a new IP address was needed for data connection. All these changes were made to the data connections, it was thought.
On 12/13, the task ran fine. On 12/16, it bombed saying could not find server.
This is set to run twice a day, M-F. After that point, I don't believe it has run automatically since. I'm needing to get in and run it manually. I say "don't believe" as, I can't remember if the instances it shows as having run in the meantime are when I ran it manually.
The History list under the Task Scheduler (this is run from the Windows Task scheduler, not SS Agent), shows it being run every day, twice a day, with no errors.
The log files from SSIS show a different situation, and one which matches the data results. I.e., it is not running, or not updating the data.
Any ideas on how I can track down this issue?
January 27, 2014 at 2:56 pm
I went and tried to run the batch file manually, noticed that it just blasted by on the screen in way under 1 second, and figured the batch file was erroring out. I got this information from the batch process output. I x'd out some connection id details, just in case I was about to violate some internal security by posting this. How do I go about fixing this? This is not a process I created:
Started: 1:47:35 PM
Error: 2014-01-27 13:47:35.28
Code: 0xC001000E
Source:
Description: The connection "{C180B6A1-XXXXXXX}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Error: 2014-01-27 13:47:35.35
Code: 0xC001000E
Source: Weekly_Master
Description: The connection "{C180B6A1-XXXXXXX}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Error: 2014-01-27 13:47:35.35
Code: 0xC001000E
Source: Weekly_Master
Description: The connection "{C180B6A1-XXXXXXX}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Error: 2014-01-27 13:47:35.35
Code: 0xC00291EB
Source: Query Max Snapshots Execute SQL Task
Description: Connection manager "{C180B6A1-XXXXXXX}" does not exist.
End Error
Error: 2014-01-27 13:47:35.35
Code: 0xC0024107
Source: Query Max Snapshots
Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 1:47:35 PM
Finished: 1:47:35 PM
Elapsed: 0.25 seconds
January 27, 2014 at 3:31 pm
That connection is in the dtsx package, but it's possible another connection was used in the log feature. I don't know how to check what connection the log is using.
January 27, 2014 at 4:23 pm
Further, I have one DTSX package calling another. The one that is called works if I run it on it's own. The outer one blows up, and now it's saying it needs to always restart from a checkpoint.
I looked at the XML code, and the object id for the data connection is not the same as the current data connection.
How do I change this in the log utility?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply