If you are Installing Microsoft TFS 2010 RC or RTM, you may notice after the installation a warning that IISRESET failed.  The warning instructs you to run it manually.  Running it manually results in the same error:

The system cannot find the file specified. (2147942402, 80070002)

IISRESET failing is not a problem for TFS, but nevertheless you may want to address this.  To fix it, open Add / Remove Programs (appwiz.cpl) and run Repair on the .NET 4.0 Client component.  This requires a reboot.

If you should receive this error Message, just go switching the .NET Framework Version for the affected Application Pool under IIS.

Error: The application pool that you are trying to use has the ‘managedRuntimeVersion’ property set to ‘v2.0′. This application requires ‘v4.0′.
Error count: 1.

Open IIS

Navigate to the affected Server, Select Application Pools. Now double-click the DefaultAppPool and choose .NET Freamework v4.0.21006 (Beta2 atm)

Screenshot

you’re done!

using the following snippet in my code:

EventLog evtLog = new EventLog();
evtLog.Source = "DEMO.Web";
evtLog.WriteEntry("TEST");

(ASP Handler Class) – (.ashx extension) resulted in a:

Server Error in ‘/DEMO/test’ Application.

Security Exception

Description: The application attempted to perform an operation not allowed by the security policy.  To grant this application the required permission please contact your system administrator or change the application’s trust level in the configuration file.
Exception Details: System.Security.SecurityException: The source was not found, but some or all event logs could not be searched.  Inaccessible logs: Security.

Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:
[SecurityException: The source was not found, but some or all event logs could not be searched.  Inaccessible logs: Security.]
System.Diagnostics.EventLog.FindSourceRegistration(String source, String machineName, Boolean readOnly) +563
System.Diagnostics.EventLog.SourceExists(String source, String machineName) +264
System.Diagnostics.EventLog.VerifyAndCreateSource(String sourceName, String currentMachineName) +84
System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData) +377
System.Diagnostics.EventLog.WriteEntry(String message) +36
DEMOProject.Web.DEMO.ProcessRequest(HttpContext context) in D:\Development\DEMO.ashx.cs:25
System.Web.CallHandlerExecutionStep.System.Web.
HttpApplication.IExecutionStep.Execute() +599
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171

I searched for a while until i found this one here:

Network Service is allowed to write to the Event Log, but not create an event source. you could give permissions to HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\ to allow it to create – but if you’ve already created it at install time, there’s no need.

It’s possible that it’s failing on the SourceExists as well – since that requires enumerating the same registry key. I’d probably just remove the SourceExists/Create check and trust that it’s there – if you’re anonymous, you can’t create it anyway.

So i just added the Network Service Account to the EventLog Key granting Full Control for the key and all of its sub keys.

Path is:

Screenshot:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog

Screenshot:

Now we’re almost done. Now, don’t forget to create the corresponding Application-Event-Source-Whatever-Key! In this case/example the Key is named: DEMO.Web

Screenshot:

Now, try it again, logging to Event Manager should be working fine..