Since the end of the 14 day trial the monitor has failed conect to my Pc and shows it off line.When I try to validate account I get a message "There is no endpoint listening at "

The 14 day trial is for server modules only - you can continue to use the app to monitor 3 computers for free with no time limitation.

Please start the PC Monitor Manager installed on your PC and press the "Validate Account" button. What is the result?

If I click on any of the buttons under the password I get the error message There is no endpoint listening at https://ws16,pulseway.com/server.svc that could accept the message.This is often caused by an incorrect address or SOAP action,

If you open that Url in a web browser what is the result?

The conection just times out.

That means your computer cannot reach our servers - the connection might be blocked by something (antivirus, firewall).

Thank you for your help,I have just set the firewall to allow PC monitor,now all is Ok

You're welcome, glad it works - thanks for the update.

I have same problem, on one of my servers, win 2003 32 bit, on same subnet is there already one server up and running perfect, this machine give the same error (no endpoint on https://ws7.pulseway.com/Server.svc but if i open link in IE i ger this 

 

 

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.

Can you please enable the diagnostic logging in the Manager app, start the PC Monitor service and after about 3-4 minutes send us the trace.log file that can be found in the PC Monitor installation folder? Please send that log to support at pulseway.com 

 

Thanks!