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

	Product(s):	APM Implementation and Performance Management
	Version(s):	7
	Environment:	N\A
	Area:	N/A
	Subarea:	N\A

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)

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

First launch the Ivara (APM) Configuration tool. Open the Server instance running the Remote and click Configuration button > full settings. With the full settings open, choose show full 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.

If setting up the Remote Master instance from the server,

Again from the APM Configuration Tool, change the type to Remote and find and select the instance. Click the Configuration button > Full settings option. Select the Remote Setting node, scroll down to find the Remote URI. Compare this with the Server's Remote Service URL copied to the text file. If these do not match then you will need to find update the Remote instance such that it matches. Most likely the Remote Settings node will be set to "default" and not the name of the APM Service running the remotes or the Port is set incorrectly in the Mandatory Settings.

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

Lastly, if all of the instances and services appear to be installed correctly, launch the IIS Manager, highlight the Web Server and select restart. This will often resolve the issue.