Amour22015
asked on
SSIS 2008 - When running debug errors
Hi,
Using Execute SQL Task.
When I do the:
Edit Breakpoints
Set the Breakpoints
F5
I am getting a error on a parameter that I am NOT mapping.
That is FILE_DT
the error is:
Package Vaildation Error
Error at Execute SQL Task: Failed to lock variable "User::FILE_DT"
But the problem is that I don't have a FILE_DT under the Parameter Mapping or the Result Set.
I did create FILE_DT, but I did a remove from the Parameter Mapping Tab.
Please help and thanks
Using Execute SQL Task.
When I do the:
Edit Breakpoints
Set the Breakpoints
F5
I am getting a error on a parameter that I am NOT mapping.
That is FILE_DT
the error is:
Package Vaildation Error
Error at Execute SQL Task: Failed to lock variable "User::FILE_DT"
But the problem is that I don't have a FILE_DT under the Parameter Mapping or the Result Set.
I did create FILE_DT, but I did a remove from the Parameter Mapping Tab.
Please help and thanks
ASKER
Ok,
I am very new to all this.
Looks like I don't understand your comments.
When I do the:
Edit Breakpoints - I right click on the Execute SQL Task: Get File Id From Database_Table
Set the Breakpoints
<F5>
I am getting a error on a parameter that I am NOT mapping. See attached snapshots
That is FILE_DT
I am only referencing FILEID
Please help..
SnapshotPassingVariables.docx
I am very new to all this.
Looks like I don't understand your comments.
When I do the:
Edit Breakpoints - I right click on the Execute SQL Task: Get File Id From Database_Table
Set the Breakpoints
<F5>
I am getting a error on a parameter that I am NOT mapping. See attached snapshots
That is FILE_DT
I am only referencing FILEID
Please help..
SnapshotPassingVariables.docx
Go to the properties of the "Package", right at the top there is a section for checkpoint attributes. Make sure CheckpointUsage is set to nver and SaveCheckpoints is set to False. Save the package and try again.
ASKER
They are currently set to what you mentioned..
I did create a variable with the name:
FILE_DT
but I did a remove from within parameter mapping tab
I have noticed that any variables that I did create and removed are still showing up in the dropdown.
Could this be the problem? If so then how can you permently delete the unwanted variables from the dropdown? That were created by mistake...
Thanks
I did create a variable with the name:
FILE_DT
but I did a remove from within parameter mapping tab
I have noticed that any variables that I did create and removed are still showing up in the dropdown.
Could this be the problem? If so then how can you permently delete the unwanted variables from the dropdown? That were created by mistake...
Thanks
Oh that's easy, just go to the variable window ( if it's not open go to the menu bar, View>Other Windows>Variable), where you can see all variables and edit or delete them if needed.
ASKER
I did:
View>Other Windows>Variables
Also
Right click within the Control Flow and select Variables
But when the Variables window appeared
there was only
FILEID
FILEIDS
No display of:
FILE_DT
Please help and thanks
View>Other Windows>Variables
Also
Right click within the Control Flow and select Variables
But when the Variables window appeared
there was only
FILEID
FILEIDS
No display of:
FILE_DT
Please help and thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So I found the problem,
I did not know that when doing a parameter check that it looks though all the task within the package.
I thought that when you did a right click on one task and selected "Edit BreakPoints" that it just checked that one task.
Thanks
I did not know that when doing a parameter check that it looks though all the task within the package.
I thought that when you did a right click on one task and selected "Edit BreakPoints" that it just checked that one task.
Thanks
ASKER
Thanks
If you have checked all components and containers and are sure that you haven't left any such reference, another possibility is that you've enabled checkpoints for your package.
When checkpoints are enable, details about the variables are written to the checkpoint file when the package is executed. If you delete any of the existing variables afterwards, make sure to delete the checkpoint file before restarting the package, otherwise if the checkpoint file is read upon execution, it will try to assign a value to the variable that has been deleted and you'll get this error.