Upgraded dynaTrace client to 5.6.0.5802 problems
Yesterday we updated the dynaTrace 5.5.5562 to dynaTrace 5.6.5713.
We installed the dynaTrace client 5.6.0.5713 as well and everything OK.
Today we applied the dynaTrace update 5.6.0.5802. After the update was finnished and we start the dynaTrace client 5.6.0.5713 (installed, not web start) it tells us it is out of date and needed updates. Fine! Update is OK and working as expected. We can start the client normally every time.
Without doing anything with the patched dynaTrace 5.6.0.5802 version we uninstalled the dynaTrace client 5.6.0.5713 and installed dyanTrace client 5.6.0.5802 instead. A pop-up appear after starting telling there are updates at the server - do you want to update Yes/Not now/ Never. We click Yes and it is updated and dashboards are displayed.
Next time we start the dynaTrace client it asks again to update! This is annoying....
As a test we tried to update directly from from dynaTrace 5.5.6.5562 to dynaTrace 5.6.0.5802 (VM Ware so we went back to snapshot with 5.5 installed) and then installed the dynaTrace client 5.6.0.5802 directly and started it. This time there is no pop-up tellling there are updates on the server...
We have tried it on several installations with same result so no support information is attached. Should be possible to reproduce your self by update DT 5.5 to 5.6.0.5713 - patch it to 5.6.0.5802 and install DT client 5.6.0.5802 and start it...
Is this a BUG?
-Tore
I saw that you logged a case so we will investigate as part of that, until then a workaround should be to run the dynaTrace Client as administrator once and do the upgrade. Sometimes Windows User Access Control (UAC) settings interfere with the update process and cause storing of update-files to fail.
Thanks... Dominik
Hi and thank you for your update.
Start the dynaTrace client with run as administrator gave the question again (first time) and then it asked me to restart.
After restart it restarted without any questions to update.
We then started the client again without run as administrator and got the question again to update... Clicked yes and an error message occured:
'Synchronizing plugins' has encountered a problem
An internal error occurred while running bundle update
So I think there is more to look into 
Have a nice weekend!
-Tore
Hi,
Is there a fix for this issue yet? While I have admin priveleges and can run the client in administrator mode to get the fixpack, many of my users of dynaTrace internally don't currently.
Hello Jay,
this issue is fixed in dynaTrace 6.0, which was released today.
Regarding solutions for 5.6, we have the following workarounds:
- Once per update solutions: Run Client as admin OR set User Account Control to "Never notify"
- Permanent solution: As Admin, manually set write permissions for all users in the dynaTrace installation "DT_HOME/client/update" folder, afterwards, all users should be able to update the client.
Hope that helps,
Thomas
Once again, both of those workarounds require admin privileges, which many of my users don't have.
Is there a back ported fix for v5.6 that's available to address the issue since it was addressed in v6?
Hello Jay,
the problem is that to install the fix for the permissions issue, you would need admin privileges as well, so it would defeat the purpose.
However, we can provide a new agent installer which has this issue fixed, which basically sets the permissions during installation, but of course this requires also Admin privileges, but only once. If you want this solution, please contact support and reference this conversation and tell them to contact me for the file delivery.
This is kind of a chicken-egg problem situation, as we cannot get more privileges without having the Admin granting them at some point.
Regards,
Thomas
EMEA Community Member of the Month - November 2018
Announcing Dynatrace's EMEA Community Member of the Month for November 2018, Mathieu C.! Click here to read more! LATAM Community Member of the Month - November 2018
Announcing Dynatrace's LATAM Community Member of the Month for November 2018, Rene S.! Click here to read more! 
