0
Answered

Event Broker service won't start

Carol Wapshere 7 years ago • updated by anonymous 3 years ago 4

Installation completed but service won't start. Following two messages in Event Log:

Log Name: Application
Source: .NET Runtime
Date: 18/10/2011 9:08:38 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PRDAPP101VS.act.gov.au
Description:
Application: Unify.Service.Event.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Unify.Framework.WinEventLogWriterException
Stack:
at Unify.Framework.WinEventLogWriterBase.WriteLogEntryBase(Unify.Framework.ILogEntry)
at Unify.Framework.LogWriterBase.WriteLogEntry(Unify.Framework.ILogEntry)
at Unify.Product.EventBroker.EventBrokerService.LogServerError(Unify.Framework.ILogEntry)
at Unify.Product.EventBroker.EventBrokerService.Dispose(Boolean)
at System.ComponentModel.Component.Dispose()
at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase[])
at Unify.Product.EventBroker.EventServiceBootStrap.Main()

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-10-17T22:08:38.000000000Z" />
<EventRecordID>6256</EventRecordID>
<Channel>Application</Channel>
<Computer>PRDAPP101VS.act.gov.au</Computer>
<Security />
</System>
<EventData>
<Data>Application: Unify.Service.Event.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Unify.Framework.WinEventLogWriterException
Stack:
at Unify.Framework.WinEventLogWriterBase.WriteLogEntryBase(Unify.Framework.ILogEntry)
at Unify.Framework.LogWriterBase.WriteLogEntry(Unify.Framework.ILogEntry)
at Unify.Product.EventBroker.EventBrokerService.LogServerError(Unify.Framework.ILogEntry)
at Unify.Product.EventBroker.EventBrokerService.Dispose(Boolean)
at System.ComponentModel.Component.Dispose()
at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase[])
at Unify.Product.EventBroker.EventServiceBootStrap.Main()
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 18/10/2011 9:08:39 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: PRDAPP101VS.act.gov.au
Description:
Faulting application name: Unify.Service.Event.exe, version: 3.0.0.4, time stamp: 0x4e0ab726
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c
Exception code: 0xe0434352
Fault offset: 0x000000000000cacd
Faulting process id: 0x1b24
Faulting application start time: 0x01cc8d1940ee9977
Faulting application path: C:\Program Files\UNIFY Solutions\Event Broker\Services\Unify.Service.Event.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 90f2cc09-f90c-11e0-a4cb-005056b40047
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-10-17T22:08:39.000000000Z" />
<EventRecordID>6257</EventRecordID>
<Channel>Application</Channel>
<Computer>PRDAPP101VS.act.gov.au</Computer>
<Security />
</System>
<EventData>
<Data>Unify.Service.Event.exe</Data>
<Data>3.0.0.4</Data>
<Data>4e0ab726</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.17651</Data>
<Data>4e21213c</Data>
<Data>e0434352</Data>
<Data>000000000000cacd</Data>
<Data>1b24</Data>
<Data>01cc8d1940ee9977</Data>
<Data>C:\Program Files\UNIFY Solutions\Event Broker\Services\Unify.Service.Event.exe</Data>
<Data>C:\Windows\system32\KERNELBASE.dll</Data>
<Data>90f2cc09-f90c-11e0-a4cb-005056b40047</Data>
</EventData>
</Event>

Service account needed local Admin

Mark told me to put service account in local Admin group which resolved the issue.

As discussed - the account requires rights to log, etc. Easiest to add to local admins on the server if possible.

Granular rights are discussed here:

https://unifysolutions.jira.com/wiki/display/EB300/Prerequisites

Thanks for helping out so quickly Mark.

We suspect that the local admin was the quickest way to give the service account permissions to write to the Windows Event Log. The installer is supposed to take care of that whole logging situation, but it may only solve half of the problem. I'll create another task off this to update the documentation with this requirement, detail (if possible) the simplest way to assign this permission (ideally without requiring local admin) and hopefully to give a better error message as well.