0
Answered

IdB 4.0.0.3 service cannot start.

Sam Wang 6 years ago • updated by anonymous 3 years ago 5

Following error occurs when starting IdB service.

---------------------------
Services
---------------------------
Windows could not start the UNIFY Identity Broker v4.0.0 RTM service on Local Computer.



Error 1053: The service did not respond to the start or control request in a timely fashion.


---------------------------
OK 
---------------------------

Two additional error message is logged in Event Viewer:

=================Error One===================
Log Name:      Application
Source:        .NET Runtime
Date:          31/10/2012 4:07:01 PM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FIMDEVSVC01.education.vic.gov.au
Description:
Application: Unify.Service.Connect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException
Stack:
   at Unify.Service.ConnectServiceBootStrap.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="2012-10-31T05:07:01.000000000Z" />
    <EventRecordID>1983</EventRecordID>
    <Channel>Application</Channel>
    <Computer>FIMDEVSVC01.education.vic.gov.au</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: Unify.Service.Connect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException
Stack:
   at Unify.Service.ConnectServiceBootStrap.Main()
</Data>
  </EventData>
</Event>
=================Error One===================


=================Error Two===================
Log Name:      Application
Source:        Application Error
Date:          31/10/2012 4:07:01 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FIMDEVSVC01.education.vic.gov.au
Description:
Faulting application name: Unify.Service.Connect.exe, version: 4.0.0.3, time stamp: 0x504eab1b
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17932, time stamp: 0x503285c2
Exception code: 0xe0434352
Fault offset: 0x000000000000caed
Faulting process id: 0x990
Faulting application start time: 0x01cdb7258fb5990c
Faulting application path: C:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: cd706c6b-2318-11e2-acf5-0050568b6a1c
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="2012-10-31T05:07:01.000000000Z" />
    <EventRecordID>1984</EventRecordID>
    <Channel>Application</Channel>
    <Computer>FIMDEVSVC01.education.vic.gov.au</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Unify.Service.Connect.exe</Data>
    <Data>4.0.0.3</Data>
    <Data>504eab1b</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.17932</Data>
    <Data>503285c2</Data>
    <Data>e0434352</Data>
    <Data>000000000000caed</Data>
    <Data>990</Data>
    <Data>01cdb7258fb5990c</Data>
    <Data>C:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect.exe</Data>
    <Data>C:\WINDOWS\system32\KERNELBASE.dll</Data>
    <Data>cd706c6b-2318-11e2-acf5-0050568b6a1c</Data>
  </EventData>
</Event>
=================Error Two===================

Additional, there is only one .dll file under C:\Program Files\UNIFY Solutions\IdentityBroker\Services\. The name is "CassiniDev4-lib.dll"

Affected Versions:
Fixed by Version:

Hi Sam,

My understanding is you've resolved this now. Can you please detail what steps you took in order to fix it.

Hi Patrick,

This problem is actually fixed by Huu.
From my understanding, the cause is that the account used does not have enough privilege to start the service.
Service started with no problem after Huu change the credential.

I will get Huu to confirm on this.

I've now assigned this to Huu so that he can respond with the resolution.

Resolution: add the service account to the admin group. The cause is the account does not have permission below:

  • Permission to write to the Windows Event Log.

Just for future reference, it's best to assign those permissions individually, as simply making the service account an administrator account is forbidden in most production environments.