Failed to post WebApp (using JET) via Eikon App Engine to PROD / DHCP

philip.perrault

I am not on the IME. The app runs locally just fine. Note that c:\EAE\Logs\Gateway.svclog says there is a broken pipe. Below is the EAE console output, note that even though there are tracebacks showing the failure at the end it still said successfully published ************************************************ Environment: DTCP Package Type: App App Type: WebApp Directory: C:\EAE\data\1.0.9.6702\apps\Level1BlotterApp\1.0.1 ************************************************ Authenticating Token: AQIC5wM2LY4SfcyylSt9JWKgMxDIY5ZLoymmfeiDcDvgLgE=@AAJTSQACNDAAAlNLAAotNTYyODEyOTEyAAJTMQACMTc=# Skipping file 'C:\EAE\data\1.0.9.6702\apps\Level1BlotterApp\1.0.1\Manifest.xml'. Skipping file 'C:\EAE\data\1.0.9.6702\apps\Level1BlotterApp\1.0.1\ThomsonReuters.Eikon.Level1BlotterApp.pdb'. Size on disk before compression: 0.57 MB Size on disk after compression: 0.67 MB Executing eem_deploy System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at
https://emea1.views1.cp.ime.reuters.com/deployment that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote name could not be resolved: '
emea1.views1.cp.ime.reuters.com' at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at System.Net.HttpWebRequest.GetRequestStream() at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream() --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream() at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) 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 EikonEnvManager.DeploymentUtility.DeploymentService.IDeploymentService.Deploy(DeployableUnit request) at EikonEnvManager.DeploymentUtility.DeploymentService.DeploymentServiceClient.EikonEnvManager.DeploymentUtility.DeploymentService.IDeploymentService.Deploy(DeployableUnit request) at EikonEnvManager.DeploymentUtility.DeployUtil.Deploy() Successfully published from C:\EAE\data\1.0.9.6702\apps\Level1BlotterApp\1.0.1 to DTCP

philip.perrault

I was able to successfully deploy this app from another machine that is on the IME (Reuters network) but the app does not run on my IME machine.

On my Non-IME machine the application runs fine but cannot deploy

gregory.machon

Hi Philip You can contact App Server Support via email
Thomson-EikonAppServerSupport@thomsonreuters.com or on the hub: https://thehub.thomsonreuters.com/groups/ui-toolkit-application-server-team-resources From my experience I was always deploying from a machine on the IME or connected to TR network via VPN.