Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 4354 Source: EventSystem

The COM+ Event System failed to fire the ConnectionMade method on subscription {71C38B61-EAE9-4E85-87A5-8B5CC119ADAD}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT <code>.
There are different methods that can be recorded in this event:
- ConnectionMade - notifies your application that the specified connection has been established (see ME319590 for an example)
- PostShell - See EV100110 (McAfee Article KB67381)
- RequestWriterInfo - Along with Error code 80070005 may indicate a permissions issue. See ME2005257
- greet  - See ME331692 for a detailed explanation (and a hotifx available)
From a newsgroup post: "This message is harmless. It means an application asked to be notified when you are on or offline and then didn't respond when told."

* * *

From another post: "One cause for this message to appear is Messenger not being allowed to connect when you're online. The solution is to turn off Windows Messenger to start automatically with Windows and uncheck "Allow this program to run in the  background" (under Windows Messenger Options/Preferences).

To Disable MSN Messenger Four things to do.:
Messenger, tools menu, Options uncheck the item for start at windows start.
Messenger, tools menu, Options uncheck the item for run in background.
OE, Tools menu, Options, uncheck run Messenger at startup.
Disable or don't open the 'contacts' pane in IE, and OE (OE, View menu, "customize toolbar", uncheck 'contacts bar')
(with XP Pro) Go to start/run, and type gpedit.msc open local computer policy/user configuration/administrative templates/ windows components/windows messenger doubleclick the 'do not allow windows messenger to be run' enable Note: This setting is available under both Computer Configuration and User Configuration. If both are present, the Computer Configuration version of this setting takes precedence.

* * *

T774221 (The COM+ Event System General Functionality) provides a very generic method of troubleshooting this message, regardless of the error code reported in the event description.

* * *

Error code 80004001 is the most common ones  but other codes have been reported so the troubleshooting suggestions should only be applied if the error code matches the one reported in your case. The meaning of the error code may provide additional clues in troubleshooting this issue:

Error code 80070005 = "Access denied"
Error code 80010105 = "Server exception"
Error code 80070534 = "No mapping between the account names and security ID was done"
Error code 80004001 - See EV100109 (Symantec Article: TECH101496) for a situation in which this event may occur.
Error code 80004001 - As per Microsoft: "This is a COM+ (Component Object Model) event system error related to Microsoft Windows Messenger or Microsoft MSN Messenger. The HRESULT return code specifies the type of error. For example, HRESULT 80004001 (E_NOTIMPL) indicates the subscribed event is either not implemented or is unable to reach the subscriber due to insufficient application updates". See MSW2KDB for more details.
Error code 80004001 - Please see ME319590: "This error message is caused by an error condition in a COM+ component that is related to Microsoft Windows Messenger and Microsoft MSN Messenger".

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.