sdnian 6 Posted July 16, 2020 Share Posted July 16, 2020 I run the Client Task from ESMC for Software Install to Upgrading EEA 7.3, most Clients succeeded in the upgrade, but a few failed and one of them displayed the Trace Message as follows: What does that mean? ESMC Server 7.2.1266.0, Agent 7.2.1266.0, Client OS: Windows 7/10 Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted July 16, 2020 ESET Staff Share Posted July 16, 2020 Unfortunately it seems to be an issue in ESMC Agent not able to handle trace messages. Any chance full msiexec log from those installations is available (in standard AGENT logs directory) for analysis? There is probably issue with encoding - I guess that installation was performed on operating system with non-latin locale? Link to comment Share on other sites More sharing options...
sdnian 6 Posted July 16, 2020 Author Share Posted July 16, 2020 6 hours ago, MartinK said: Unfortunately it seems to be an issue in ESMC Agent not able to handle trace messages. Any chance full msiexec log from those installations is available (in standard AGENT logs directory) for analysis? There is probably issue with encoding - I guess that installation was performed on operating system with non-latin locale? This is one of the clients that failed to upgrade, the error message is in Chinese, this kind of message also appeared before, why this is an Invalid utf8 leading byte? software-install.log Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted July 16, 2020 ESET Staff Share Posted July 16, 2020 3 hours ago, sdnian said: This is one of the clients that failed to upgrade, the error message is in Chinese, this kind of message also appeared before, why this is an Invalid utf8 leading byte? software-install.log 166.53 kB · 0 downloads Thanks for logs. We are currently not sure but most probable reason is that either message is cut-off (there is maximal length) in wrong place and thus rendering string as invalid, or there is a problem with conversion of data as reported by system. Link to comment Share on other sites More sharing options...
sdnian 6 Posted July 17, 2020 Author Share Posted July 17, 2020 12 hours ago, MartinK said: Thanks for logs. We are currently not sure but most probable reason is that either message is cut-off (there is maximal length) in wrong place and thus rendering string as invalid, or there is a problem with conversion of data as reported by system. This issue seems to have occurred after I upgraded ESMC 7.2, maybe there is a tweak or something in the new version that is causing this problem. Link to comment Share on other sites More sharing options...
Recommended Posts