A script task is not functioning as expected at runtime when I use targetserverversion2019 on SSIS 2019

Question

A script task is not functioning as expected at runtime when I use targetserverversion2019 on SSIS 2019

Chapagain, Dilli R 96

On my local machine, the package runs fine with any targetserverversion, but when I load it into SQL Server Management Studio the script task doesn't work as expected at runtime environment. SQL job/package run successfully, However, the "Script Task" doesn't appear to be executing at all with targetserverversion2019. But when I change targetserverversion to 2014 it seems working fine.

Any suggestion to fix this problem will appreciate.

Yitzhak Khabinsky 26,491 Reputation points

2021-01-07T03:21:51.993+00:00
Please edit your post and provide additional details:

Visual Studio version.

SSDT version.

SQL Server + SSIS version on the server.
Chapagain, Dilli R 96 Reputation points

2021-01-07T04:06:37.563+00:00

Hi,
VS Version is 2019
SSDT Version: 2019
SQL Server @@version is Microsoft SQL Server 2019 (RTM-CU6) (KB4563110) - 15.0.4053.23 (X64) Jul 25 2020 11:26:55 Copyright (C) 2019 Microsoft Corporation Enterprise Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)

It seems like my script task is in a different version of SQL Server.

I am looking to find a way to update the script task version to match VS or SSMS version.
Yitzhak Khabinsky 26,491 Reputation points

2021-01-07T04:38:09.177+00:00

It seems that you missed a solution at the end of my answer:

After that you need to open Script Task in edit mode, and go to the Build menu, and rebuild it.
It will recompile that Script Task for the TargetServerVersion value.
Chapagain, Dilli R 96 Reputation points

2021-01-07T05:00:40.883+00:00

Hi @Yitzhak Khabinsky , Sorry I missed that part.

However, I still have the same issue after rebuilding the script task and redeploy the package.
My script task still not functioning.
Yitzhak Khabinsky 26,491 Reputation points

2021-01-07T13:15:01.107+00:00

@Chapagain, Dilli R ,

Please clarify exactly what is going on, and provide error messages if any

My script task still not functioning.

I updated my answer too. Please check its UPDATE section.

Accepted answer

2 additional answers

Your answer

Yitzhak Khabinsky 26,491 Reputation points

2021-01-07T03:21:51.993+00:00

Please edit your post and provide additional details:

Visual Studio version.

SSDT version.

SQL Server + SSIS version on the server.
Chapagain, Dilli R 96 Reputation points

2021-01-07T04:06:37.563+00:00

Hi,
VS Version is 2019
SSDT Version: 2019
SQL Server @@version is Microsoft SQL Server 2019 (RTM-CU6) (KB4563110) - 15.0.4053.23 (X64) Jul 25 2020 11:26:55 Copyright (C) 2019 Microsoft Corporation Enterprise Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)

It seems like my script task is in a different version of SQL Server.

I am looking to find a way to update the script task version to match VS or SSMS version.
Yitzhak Khabinsky 26,491 Reputation points

2021-01-07T04:38:09.177+00:00

It seems that you missed a solution at the end of my answer:

After that you need to open Script Task in edit mode, and go to the Build menu, and rebuild it.
It will recompile that Script Task for the TargetServerVersion value.
Chapagain, Dilli R 96 Reputation points

2021-01-07T05:00:40.883+00:00

Hi @Yitzhak Khabinsky , Sorry I missed that part.

However, I still have the same issue after rebuilding the script task and redeploy the package.
My script task still not functioning.
Yitzhak Khabinsky 26,491 Reputation points

2021-01-07T13:15:01.107+00:00

@Chapagain, Dilli R ,

Please clarify exactly what is going on, and provide error messages if any

My script task still not functioning.

I updated my answer too. Please check its UPDATE section.

Answer 1

Chapagain, Dilli R 96

Hi @Monalv-MSFT , @Yitzhak Khabinsky

Looks like I found the issue/solution-

I have been deploying my .ispac using .bat file (reason for my problem)

ISDeploymentWizard /S /SP:"%~dp0\xxx.ispac" /DestinationServer:"xxx" /DestinationPath:"/SSISDB/xxx/xxx"

pause

To resolved this, I have altered my environment Variable in the below order (on my window 10 machine). No more Script task issues using targetserverversion2019 on runtime now using with .bat file deployment.

Yitzhak Khabinsky 26,491 Reputation points

2021-01-08T19:50:30.63+00:00

Good to hear that you resolved the issue. 😊
Chapagain, Dilli R 96 Reputation points

2021-01-09T16:00:22.683+00:00

Thanks for help.

Answer 2

Monalv-MSFT 5,921

Hi @Chapagain, Dilli R ,

However, the "Script Task" doesn't appear to be executing at all with targetserverversion2019. But when I change targetserverversion to 2014 it seems working.

Please use select @@VERSION; in SQL Server Management Studio to check the version of SQL Server.
Then please set the TargetServerVersion according to the version of SQL Server.
It seems that your script task is created in the version of SQL Server 2014.

Best Regards,
Mona

----------

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Chapagain, Dilli R 96 Reputation points

2021-01-07T03:37:42.94+00:00

Thanks, @Mona for the quick reply.

I am working on to update our system to SQL2019 using VS2019

and My current SSMS select @@version is Microsoft SQL Server 2019 (RTM-CU6) (KB4563110) - 15.0.4053.23 (X64) Jul 25 2020 11:26:55 Copyright (C) 2019 Microsoft Corporation Enterprise Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)

I think your guess is accurate in my case here: "It seems that your script task is created in the version of SQL Server 2014."
Do you know how to update them to the SQL2019 version?
Monalv-MSFT 5,921 Reputation points

2021-01-08T06:56:00.477+00:00

Hi @Chapagain, Dilli R ,

Please backup the script in your Script Task. Then delete this Script Task and create a new Script Task.

Best Regards,
Mona
Karthik Kunala Venu 1 Reputation point

2022-09-06T06:07:36.427+00:00

Thank you so much, Mona.

Your answer solved my issue :).
mh 0 Reputation points

2025-04-11T19:02:48.71+00:00

I was developing against SQLServer 2022 but PROD is still SQL 2019. The ScriptTask kept failing in PROD after changing the TargetVersion from 2022 to 2019. Recreating the ScriptTask fixed the problem. Glad I found this, I'm not sure I would have thought to recreate it.

Answer 3

SSIS has two environments:

Dev. environment, on the development workstation where Visual Studio is installed.
TargetServerVersion setting value specifies future run-time environment.
Run-time environment, on a server with SQL Server + SSIS installed.

VS's TargetServerVersion value shall match SQL Server version in the run-time environment,

After that you need to open Script Task in edit mode, and go to the Build menu, and rebuild it.
It will recompile that Script Task for the TargetServerVersion value. And make sure that you see a "Build Succeeded" message in the Output pane.

UPDATE
Please make sure the following:

SSIS run-time server has the same .Net Framework version installed as specified in the SSIS Script Task.
VS2019 is updated up to the latest version: v.16.8.3
SQL Server Integration Services Projects extension is updated up to the latest version: v.3.11.1

Share via

A script task is not functioning as expected at runtime when I use targetserverversion2019 on SSIS 2019

2 additional answers

Your answer