Sfrgttk

Is the "hot network questions" element on Stack Overflow a dark pattern?

How to create a cover page like this?

Is candidate anonymity at all practical?

Why does Python copy numpy arrays where the length of the dimensions are the same?

Who, if anyone, was the first astronaut to return to earth in a different vessel?

Taking an academic pseudonym?

How do I add numbers from two txt files with Bash?

Arbitrary Interval Ruler

Unions, aliasing and type-punning in practice: what works and what does not?

Can neural cryptanalysis be applied to AES?

What happens if you declare more than $10,000 at the US border?

Why did Shae (falsely) implicate Sansa?

Is it possible to make a dynamically risizing filesystem-as-file?

As per hinduism, does life span of human depends on his respiratory breaths?

How can guns be countered by melee combat without raw-ability or exceptional explanations?

How to run a binary file from crontab?

Father gets chickenpox, but doesn't infect his two children. How is this possible?

Lost citations on Scholar

What's the relationship between the chords Cmaj Dmaj Emaj?

I hate taking lectures, can I still survive in academia?

Manager has noticed coworker's excessive breaks. Should I warn him?

Hands-Free Methods of Firing Arrows for Flying Soldiers

Why do atoms emit a certain colour of light? (The emission spectra)

Why does the includeonly command not stepcounter the chaptercounter for omitted chapters?

SSIS: Scripts in package part not being executed when target server is 2016

SSIS File System Task Copy File Could not find part of the path errorError while executing SSIS package which contains Script component through SQL Server Agent JobRunning Excel Macro Code by SSIS package configured with SQL Server Job agentMSSQL: Export Wizard, not possible to save SSIS PackageFault Finding SSIS “Unexpected Termination” - SQL Server 2016SSIS FTP Package job fails when scheduling through SQL Server Agent jobSource - ODBC is not compatible with this version of the DataFlowUpgrading SSIS Packages to 2017SSIS package deployed to SQL Server hangs when running a Powershell scriptSSIS Package when executed via agent job or manually on SQL Server does nothing, but shows it completed successfully. What gives?

1

I am having an issue with SSIS packages where scripts included in package parts ar not executed when the target server version is SQL Server 2016.

1. Create an SSIS project, set target server version to SQL Server 2016 (very important!)



2. 
   

   Go ahead and add a simple script in the default Package. This should work fine.

   
   
   
   
   
   • In my case I have a script that sends an email using SendGrid service via SMTP. You can see the code here: https://pastebin.com/DW3hfBP3
     
   
   
   • However I tested this issue with other scripts Something like: MessageBox.Show("Great. Another bug. Thanks a lot guys..."); would do.
   
   
   
   



3. Create a package part.



4. 
   

   Now just try re-creating the simple script from step 2 into the package part. Then add the package part onto the default Package or another package and execute the task. Even though the execution is successful, the script is not executed.

   
   
   

   NOTE: If you try to copy the script from the default package into the package part, you should also notice a moronic error saying that the version is wrong. This is why I say to re-create the script in the package part.

   
   

I wonder if anyone could reproduce this issue and if there is a way around it? Worth noticing that this issue doesn't seem to happen when the target server is SQL 2017.

sql-server ssis-2016

share|improve this question

edited 10 hours ago

Tony Hinkle

2,4181422

asked 17 hours ago

pmdcipmdci

3851313

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I've been looking into the code of the package part and it seems that script code is not saved properly.
  
  – pmdci
  17 hours ago
  

  
  
  
  

add a comment | 

1

I am having an issue with SSIS packages where scripts included in package parts ar not executed when the target server version is SQL Server 2016.

1. Create an SSIS project, set target server version to SQL Server 2016 (very important!)



2. 
   

   Go ahead and add a simple script in the default Package. This should work fine.

   
   
   
   
   
   • In my case I have a script that sends an email using SendGrid service via SMTP. You can see the code here: https://pastebin.com/DW3hfBP3
     
   
   
   • However I tested this issue with other scripts Something like: MessageBox.Show("Great. Another bug. Thanks a lot guys..."); would do.
   
   
   
   



3. Create a package part.



4. 
   

   Now just try re-creating the simple script from step 2 into the package part. Then add the package part onto the default Package or another package and execute the task. Even though the execution is successful, the script is not executed.

   
   
   

   NOTE: If you try to copy the script from the default package into the package part, you should also notice a moronic error saying that the version is wrong. This is why I say to re-create the script in the package part.

   
   

I wonder if anyone could reproduce this issue and if there is a way around it? Worth noticing that this issue doesn't seem to happen when the target server is SQL 2017.

sql-server ssis-2016

share|improve this question

edited 10 hours ago

Tony Hinkle

2,4181422

asked 17 hours ago

pmdcipmdci

3851313

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I've been looking into the code of the package part and it seems that script code is not saved properly.
  
  – pmdci
  17 hours ago
  

  
  
  
  

add a comment | 

I am having an issue with SSIS packages where scripts included in package parts ar not executed when the target server version is SQL Server 2016.

1. Create an SSIS project, set target server version to SQL Server 2016 (very important!)



2. 
   

   Go ahead and add a simple script in the default Package. This should work fine.

   
   
   
   
   
   • In my case I have a script that sends an email using SendGrid service via SMTP. You can see the code here: https://pastebin.com/DW3hfBP3
     
   
   
   • However I tested this issue with other scripts Something like: MessageBox.Show("Great. Another bug. Thanks a lot guys..."); would do.
   
   
   
   



3. Create a package part.



4. 
   

   Now just try re-creating the simple script from step 2 into the package part. Then add the package part onto the default Package or another package and execute the task. Even though the execution is successful, the script is not executed.

   
   
   

   NOTE: If you try to copy the script from the default package into the package part, you should also notice a moronic error saying that the version is wrong. This is why I say to re-create the script in the package part.

   
   

I wonder if anyone could reproduce this issue and if there is a way around it? Worth noticing that this issue doesn't seem to happen when the target server is SQL 2017.

sql-server ssis-2016

share|improve this question

edited 10 hours ago

Tony Hinkle

2,4181422

asked 17 hours ago

pmdcipmdci

3851313

share|improve this question

edited 10 hours ago

Tony Hinkle

2,4181422

asked 17 hours ago

pmdcipmdci

3851313

share|improve this question

edited 10 hours ago

Tony Hinkle

2,4181422

asked 17 hours ago

pmdcipmdci

3851313

edited 10 hours ago

Tony Hinkle

2,4181422

edited 10 hours ago

Tony Hinkle

2,4181422

asked 17 hours ago

pmdcipmdci

3851313

asked 17 hours ago

pmdcipmdci

3851313