Problem

APM Remote fails to run initialization due to Web Service being unavailable or busy.

Solution

Check the RemoteSynchronizer log. If the error log entry contains the following:

2018-06-20 18:58:10.1395Z Error Joe.Marin Ivara.Replication.Remote.Synchronizer.Client [9] Synchronization Failure EXCEPTION OCCURRED:EndpointNotFoundException There was no endpoint listening at http://xxxxxx.bentley.com/remotesvc/RemoteService/Synchronize that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Server stack trace: ...

...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)

Messages of this type indicate that the web service is busy or unavailable.  

If the Synchronization Service has been configured properly and is up and running without errors, this is likwly due to a configuration problem on the Remote.  Here is how to verify that the settings on the remote are correct:

1. On the machine running the synchronization Server instance, launch the Ivara (APM) Configuration tool .  Find the Server Instance used for Synchronizaation, click Configuration button > full settings. With the full settings open, choose show Advanced settings. Open the Service Providers node and scroll down to expose the Remote Base URL, copy it to a text document for later reference. Close the Full settings for the Service.
2. On the machine with where setting up the Remote Master instance, launch the Ivara (APM) Configuration tool.  Find the Remote instance to be updated, click the Configuration button > Full settings option.
   1. In Mandatory Settings, under Network node, ensure that the Application Server Address property is set to the machine name of the Server running the synchronization Service.  Check that the protocol and port #'s are also correct (see the machine name portion of the address saved in step #1)
   2. In the Remote Setting node, scroll down to find the Remote Server Instance.  Make sure this is set to the name of the Server Service Instance running the synchronization.  Most likely the Remote Settings node will be set to "default" and not the name of the APM Service, it must be updated.  Save and exit.
   3. go back into Full Settings, to the Remote Settings/Remote Server URI, it should now match the Server's Remote Service URL copied to the text file in step #1.

If the Remote was packaged and deployed, then you will need to redeploy deployment package.