我注意到当我在NServiceBus.host.exe上调用/ install标志时,会在Application事件日志下创建一个事件日志源。问题是,我们已将NServiceBus L4N配置为将事件写入同一源但在自定义事件日志下。
这会导致问题,因为如果我们在自定义事件日志下创建源,则安装失败(NserviceBus安装程序抛出System.ArgumentException:本地计算机上已存在Source blah)。
那么我们如何阻止NServiceBus安装程序尝试在应用程序事件日志下创建事件源?
我们正在使用NServiceBus 3.0.1.0
由于
编辑 - 完整的堆栈跟踪
Creating EventLog source blah in log Application...
An exception occurred during the Install phase.
System.ArgumentException: Source blah already exists
on the local computer.
The Rollback phase of the installation is beginning.
Restoring event log to previous state for source blah
.
Service blah is being removed from the system...
Service blah was successfully removed from the system
.
The Rollback phase completed successfully.
Unhandled Exception: System.InvalidOperationException: The installation failed, and the rollback has been performed. ---> System.ArgumentException: Source blah already exists on the local computer.
at System.Diagnostics.EventLog.CreateEventSource(EventSourceCreationData sourceData)
at System.Diagnostics.EventLogInstaller.Install(IDictionary stateSaver)
at System.Configuration.Install.Installer.Install(IDictionary stateSaver)
at System.ServiceProcess.ServiceInstaller.Install(IDictionary stateSaver)
at System.Configuration.Install.Installer.Install(IDictionary stateSaver)
at Topshelf.Internal.Hosts.HostServiceInstaller.Install(IDictionary stateSaver)
in d:\dev\open-source\topshelf\src\Topshelf\Internal\Hosts\HostServiceInstaller.cs:line 120
at System.Configuration.Install.Installer.Install(IDictionary stateSaver)
at System.Configuration.Install.TransactedInstaller.Install(IDictionary savedState)
--- End of inner exception stack trace ---
at System.Configuration.Install.TransactedInstaller.Install(IDictionary savedState)
at Topshelf.Internal.Hosts.HostServiceInstaller.Register() in d:\dev\open-source\topshelf\src\Topshelf\Internal\Hosts\HostServiceInstaller.cs:line 61
at Topshelf.Internal.Actions.InstallServiceAction.Do(IRunConfiguration configuration) in d:\dev\open-source\topshelf\src\Topshelf\Internal\Actions\InstallServiceAction.cs:line 42
at Topshelf.Runner.Host(IRunConfiguration configuration, String[] args) in d:\dev\open-source\topshelf\src\Topshelf\Runner.cs:line 70
at NServiceBus.Hosting.Windows.Program.Main(String[] args) in d:\BuildAgent-03\work\nsb.masterbuild1\src\hosting\NServiceBus.Hosting.Windows\Program.cs:line 122
答案 0 :(得分:2)
如果我们使用与端点名称相同的事件源名称配置Log4net,则只会出现此问题。
因此我们可以在事件日志中使用不同的源名称(在我们的例子中为<endpoint-name>.l4n
)。这将解决现在的问题。
答案 1 :(得分:2)
如果事情变得非常梨形,您可以在注册表中找到事件日志源
HKLM/SYSTEM/ControlSet001/services/eventlog/...
从那里,您可以手动删除不再需要的事件日志源。