October 14, 2015 at 3:00 am
Hi i have been working in project which usses SSIS package to uplaod multiple files and they are been called by batch script(cmd)
i want to capture the error from cmd to Message box in VBA or might be in SQL server and capture it and display to the user , so it becomes easier for thenm to rectify error .
October 14, 2015 at 3:11 am
SSIS packages are designed to run unattended, not interactively, so don't use message boxes - they'll make your package fail as soon as you schedule it. Have you tried enabling package logging?
John
October 19, 2015 at 12:00 pm
Some suggestions.
If possible make a Send Mail task that will run in the package OnError event handler. Lots of notification there but maintenance depending on how you set up the mail distribution.
Also possible is to create an audit logging process that will flat critical errors and sent out SSRS reports or another package can pick them up and send them using that same Send Mail task.
The SSIS catalog has some logging and reporting functions if you're using it.
Regardless John is right and since the packages run without user action having a message box is a very bad idea. It's better to figure out a way to get those notifications out without breaking your package flow and in a way that it's distributed to those who can fix it.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply