SSIS, fire events and the execution reports
I have an SSIS package with a script task that fires various information and warning messages, for example:
Dts.Events.FireWarning(1, taskName, "Common Version API URL not specified", null, 0);
This works fine on my laptop where I have it running in SQL Server 2017. The message gets written to the Execution report just as desired:
However, when I deploy and run the package in our test environment, which is using SQL Server 2016, the execution report does not show any of my messages. Could this be due to some setting that I'm not aware of or is this maybe a feature that is missing in SQL Server 2016?
I don't actually have an answer for my question, however, my problem has been solved. The Dts.Events.FireWarning etc. now works as expected, i.e.my messages are included in the execution report in our test (and production) environments. As I have not changed any code I can only assume that something in those environments have changed. I've asked if it has been any update that could explain this but I've not received any satisfying answer.
- Math.Sin() gives incorrect value
- How to run my python script when the sunOS is start booting
- Express-session: not resetting cookie expiration on each request
- Getting a stack overflow exception when normalizing a vector
- Edit default summary function in R gives error for multiple variables
- What was a For loop? Why isn't it needed in R?
- How to use download button in shiny and save results in various formats (csv, texte, pdf, spss...)?
- Why are there two assignment operators, `<-` and `->` in R?
- lm()$assign: what is it?
- How to get the value of list(...) in R and S functions
- Design matrix for MLM from library(lme4) with fixed and random effects
- how to generate elements not included in my sample
- Create a matrix with gradually changing values without a for loop
- Emacs ESS and S-plus ( S+ ) 8.1 compatability
- How to lag date-index in a time-series in R?
- Nonlinear regression in R / S
- Calling R from S-Plus?