Question

I am having difficulty reliably creating / removing event sources during the installation of my .Net Windows Service.

Here is the code from my ProjectInstaller class:

// Create Process Installer ServiceProcessInstaller spi = new ServiceProcessInstaller(); spi.Account = ServiceAccount.LocalSystem;  // Create Service ServiceInstaller si = new ServiceInstaller(); si.ServiceName = Facade.GetServiceName(); si.Description = 'Processes ...'; si.DisplayName = 'Auto Checkout'; si.StartType = ServiceStartMode.Automatic;  // Remove Event Source if already there if (EventLog.SourceExists('AutoCheckout'))     EventLog.DeleteEventSource('AutoCheckout');  // Create Event Source and Event Log      EventLogInstaller log = new EventLogInstaller(); log.Source = 'AutoCheckout'; log.Log = 'AutoCheckoutLog';  Installers.AddRange(new Installer[] { spi, si, log }); 

The facade methods referenced just return the strings for the name of the log, service, etc.

This code works most of the time, but recently after installing I started getting my log entries showing up in the Application Log instead of the custom log. And the following errors are in the log as well:

The description for Event ID ( 0 ) in Source ( AutoCheckout ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details.

For some reason it either isn’t properly removing the source during the uninstall or it isn’t creating it during the install.

Any help with best practices here is appreciated.

Thanks!

In addition, here is a sample of how I am writing exceptions to the log:

// Write to Log EventLog.WriteEntry(Facade.GetEventLogSource(), errorDetails, EventLogEntryType.Error, 99); 

Regarding stephbu’s answer: The recommended path is an installer script and installutil, or a Windows Setup routine.

I am using a Setup Project, which performs the installation of the service and sets up the log. Whether I use the installutil.exe or the windows setup project I believe they both call the same ProjectInstaller class I show above.

I see how the state of my test machine could be causing the error if the log isn’t truly removed until rebooting. I will experiment more to see if that solves the issue.

Edit: I’m interested in a sure fire way to register the source and the log name during the installation of the service. So if the service had previously been installed, it would remove the source, or reuse the source during subsequent installations.

I haven’t yet had an opportunity to learn WiX to try that route.

Answer 1

The best recommendation would be to not use the Setup Project in Visual Studio. It has very severe limitations. I had very good results with WiX