1. UNIFYBroker Forum
  2. Questions
0
Answered

'Unify.Framework.LDIFAdapterServiceHostDecorator' has zero application (non-infrastructure) endpoints

André van der Westhuizen 11 years ago • updated by anonymous 9 years ago • 13

When trying to start the Identity Broker Service receive the following error when using the debug:

C:\Program Files\UNIFY Solutions\Services>Unify.Service.Connect.Debug.exe
Unify.Framework.UnifyServerStartException: Service 'Unify.Framework.LDIFAdapterS
erviceHostDecorator' has zero application (non-infrastructure) endpoints. This m
ight be because no configuration file was found for your application, or because
no service element matching the service name could be found in the configuratio
n file, or because no endpoints were defined in the service element. ---> System
.InvalidOperationException: Service 'Unify.Framework.LDIFAdapterServiceHostDecor
ator' has zero application (non-infrastructure) endpoints. This might be because
no configuration file was found for your application, or because no service ele
ment matching the service name could be found in the configuration file, or beca
use no endpoints were defined in the service element.
   at System.ServiceModel.Description.DispatcherBuilder.EnsureThereAreNonMexEndp
oints(ServiceDescription description)
   at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(Se
rviceDescription description, ServiceHostBase serviceHost)
   at System.ServiceModel.ServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Unify.Framework.IdentityBrokerEngine.Start()
   at Unify.Framework.UnifyEngine.Start()
   --- End of inner exception stack trace ---
   at Unify.Framework.UnifyEngine.Start()
   at Unify.Services.Connect.Debug.ProgramProxy.Execute()

installation files.jpg
Unify.Service.Connect.exe.config
André van der Westhuizen 11 years ago

The following Identity broker 3 Software has been installed:
UNIFY Identity Broker v3.0.8 service
UNIFY Management Studio 3.0.7
UNIFY Log Studio 3.0.0
Identity Broker Service Debugger v3.0.8
UNIFY Identity Broker for Microsoft FIM v3.0.0
UNIFY Identity Broker for Marval v3.0.0
UNIFY Identity Broker for Cisco UCM v3.0.1
UNIFY Identity Broker for eNitiatives ViewDS v3.0.2
UNIFY Novell Identity Manager Identity Broker v3.0.0

André van der Westhuizen 11 years ago

Hi Patrick could you please have a look at this as a matter of urgency?

Matthew Clark 11 years ago

Hey Andre

Just saw this before and I've had a bit of experience with this. I'm assuming you're using the debugger because you're getting another error message telling you the service won't start. The debugger actually requires it's own .exe.config file, ie. "Unify.Service.Connect.Debug.exe.config". This will need to have the same contents as the "Unify.Service.Connect.exe.config" file you provided.

This point is described in https://unifysolutions.jira.com/wiki/display/IDB307/Debugger where it suggests copying the config file and renaming it with the name listed above.

Matt

Shane Day (Chief Technology Officer) 11 years ago

Changed to type "Defect" as this isn't a Client Support issue, it is a technical issue raised during the course of a project.

André van der Westhuizen 11 years ago

Hi Matt, yes you are correct we did this as the service didn't want to start and Peter Wass has created a copy of the file attached and renamed it as required and we then received the error above.

Shane Day (Chief Technology Officer) 11 years ago

I assume also that you are attempting to debug a reason for the Identity Broker service not starting. If you resolve this issue and need assistance with that, please raise another issue of type "Defect" and let me know through Lync.

Shane Day (Chief Technology Officer) 11 years ago

Please supply a directory listing of files in the services directory.

André van der Westhuizen 11 years ago

The Identity Broker 3 directory is:

C:\Program Files\Unify Solutions\Service|

The files is as follow:

Shane Day (Chief Technology Officer) 11 years ago

Unify.Service.Connect.Debug.exe.config doesn't exist. As per Matt's instructions, you need to copy the existing Unify.Service.Connect.exe.config file and rename it to Unify.Service.Connect.Debug.exe.config

André van der Westhuizen 11 years ago

The issue was that the Unify.Service.Connect.Debug.exe.config file was missing the exe part. Change the file name and the Debugger work.

André van der Westhuizen 11 years ago

Issue resolved

Matthew Clark 11 years ago

Reopening to add Affects and Fix Version

Matthew Clark 11 years ago

Issue closed

Customer support service by UserEcho