The agent is killed while testing

[valilazarov]

The agent is killed while testing

[chriswendt1]

Excellent. @valilazarov, thanks for letting me know. I have checked in this change.
Your IT team can fix the problem by permitting the Azure domains in the proxy's firewall settings.

[chriswendt1]

Hi @valilazarov , thanks for the feedback. The VPN by itself should not do harm, but a firewall may be blocking access to the service URLs the client is using.
Can you add a description of what happened before the crash?

[valilazarov]

The agent is just crashing without any logs or notification. I am running on Windows 11 and wanna give a second try on a different notebook. Is it possible to see any logs? Thanks for support!

[chriswendt1]

Log is in C:\Users\user\AppData\Roaming\Document Translation\doctrLog.txt
Can you enter and [Test] your credentials? Does the test pass?

[valilazarov]

No logs available as file is not existing, the agent is crashing during testing...I suspect a VPN drop.

[chriswendt1]

Thanks.
Are you using Key Vault or entering complete credentials?
Please be as exact as possible:

1. You enter your credentials (key vault or direct?) on the Settings page
   As far as you know, those are correct credentials.
2. You press the [Test] button

App crashes.
Is that it?

[valilazarov]

I am using the complete credentials - the correct one for sure. After pressing save and testing button the app crashes.

[chriswendt1]

@valilazarov Thanks. I'll have a look.

[chriswendt1]

Hi @valilazarov,

Can you run this command on the command line and see what happens?
doctr config test

I built an unsigned version that catches some additional exceptions in the test phase. Hopefully this will reveal something.
DocumentTranslationTest 1.0.2.1.zip

Let us know what you find.

[valilazarov]

Hi @chriswendt1 - thanks a lot! The output is pointing to "Unhandled exception. System.Net.Http.HttpRequestException: The proxy tunnel request to proxy ...failed with status code '407'."" . My assumption was correct: the VPN is dropping the connections. I'll talk with the network team to allow the connections.

Thanks a lot for support!

[chriswendt1]

Thanks, @valilazarov . How did you find this? Did you have to run the updated Windows app, or was the command line enough to show you this message?

[valilazarov]

@chriswendt1 , the command line was enough.

[chriswendt1]

Thanks a lot, @valilazarov .
Could you still do me a favor and run the above attached binary version 1.0.2.1 before you change the proxy?
I expect it to not crash and instead display the proxy failure 407 message in the status bar.

[valilazarov]

Indeed. The proxy failure 407 is showned in the status bar after the update to 1.0.2.1. @chriswendt1, great job!