I enabled Windows Events for OnError, OnTaskFailed, OnWarning for my package and subelements. However, even if no errors occur, I still get Informational Events generated even though those are disabled for all modules and packages. Any way to disable Information Events? Is this an SSIS defect, or just an oddity of how it implements Windows Events?Windows Event:Source: SQLISPackageType: InformationEvent ID: 12288Description: Package "XXXXXX" started.Event ID: 122289Description: Package "XXXXXX" finished successfully.

faype02 wrote: I enabled Windows Events for OnError, OnTaskFailed, OnWarning for my package and subelements. However, even if no errors occur, I still get Informational Events generated even though those are disabled for all modules and packages. Any way to disable Information Events? Is this an SSIS defect, or just an oddity of how it implements Windows Events?Windows Event:Source: SQLISPackageType: InformationEvent ID: 12288Description: Package "XXXXXX" started.Event ID: 122289Description: Package "XXXXXX" finished successfully. Oh yeah, I can reproduce that. Weird - I don't think those should be there. [Microsoft follow-up] Is this a bug or by design? -Jamie

It appears that this is by design see: http://www.microsoft.com/technet/prodtechnol/sql/2005/mgngssis.mspx In section on "Custom Log Provider" it says: "To facilitate operations management, SSIS packages always write some basic logging information to the Windows event log, even for packages that do not incorporate logging. SSIS packages write events for package initiation and package completion and they can be identified using either the SQLISPackage or SQLISService event sources." It would be a lovely option to be able to disable this. Regards

So if I have a package that executes every 30 seconds, I have no control over thousands of "package start" and "package finished" log events per day??????There must be a way to intercept these with an event handler in the package - how would this be done?

Did anyone get an answer to this problem? Our users want to run the package once per minute. Way too much noise in the Event Viewer due to this Microsoft "feature". A very messy intrusion on the Event Viewer by SSIS. Please tell me how to turn it off!!!

Stupid!!!!! Crazy wild innumerable unnecessary cluttering log entries. Please help! Who cares that the package started and finished? I categorize this under the heading "bug". SSIS really missed the boat on this one. Please allow one to disable these foolish log entries.

Hi, Like you, I've been tearing my hair out looking for a way to remove the SSIS Package Start and End Events (SQLISPackage - 12288 and 12289) from the application log. The good news is I've found a way. The bad news is: it's a registry hack. Event log information is stored in the Registry in the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog. Inside this key is a key for each one of the log files (Application, Security, System etc) and inside each of these is a key for each EventSource (of which SQLISPackage is one - under Application). What I did was create a custom log file called SSIS by adding a key to the Registry : HKLM\SYSTEM\CurrentControlSet\Services\EventLog\SSIS. I then moved the SQLISPackage key from Application to the new SSIS key. After rebooting the server, the SQLISPackage Events are no longer written to the Application log - they are now written to a new log file called SSIS. As I have said - this suggestion comes with no warranty that it won't break SSIS but I was most pleased to find that it appears to work without issue, but I've yet to deploy this in a production environment - I'm testing it more thoroughly first. Hope this helps, Alex Weatherall www.TeleWare.com

Ok, if you want to disable all events. This is not what I am looking for - I HAVE to receive error messages, otherwise, I could have just disable all event logging for SSIS (without a registry hack). I want to have events logged, but I want to limit the LEVEL of logging, so I don't have tens of thousands of 'start' and 'end' events that are worthless. How can people stand this?

This registry solution works great for me. All the start/stop messages are going to the SSIS log as well as other SSIS SQLISPackage errors where I can see them if I need to. And allmy internal package messages are directed to the Application log. This is effectively separating the clutter messages from the critical ones I generate from my internal package processing. Thanks for this solution. Wa

Hi, I know that this thread is very old.. and there is probablya solution for stopping those annoying PackageStart/PackageEnd entries. But I haven't managed to come accross a solution.please, could anybody help and share the solution? Thanks in advance

Oh my god! This is so extremly annoying!!!!! Still nobody out there who has a solution? I have to perform a transaction log backup each minute and those 12288/89 event log entries make the eventlog totally unreadable :-((

Harrr!! I always find a solution short after posting a question into a forum. ;-) Here we go: In the registry go to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\SSIS" node and change the value of "LogPackageExecutionToEventLog" key from 1 to 0. Msdn says that new installments of SqlServer2008 set this value to 0 as standard but in my case this was different! Here is the msdn link about the topic: http://msdn.microsoft.com/en-us/library/ms143731.aspx (simply search for 12288 in the article)

Any solution for sql server 2005? This is plaguing our eventlogs with tons of useless entries making eventlog unreadable for pertinent information and errors.

Arrrgh, My Sql2008 installations don't have this turned off by default. thanks.

Thank you Alex, your registry hack is the only feasable thing to do on 2005. Here's the .reg file i created: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\SSIS] "File"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\ 00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,43,00,\ 6f,00,6e,00,66,00,69,00,67,00,5c,00,53,00,53,00,49,00,53,00,2e,00,61,00,76,\ 00,74,00,00,00 "CustomSD"="O:BAG:SYD:(D;;0xf0007;;;AN)(D;;0xf0007;;;BG)(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x7;;;SO)(A;;0x3;;;IU)(A;;0x3;;;SU)(A;;0x3;;;S-1-5-3)" "Sources"=hex(7):53,00,51,00,4c,00,49,00,53,00,50,00,61,00,63,00,6b,00,61,00,\ 67,00,65,00,00,00,00,00 [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLISPackage] "EventMessageFile"="%programfiles%\\Microsoft SQL Server\\90\\DTS\\Binn\\Resources\\1040\\dtsmsg.rll" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\SSIS\SQLISPackage] "EventMessageFile"="%programfiles%\\Microsoft SQL Server\\90\\DTS\\Binn\\Resources\\1040\\dtsmsg.rll"

Hi Guys , I have not solved the problem for the windows eventlog,but I am logging to SQL Server in my packages and by deafult Integration Services uses a stored procedure called sp_ssis_addlogentry to insert a records for events in the sysssislog table.I altered the stored procedure to only insert into the sysssislog table if the event is an onerror event ,hence filtering out the OnPackageStart and OnPackageEnd events.Hope it helps someone.One should be able to do the same for SQL Server 2005 where logging is done via the sp_dts_addlogentry to the sysdtslogs90 table IF (@event = 'onerror') BEGIN INSERT INTO sysssislog ( event, computer, operator, source, sourceid, executionid, starttime, endtime, datacode, databytes, message ) VALUES ( @event, @computer, @operator, @source, @sourceid, @executionid, @starttime, @endtime, @datacode, @databytes, @message ) END

raf Thanks for sharing. Good work.

I think its a bug in SSIS Log Provider or its by design. What you will have to do is implement ssis logging using eventhandler See this Article very well documented. http://pragmaticworks.com/Products/Business-Intelligence/BIxPress/ssis-logging-auditing-monitoring.aspx SSIS-Tutorials-FAQs | Convert DTS to SSIS | Document SSIS | SSIS Tasks | Real-time SSIS Monitoring