eventlog-source

Setup project for a windows service and the event log

由 旧时模样 提交于 2021-01-27 04:35:52
问题 I got a setup project that installs a windows service. We are registering a event log source in a custom log which should be used by the winservice project (how and why is not important). My problem is that the setup project tries to create an event log source per default. By doing so it get's an error message ( "Error 1001" source XXX already exists on local computer ) and rolls back. I have looked everywhere and I cannot find where the registration is done or how I can turn it off. How can

WIX: Create EventSource using .NET message file

由 一世执手 提交于 2019-12-30 05:07:06
问题 I'm creating an installer for my application using WIX. Everything works fine so far. However, I'm trying to create a new event source during installation and that doesn't work as expected. I've read and understood this question here on SO, but I have a somewhat different situation in which the given solution does not seem to work properly. The following is done differently: I'm using the WixNetFxExtension to determine whether .NET 3.5 is installed as a startup condition. I'm using the

Cannot open log for source {0} on Windows 2003 Server

由 安稳与你 提交于 2019-12-25 00:36:35
问题 I am having a huge problem with the eventlog on my server. Right let me first of all explain the setup. I have a domain setup with 2 computers One computer is running IIS the other is a workstation. The IIS is running Win2k3 the workstation Win XP. The IIS computer is hosting a website which uses Windows Impersonation and tries to log an entry to the eventlog for a custom log file called MyApp and a custom event source MySource I have a domain user called MyUser who is just a member of Domain

Simplest way to write a log message and display in Perfview

由 柔情痞子 提交于 2019-12-20 06:25:12
问题 I need the to write a log message and capture that in PerfView. I would like to avoid using EventLog or EventSource because they are quite invasive: they require registering a new source or ETW provider, which leaves leftovers in the system. Ideally I just want to call Debug.WriteLine (which uses OutputDebugString), but it seems that PerfView cannot collect it. Or is there some ETW provider that sees debug messages? If you have an answer, please state the two parts of the solution: What

How to create a .NET event log source using WiX

由 痞子三分冷 提交于 2019-12-17 19:15:58
问题 This is an intentional semi-duplicate of How do you create an event log source using WiX and WIX: Create EventSource using .NET message file. My first question is, does it really have to be so complicated? Isn't there some way to simply specify to WiX, "my program is a .Net program, and it needs to write to the event log - please do the necessary setup"? OK, assuming that isn't possible, I'd like to receive any recommendations for the necessary WiX statements to make it work, irrespective of

How do you create an event log source using WiX

由 霸气de小男生 提交于 2019-12-17 04:29:49
问题 I'm creating an installer for a website that uses a custom event log source. I would like our WiX based installer to create that event log source during installation. Does anyone know the best way to do this using the WiX framework. 回答1: Wix has out-of-the-box support for creating event log sources. Assuming you use Wix 3, you first need to add a reference to WixUtilExtension to either your Votive project or the command line. You can then add an EventSource element under a component : <Wix

Can I count on this ASP.NET event log source always being registered?

由 梦想与她 提交于 2019-12-10 11:35:35
问题 Unhandled exceptions cause ASP.NET-based applications to unexpectedly quit in the .NET Framework 2.0 makes me think that an event log source named with the following convention will always be registered on any box where the .NET Framework has been installed: "ASP.NET X.Y.Z.0" Where X, Y, and Z are the major, minor, and build numbers from the .NET runtime. Is it safe to assume that the installation of the .NET Framework will always create this event log source? 回答1: This event log source is

Can I count on this ASP.NET event log source always being registered?

由 江枫思渺然 提交于 2019-12-06 13:30:22
Unhandled exceptions cause ASP.NET-based applications to unexpectedly quit in the .NET Framework 2.0 makes me think that an event log source named with the following convention will always be registered on any box where the .NET Framework has been installed: "ASP.NET X.Y.Z.0" Where X, Y, and Z are the major, minor, and build numbers from the .NET runtime. Is it safe to assume that the installation of the .NET Framework will always create this event log source? This event log source is installed by ASP.NET as part of ASP.NET Health Monitoring . In particular, it is written to by the

How to determine if an EventLog already exists

由 孤街醉人 提交于 2019-12-05 08:32:19
问题 I'm using the following line to create a new event log new-eventlog -LogName "Visual Studio Builds" -Source "Visual Studio" I want to run this every time, because if I run a build from a new computer, I'd still like to see the event logs. The problem is that every time the script is run after the log is already created, it throws an error. New-EventLog : The "Visual Studio" source is already registered on the "localhost" computer. At E:\Projects\MyApp\bootstrap.ps1:14 char:13 + new-eventlog <

How to determine if an EventLog already exists

由 筅森魡賤 提交于 2019-12-03 22:05:29
I'm using the following line to create a new event log new-eventlog -LogName "Visual Studio Builds" -Source "Visual Studio" I want to run this every time, because if I run a build from a new computer, I'd still like to see the event logs. The problem is that every time the script is run after the log is already created, it throws an error. New-EventLog : The "Visual Studio" source is already registered on the "localhost" computer. At E:\Projects\MyApp\bootstrap.ps1:14 char:13 + new-eventlog <<<< -LogName "Visual Studio Builds" -Source "Visual Studio" + CategoryInfo : InvalidOperation: (:) [New
订阅 eventlog-source