August 28, 2010 at 12:10 pm
A job which has been running fine for a while has suddenly started barking back with the following error message:
Source: Script Task 1 Description: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on a container during execution of the package and the element is not there.
Now here's the thing. The job started executing at around 10am. About 40 minutes in, my laptop crashed, however, i'd executed the job via remote desktop to the host machine where the SQL Service instance resides. The process/job was not running on my machine.
I went back and tested this package in debug and it runs perfectly without error. All variables that are in use are used as far as i can tell, and a debug session using F10 and F11 over every line in the scripting task does what it's supposed to do without throwing any exceptions. I rebuilt and deployed the job to the database on the SQL instance where the job is running from. Still no difference; getting the same error back every time.
When the package is run from the job, it relies on a config file which looks to be intact. I read somewhere about xml corruption on the server level, but the topic ran into things far over my head.
Anyway, i'm out of ideas and hoping someone out there might have a suggestion.
Many thanks in advance,
B
September 1, 2010 at 11:51 am
When you run it locally do you use the prod config file?
CEWII
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply