Application as also installation DO NOT RUN and tells me to contact support

lavio@gigalink.com.br
12 Jul 2018, 05:45

RE:

Let me tell you a bit more about this error...

In another computer using Windows, where I had a backup, the first time I run CTrader it started the last update (from a 3 to another new 3.xxx) and it ALSO had the SAME ERROR.
Then I insisted using a CAlgo FxPro old link, it downloaded again the new update, and it worked using two versions of CTrader for ICM Markets and FxPro.
I had the impression that when updating from version 3 to a new last 3 it crashes. And when I updated from 2 to 3 it worked.

To continue doing what I as doing with CTrader, I had to run CTrader (and do the upgrade to version 3 from a version 2) in a second Windows installation I have in the same computer.
The point is that in the old Windows I wanted to run (because of a SSD drive) it refuses even to install the application ! It downloads the files, but at first execution attempt, it says it cannot run the apllication and tells me to contact support using a details log file (as message above).

lavio@gigalink.com.br said:

I use CTrader for about 3 years. But... after last CTRader 3 update, it says cannot run application and tells me to contact CTrader support with a details file below (written in Portuguese).
Notice: I have even uninstalled the product, downloaded the last setup. But also the setup says it cannot run the application.

LOG ERROR FILE to support below:
I guess the main info is this one:

* Activation exception http://fxpro.ctrader.com/xTrader-FxPro.application. The following error messages were detected: + Invalid connection data format of application. (HRESULT excpetion: 0x800736B2)

The log:

INFORMAÇÕES SOBRE VERSÕES DE PLATAFORMAS

Windows : 10.0.17134.0 (Win32NT)

Common Language Runtime : 4.0.30319.42000

System.Deployment.dll : 4.7.3056.0 built by: NET472REL1

clr.dll : 4.7.3131.0 built by: NET472REL1LAST

dfdll.dll : 4.7.3056.0 built by: NET472REL1

dfshim.dll : 10.0.17134.1 (WinBuild.160101.0800)

 

ORIGENS

URL da Implantação : http://fxpro.ctrader.com/xTrader-FxPro.application

Servidor : nginx/1.8.0

URL do Provedor de Implantação : http://fxpro.ctrader.com/xTrader-FxPro.application

Servidor : nginx/1.8.0

URL do Aplicativo : https://sdl.ctrader.com/fxpro/cTrader%20AppFiles/3.0.65534.35392/xTrader.exe.manifest

Servidor : nginx/1.8.0

 

IDENTIDADES

Identidade da Implantação : xTrader - FxPro, Version=3.0.65534.35392, Culture=neutral, PublicKeyToken=37dabdf737419672, processorArchitecture=msil

Identidade do Aplicativo : xTrader - FxPro, Version=3.0.65534.35392, Culture=neutral, PublicKeyToken=37dabdf737419672, processorArchitecture=msil, type=win32

 

RESUMO DO APLICATIVO

* Aplicativo instalável.

* O parâmetro da URL de confiança está definido.

RESUMO DOS ERROS

Um resumo dos erros pode ser encontrado a seguir. Os detalhes desses erros são relacionados posteriormente no log.

* Exceção na ativação de http://fxpro.ctrader.com/xTrader-FxPro.application. As seguintes mensagens de erro foram detectadas:

+ O formato de dados de ligação de aplicativo é inválido. (Exceção de HRESULT: 0x800736B2)

 

RESUMO DA FALHA DA TRANSAÇÃO DE ARMAZENAMENTO DO COMPONENTE

Nenhum erro de transação foi detectado.

 

AVISOS

Não houve avisos durante esta operação.

 

STATUS DO ANDAMENTO DA OPERAÇÃO

* [11/07/2018 23:06:41] : A ativação de http://fxpro.ctrader.com/xTrader-FxPro.application foi iniciada.

* [11/07/2018 23:06:45] : O processamento do manifesto da implantação foi concluído com êxito.

* [11/07/2018 23:06:45] : A instalação do aplicativo foi iniciada.

* [11/07/2018 23:06:45] : O processamento do manifesto do aplicativo foi concluído com êxito.

* [11/07/2018 23:06:48] : Encontrada versão 4.0.30319 do runtime compatível.

* [11/07/2018 23:06:48] : A solicitação de confiança e de detecção da plataforma foi concluída.

* [11/07/2018 23:07:39] : O download das dependências da inscrição foi concluído.

* [11/07/2018 23:07:39] : A confirmação do aplicativo baixado foi iniciada.

 

DETALHES DOS ERROS

Os erros a seguir foram detectados durante esta operação.

* [11/07/2018 23:07:39] System.Runtime.InteropServices.COMException

- O formato de dados de ligação de aplicativo é inválido. (Exceção de HRESULT: 0x800736B2)

- Origem: System.Deployment

- Rastreamento de pilha:

em System.Deployment.Internal.Isolation.IEnumSTORE_ASSEMBLY.Next(UInt32 celt, STORE_ASSEMBLY[] rgelt)

em System.Deployment.Internal.Isolation.StoreAssemblyEnumeration.MoveNext()

em System.Deployment.Application.ComponentStore.CollectCrossGroupApplications(Uri codebaseUri, DefinitionIdentity deploymentIdentity, Boolean& identityGroupFound, Boolean& locationGroupFound, String& identityGroupProductName)

em System.Deployment.Application.SubscriptionStore.CommitApplication(SubscriptionState& subState, CommitApplicationParams commitParams)

em System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)

em System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)

em System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)

--- Fim do rastreamento de pilha do local anterior onde a exceção foi gerada ---

em System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

em System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)

em System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

 

DETALHES DA TRANSAÇÃO DE ARMAZENAMENTO DO COMPONENTE

Nenhuma informação de transação está disponível.

 

PanagiotisCharalampous
16 Jul 2018, 15:01

Hi Lavio,

Can you try performing a clean installation? 

Best Regards,

Panagiotis

lavio@gigalink.com.br
16 Jul 2018, 22:40

RE:

Panagiotis Charalampous said:

Hi Lavio,

Can you try performing a clean installation? 

Best Regards,

Panagiotis

Yes, it was one of the first things I did manually. And it did not work first time.

But now, after reading the instructions to do a clean installation about, I did two new things: removed the "2.0" directory and run a NetFxRepairTool from Microsoft.
And this time it worked.

Thanks for your help.

Lavio