He is certified in several technologies and is 1 of 63 people globally that is a recipient of the prestigious Citrix Technology Professional (CTP) award. He is an Author, Speaker, and Local User Group Community Leader. He also has an extensive background in web architecture and networking over his 20+ year career in IT. Jason Samuel lives in Houston, TX with a primary focus on strategic advisory and architecture of end-user computing, security, enterprise mobility, virtualization, and cloud technologies from Citrix, Microsoft, & VMware. If you followed the steps in this blog post, it should write the event just fine. You should get a message saying it was successfully written or you should get an error message with details on why it was not written. If your application is not writing events to your new log, test it manually by opening a command prompt and going to:Įventcreate /l CustomLog /t Information /so Application1 /id 1 /d "Test message" When it’s back up, check and see if your new event log appears under Event Viewer. NET 2.0 event log message dll:Ĭ:\WINDOWS\Microsoft.NET\Framework\v7\EventLogMessages.dll I have to create a string value called EventMessageFile and give it the path to the.
You will also notice my custom app in this example is a. If it is a custom source, you need to create a DWORD value under this key with the value of 1: MAKE SURE to delete it from Application after you add it to the Custom log or it will not write events to your new log since Windows thinks its still associated with the Application log. There’s no copy/paste command so you can recreate the key if it’s small or you can export/import if it’s something complicated and you are afraid of mistyping something.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\CustomLog HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\ApplicationĪnd copy whatever key you see in there for your app under your new Custom log:
0 kommentar(er)
