APM Remote fails to run initialization due to Web Service being unavailable or busy.
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.
Launch the Web Monitor for the server service. From the home page, look in the Service Providers section for the Web Service Host. If the web service host is missing, have the administrator open the application to the Enterprise level > Services view > Servers tab. Find the desired service and check if the web service host is linked to the appropriate service. If not, then browse for the web service host. From the server, restart the service.
If the Synchronization Service has been configured properly and is up and running without errors, this is likely due to a configuration problem on the Remote. Here is how to verify that the settings on the remote are correct:
If the Remote was packaged and deployed, then you will need to redeploy deployment package.