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 www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: .NET Runtime|
.NET Runtime version 4.0.30319.18052 - There was a failure initializing profiling API attach infrastructure. This process will not allow a profiler to attach. HRESULT: 0x80004005. Process ID (decimal): 3884. Message ID: [0x2509].
.NET Runtime version 2.0.50727.3082 - Failed to CoCreate profiler.
|English: Request a translation of the event description in plain English.|
For ".NET Runtime version 2.0.50727.3082 - Failed to CoCreate profiler." - If using IBM Tivoli Composite Application Manager for Transactions, see EV100453 (.NET Data Collector event 1022).
For "There was a failure initializing profiling API attach infrastructure..." - Several support forums suggest that this error is related to certain video codes. Updating them with the latest version may help fix the problem.
From a support forum: "The error is triggered by the Windows Indexing Service, when the Icaros PropertyHandler is installed. The error itself is completely harmless. It is just Microsoft .NET being stupid.
- Don't install Icaros PropertyHandler
- Disable indexing on the drives/folders that contain your media files
- Disable the Windows Indexing Service"
Several error codes (HRESULT) can be recorded with this error. Looking up the information for that particular error code may assist with the troubleshooting. Examples:
- Error code 0x80004005
- Error code 0x800700c1
- Error code 0x80070002
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated