[There was no endpoint listening at https://..... when validating account]

Calin,

 

I have 10 servers and 2 win7 pc's. And on all servers Win2008R2 x64 nad win7 SP1 x64 the agent runs ok. On the systems with Win2003R2 SP2 x86 I get the erors.There is no firewall running and the proxy settings are OK. I double checked it. Do you have any suggestions?

 

Regards Roy

[There was no endpoint listening at https://..... when validating account]

Service

 

 

 

This is a Windows© Communication Foundation service.

 

 

Metadata publishing for this service is currently disabled.

 

 

If you have access to the service, you can enable metadata publishing by completing the following steps to modify your web or application configuration file:

 

 

1. Create the following service behavior configuration, or add the <serviceMetadata> element to an existing service behavior configuration:

 

 

<behaviors>

 

    <serviceBehaviors>

 

        <behavior name="MyServiceTypeBehaviors" >

 

            <serviceMetadata httpGetEnabled="true" />

 

        </behavior>

 

    </serviceBehaviors>

 

</behaviors>

 

 

2. Add the behavior configuration to the service:

 

 

<service name="MyNamespace.MyServiceType" behaviorConfiguration="MyServiceTypeBehaviors" >

 

 

Note: the service name must match the configuration name for the service implementation.

 

 

3. Add the following endpoint to your service configuration:

 

 

<endpoint contract="IMetadataExchange" binding="mexHttpBinding" address="mex" />

 

 

Note: your service must have an http base address to add this endpoint.

 

 

The following is an example service configuration file with metadata publishing enabled:

 

 

<configuration>

 

    <system.serviceModel>

 

 

        <services>

 

            <!-- Note: the service name must match the configuration name for the service implementation. -->

 

            <service name="MyNamespace.MyServiceType" behaviorConfiguration="MyServiceTypeBehaviors" >

 

                <!-- Add the following endpoint.  -->

 

                <!-- Note: your service must have an http base address to add this endpoint. -->

 

                <endpoint contract="IMetadataExchange" binding="mexHttpBinding" address="mex" />

 

            </service>

 

        </services>

 

 

        <behaviors>

 

            <serviceBehaviors>

 

                <behavior name="MyServiceTypeBehaviors" >

 

                    <!-- Add the following element to your service behavior configuration. -->

 

                    <serviceMetadata httpGetEnabled="true" />

 

                </behavior>

 

            </serviceBehaviors>

 

        </behaviors>

 

 

    </system.serviceModel>

 

</configuration>

 

 

For more information on publishing metadata please see the following documentation: http://go.microsoft.com/fwlink/?LinkId=65455.

[There was no endpoint listening at https://..... when validating account]

Only with the x86 software I get the errors! This is the log:

 

12-2-2014, 13:57:28.627: [service] System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://ws5.pulseway.com/Server.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: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 212.0.177.130:8080

 

   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

 

   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)

 

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

 

   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)

 

   at System.Net.HttpWebRequest.GetRequestStream()

 

   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()

 

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

 

 

Server stack trace:

 

   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()

 

   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)

 

   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)

 

   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)

 

   at System.ServiceModel.Dispatcher.RequestChannelBinder.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 MM.Monitor.Service.ServerService.IServer.CheckForUpdate(Int32 computerType, String currentVersion)

 

   at .(Int32 )

 

   at .(Boolean )

[There was no endpoint listening at https://..... when validating account]

Calin,

 

On the server I get: 403 -forbidden: access is denied. You do not have permission...

 

On my own laptop outside the network I get the same.

 

Regards Roy

[There was no endpoint listening at https://..... when validating account]

 Dear Support,

 

When installing the latest version of the agent I get an error only on the x86 version of the program. The x64 gives no problem.

 

The problem is when Validating the account which I get only on the x86 version: There was no endpoint listening at http://..

 

Proxy setting are ok and I can get on evry HTTPS site on port 443