Connection to host is not available or migration agent is not running on the source host.

Refers to:

  • Plesk 12.0 for Windows

Created:

2016-11-16 12:41:54 UTC

Modified:

2016-12-21 19:00:09 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Connection to host is not available or migration agent is not running on the source host.

Symptoms

Plesk on source server is running with Turkish locale.

Error message when trying to start new migration:

Connection to host is not available or migration agent is not running on the source host.

The following message can be found in migration.log :

[2014-07-23 17:40:31.860|3908] Debug: ForeignMigratorCore.WinAgentIsNotRunningException ---> System.Runtime.Remoting.RemotingException: Requested Service not found

Server stack trace:
at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)

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 ForeignMigratorCore.ICredentialsChecker.CheckCredentials(String user, String password)
at CrossSysAgentSup.CrossSysAgent.deployScoutToWindowsHost(ConnectionParameters connParams)
— End of inner exception stack trace —
at CrossSysAgentSup.CrossSysAgent.deployScoutToWindowsHost(ConnectionParameters connParams)
at CrossSysAgentSup.CrossSysAgent.DeployScout(ConnectionParameters connParams)
at PsaMigrMng90.MigrMng90.DeployScout(ConnectionParameters connParams)
at migrmng.App.deployScout(ConnectionParameters connParams, Boolean removeConfigDir)
at migrmng.App.Main(String[] args)
[2014-07-23 17:40:31.860|3908] Debug: Saving result...
[2014-07-23 17:40:31.860|3908] Debug: migrmng exits with code 12

Cause

The issue is caused by software issue with ID PPPM-1842 , it was fixed in Plesk 12 MU#11 .

Resolution

Apply latest Plesk microupdates .

Have more questions? Submit a request
Please sign in to leave a comment.