SSIS Script Task appears to run, but actually doesn'tSSIS Package Validation Error when Executed From Windows...
Coworker is trying to get me to sign his petition to run for office. How to decline politely?
Why did Tywin never remarry?
Bitcoin automatically diverted to bech32 address
Does a star need to be inside a galaxy?
Which was the first story to feature space elevators?
Buying a "Used" Router
Why do most space probes survive for far longer than they were designed for?
Run a command that requires sudo after a time has passed
How bad is a Computer Science course that doesn't teach Design Patterns?
Why is it a problem for Freddie if the guys from Munich did what he wanted?
Is layered encryption more secure than long passwords?
Identical projects by students at two different colleges: still plagiarism?
How can guns be countered by melee combat without raw-ability or exceptional explanations?
Taking an academic pseudonym?
Do error bars on probabilities have any meaning?
Should corporate security training be tailored based on a users' job role?
Found a major flaw in paper from home university – to which I would like to return
Prove that a cyclic group with only one generator can have at most 2 elements
Does the phrase がんばする makes sense?
What happens if you declare more than $10,000 at the US border?
Is 'bad luck' with former employees a red flag?
Pictures from Mars
I'm struggling to say 'struggle'
Why are energy weapons seen as more acceptable in children's shows than guns that fire bullets?
SSIS Script Task appears to run, but actually doesn't
SSIS Package Validation Error when Executed From Windows Task SchedulerSSIS package error, can't find pre-compiled scriptError while executing SSIS package which contains Script component through SQL Server Agent JobSSIS Execute Sql Task not executed on serverSQL Server 2014 SSIS Package Ignores Script Task when running as AGENTSSIS Script Task doesn't appear to run when scheduledwhen running SSIS package with Windows Auth it works but with SQL Auth it failsHow to change a script task version in SSIS?SSIS Not Executing any Script TaskSSIS package deployed to SQL Server hangs when running a Powershell script
I have a script task that appears as running fine, but no matter what I put inside nothing ever get executed. I tried all sort of stuff: logging via the built in SSIS Logging mechanism, logging through additional variables and SQL Command task and I can never figure what's wrong. I tried to put breakpoint and it won't break during debugging.
This is VS 2015 with SQL 2016. This issue happens only when deployed on one of the SQL Server. I previously has no issue at all at that server. I deployed the same package on a different SQL box (same configuration) and it ran as expected.
EDIT: To better clarify the problem I started a new SSIS Package, it only 3 script tasks in it:
Test Task:
public void Main()
{
// TODO: Add your code here
Dts.TaskResult = (int)ScriptResults.Failure;
}
Once the Test Task is completed, it is linked to a "Success Task" if the test is successful, a "Fail Task" if it fails.
On VS, the test task fail as expected and goes to the fail task. However once deployed it stop working.
ssis
asked Nov 15 '17 at 21:53
elty123elty123
151129
add a comment |
I have a script task that appears as running fine, but no matter what I put inside nothing ever get executed. I tried all sort of stuff: logging via the built in SSIS Logging mechanism, logging through additional variables and SQL Command task and I can never figure what's wrong. I tried to put breakpoint and it won't break during debugging.
This is VS 2015 with SQL 2016. This issue happens only when deployed on one of the SQL Server. I previously has no issue at all at that server. I deployed the same package on a different SQL box (same configuration) and it ran as expected.
EDIT: To better clarify the problem I started a new SSIS Package, it only 3 script tasks in it:
Test Task:
public void Main()
{
// TODO: Add your code here
Dts.TaskResult = (int)ScriptResults.Failure;
}
Once the Test Task is completed, it is linked to a "Success Task" if the test is successful, a "Fail Task" if it fails.
On VS, the test task fail as expected and goes to the fail task. However once deployed it stop working.
ssis
asked Nov 15 '17 at 21:53
elty123elty123
151129
if you remove the try/catch does it blow up like it should?
– indiri
Nov 15 '17 at 22:52
1
I modify the code so all it does is Dts.TaskResult = (int)ScriptResults.Failure; and it still said the task success.
– elty123
Nov 16 '17 at 16:12
add a comment |
I have a script task that appears as running fine, but no matter what I put inside nothing ever get executed. I tried all sort of stuff: logging via the built in SSIS Logging mechanism, logging through additional variables and SQL Command task and I can never figure what's wrong. I tried to put breakpoint and it won't break during debugging.
This is VS 2015 with SQL 2016. This issue happens only when deployed on one of the SQL Server. I previously has no issue at all at that server. I deployed the same package on a different SQL box (same configuration) and it ran as expected.
EDIT: To better clarify the problem I started a new SSIS Package, it only 3 script tasks in it:
Test Task:
public void Main()
{
// TODO: Add your code here
Dts.TaskResult = (int)ScriptResults.Failure;
}
Once the Test Task is completed, it is linked to a "Success Task" if the test is successful, a "Fail Task" if it fails.
On VS, the test task fail as expected and goes to the fail task. However once deployed it stop working.
ssis
asked Nov 15 '17 at 21:53
elty123elty123
151129
I have a script task that appears as running fine, but no matter what I put inside nothing ever get executed. I tried all sort of stuff: logging via the built in SSIS Logging mechanism, logging through additional variables and SQL Command task and I can never figure what's wrong. I tried to put breakpoint and it won't break during debugging.
This is VS 2015 with SQL 2016. This issue happens only when deployed on one of the SQL Server. I previously has no issue at all at that server. I deployed the same package on a different SQL box (same configuration) and it ran as expected.
EDIT: To better clarify the problem I started a new SSIS Package, it only 3 script tasks in it:
Test Task:
public void Main()
{
// TODO: Add your code here
Dts.TaskResult = (int)ScriptResults.Failure;
}
Once the Test Task is completed, it is linked to a "Success Task" if the test is successful, a "Fail Task" if it fails.
On VS, the test task fail as expected and goes to the fail task. However once deployed it stop working.
ssis
ssis
asked Nov 15 '17 at 21:53
elty123elty123
151129
asked Nov 15 '17 at 21:53
elty123elty123
151129
edited Nov 16 '17 at 16:42
elty123
asked Nov 15 '17 at 21:53
elty123elty123
151129
asked Nov 15 '17 at 21:53
elty123elty123
151129
asked Nov 15 '17 at 21:53
elty123elty123
151129
151129
if you remove the try/catch does it blow up like it should?
– indiri
Nov 15 '17 at 22:52
1
I modify the code so all it does is Dts.TaskResult = (int)ScriptResults.Failure; and it still said the task success.
– elty123
Nov 16 '17 at 16:12
add a comment |
if you remove the try/catch does it blow up like it should?
– indiri
Nov 15 '17 at 22:52
1
I modify the code so all it does is Dts.TaskResult = (int)ScriptResults.Failure; and it still said the task success.
– elty123
Nov 16 '17 at 16:12
if you remove the try/catch does it blow up like it should?
– indiri
Nov 15 '17 at 22:52
if you remove the try/catch does it blow up like it should?
– indiri
Nov 15 '17 at 22:52
1
1
I modify the code so all it does is Dts.TaskResult = (int)ScriptResults.Failure; and it still said the task success.
– elty123
Nov 16 '17 at 16:12
I modify the code so all it does is Dts.TaskResult = (int)ScriptResults.Failure; and it still said the task success.
– elty123
Nov 16 '17 at 16:12
add a comment |
1 Answer
1
active
oldest
votes
There are 2 things you can check:
(1) The TargetServerVersion property
Check that you are selecting the appropriate TargetServerVersion property
GoTo Project Properties >> Configuration Properties >> TargetServerVersion
(2) ForceExecutionResult property Value
Click on Fail Task and press F4 to show the perperty Tab, check that ForceExecutionResult is set to False.
(3) Run in 32-bit mode
Try running the package in 32-bit mode:
GoTo Project properties >> Debugging >> Run64BitRuntime = False
answered 1 hour ago
HadiHadi
1,150616
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f191029%2fssis-script-task-appears-to-run-but-actually-doesnt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are 2 things you can check:
(1) The TargetServerVersion property
Check that you are selecting the appropriate TargetServerVersion property
GoTo Project Properties >> Configuration Properties >> TargetServerVersion
(2) ForceExecutionResult property Value
Click on Fail Task and press F4 to show the perperty Tab, check that ForceExecutionResult is set to False.
(3) Run in 32-bit mode
Try running the package in 32-bit mode:
GoTo Project properties >> Debugging >> Run64BitRuntime = False
answered 1 hour ago
HadiHadi
1,150616
add a comment |
There are 2 things you can check:
(1) The TargetServerVersion property
Check that you are selecting the appropriate TargetServerVersion property
GoTo Project Properties >> Configuration Properties >> TargetServerVersion
(2) ForceExecutionResult property Value
Click on Fail Task and press F4 to show the perperty Tab, check that ForceExecutionResult is set to False.
(3) Run in 32-bit mode
Try running the package in 32-bit mode:
GoTo Project properties >> Debugging >> Run64BitRuntime = False
answered 1 hour ago
HadiHadi
1,150616
add a comment |
There are 2 things you can check:
(1) The TargetServerVersion property
Check that you are selecting the appropriate TargetServerVersion property
GoTo Project Properties >> Configuration Properties >> TargetServerVersion
(2) ForceExecutionResult property Value
Click on Fail Task and press F4 to show the perperty Tab, check that ForceExecutionResult is set to False.
(3) Run in 32-bit mode
Try running the package in 32-bit mode:
GoTo Project properties >> Debugging >> Run64BitRuntime = False
answered 1 hour ago
HadiHadi
1,150616
There are 2 things you can check:
(1) The TargetServerVersion property
Check that you are selecting the appropriate TargetServerVersion property
GoTo Project Properties >> Configuration Properties >> TargetServerVersion
(2) ForceExecutionResult property Value
Click on Fail Task and press F4 to show the perperty Tab, check that ForceExecutionResult is set to False.
(3) Run in 32-bit mode
Try running the package in 32-bit mode:
GoTo Project properties >> Debugging >> Run64BitRuntime = False
answered 1 hour ago
HadiHadi
1,150616
edited 1 hour ago
answered 1 hour ago
HadiHadi
1,150616
answered 1 hour ago
HadiHadi
1,150616
answered 1 hour ago
HadiHadi
1,150616
1,150616
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f191029%2fssis-script-task-appears-to-run-but-actually-doesnt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
if you remove the try/catch does it blow up like it should?
– indiri
Nov 15 '17 at 22:52
1
I modify the code so all it does is Dts.TaskResult = (int)ScriptResults.Failure; and it still said the task success.
– elty123
Nov 16 '17 at 16:12