Skip to main content
InSource Solutions

74870 - Trend Application Impossible Error Adding Server


Multiple Terminal servers Trend works on all but one. Client tries to add the server in trend using the sa account (validated working on another node) but is prompted with : Impossible! The server was not added at ArchestrA.HistClient.UI.aaServerListConfigurator.btnAddUpdate ... aaLoger Also happens from the Excel add in and Query same message locks up the software. Partially working if logged in as administrator.

Version: 2017

Service Pack: Update 3

OS: Windows Server 2012R2

OS Service Pack:


Client is in process reinstalling. If the issue persists will try to rebuild the Servers.xml file: c:\Users\UserName\AppData\Local\Wonderware\ActiveFactory Back up and then remove file 'Servers.xml' - Removed Servers.xml. Tried launching Trend. File was not recreated when adding a server. Tried updating XML with PROTECTED="FALSE". both result in same error. Client is running a repair with fresh installer. And will provide xml from a working trend. Identified multiple unsupported updates however other systems with same updates are working. WebEx Notes 2.28: FIPS-compliant Encryption policy disabled and the server.xml was created when Trend launched. Once this policy was updated the client lost RDP connectivity. Other working systems do not have this policy enabled. Client has following up with IT but has not received any clarification.

Close Date: 3/16/20 9:07

  • Was this article helpful?