There was no endpoint listening at

Problem

You find this error in the ZervicePoint log

Log Name:      ZervicePoint
Source:        Provisioning system service
Date:          2/4/2014 9:04:12 AM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:
Description:
Timestamp: 09:04:12.161

Message: Could not get next job:
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at [https://zervicepoint.domain.local:9900/ProcessSystem/ProvisioningService.svc](https://zervicepoint.domain.local:9900/ProcessSystem/ProvisioningService.svc) that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory\`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

   --- End of inner exception stack trace ---

Server stack trace:
   at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
   at System.ServiceModel.Channels.HttpChannelFactory\`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.SecurityChannelFactory\`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Zipper.ZervicePoint.ProcessSystem.Contracts.IProvisioning.GetNextProvisioningJob(String storeName)
   at Zipper.ZervicePoint.ProvisioningSystem.Engine.WorkerEngine.GetNextProvisioningJob()

Category: Provisioning
Priority: -1
EventId: 0
Severity: Error
Title:
Machine:
Application Domain: Zipper.ZervicePoint.ProvisioningSystem.Service.exe
Process Id: 1120
Process Name: C:\Program Files\Zipper\ZervicePoint\ProvisioningSystem\Zipper.ZervicePoint.ProvisioningSystem.Service.exe
Win32 Thread Id: 1532
Thread Name:
Extended Properties:
Event Xml:

  <System>
    <Provider Name="Provisioning system service" />
    <EventID Qualifiers="0">0</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-04T08:04:12.000000000Z" />
    <EventRecordID>136467</EventRecordID>
    <Channel>ZervicePoint</Channel>
    <Computer>s0004618.ecdomain.net</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Timestamp: 09:04:12.161

Message: Could not get next job:
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at [https://zervicepoint.domain.local:9900/ProcessSystem/ProvisioningService.svc](https://zervicepoint.domain.local:9900/ProcessSystem/ProvisioningService.svc) that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. --- System.Net.WebException: The remote server returned an error: (404) Not Found.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory\`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

   --- End of inner exception stack trace ---

Server stack trace:
   at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
   at System.ServiceModel.Channels.HttpChannelFactory\`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.SecurityChannelFactory\`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData msgData, Int32 type)
   at Zipper.ZervicePoint.ProcessSystem.Contracts.IProvisioning.GetNextProvisioningJob(String storeName)
   at Zipper.ZervicePoint.ProvisioningSystem.Engine.WorkerEngine.GetNextProvisioningJob()

Category: Provisioning
Priority: -1
EventId: 0
Severity: Error
Title:
Machine: S0004618
Application Domain: Zipper.ZervicePoint.ProvisioningSystem.Service.exe
Process Id: 1120
Process Name: C:\ProgramFiles\Zipper\ZervicePoint\ProvisioningSystem\Zipper.ZervicePoint.ProvisioningSystem.Service.exe
Win32 Thread Id: 1532
Thread Name:

Extended Properties:

    </Data>
  </EventData>
</Event>

Solution

  1. Open the ADFS console.
  2. Add relying party trust according to attatched image.
  3. This should solve your problem.

ADFS Enable WF federation

If you get a 404 when trying to access the :9900/ProcessSystem/ProvisioningService.svc :

ProvisioningSystem.svc

Check Server Manager if HTTP Activation under .NET Framework 4.5 is enabled.

http activition

Troubleshooting guidelines

ZervicePoint event log errors and warnings with unique event Ids