I am using .NET controller 184.108.40.206. Recently we upgraded .Net framework version of our ASP.Net web application to .net 4.7.1 from 4.5.2. We noticed few crashes with AppD .Net agent 220.127.116.11 being installed. So we are planning to upgrade appdynamics.Net agent to 18.104.22.168.
1) When tried to install through MSI , we are able to successfully install and monitor the application in controller.
2) When tried to install through startup.cmd by invoking startup.cmd on VM- agent gets installed , role instace reboots and installation succeeds.
3) When trying to install through startup task the deployment doesn't success the role recycles and in Azure portal I can see the error message - appdynamics/startup.cmd - startup task exit wih exit code 1.
Because role is not started I am not able to RDP and get look into the logs.
My startup task runs with elevated context.
1 & 2 were tried when startup task was disabled during deployment.
I have attached screenshot of error I receive on Azure when trying to deploy.
Do you have any sugegstions on how to troubleshoot?
... View more