Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Historian Client | Web
  • AVEVA Historian Client | Web Tech Notes

TN - 1230 Resolving Incorrect server.xml file used after coping server.xml to user profiles

Last updated: March 6th, 2025

Description

  • Author: Brian Schneider
  • Published: March 6th, 2025

Details:

Description

This article from InSource shows how to resolve Incorrect server.xml file used after coping server.xml to user profiles.

  • Author: Peter Farrell
  • Published: 3/17/2022
  • Applies to: Historian Client 2020

Details

Prior to System Platform, version 2020, it was possible to export and import a list of all available active Historians with usernames and passwords without having to manually enter them all in Historian Client Tools for each user profile. This is no longer possible with version 2020.

If you encounter issues after copying the server.xml file to user profiles the following information may help resolve the situation.

Check the AVEVA logger. If you see Error: aaHistclientdatabase warning "Incorrect server.xml file used" it is possible that the server.xml file has become corrupt.

Copying Server.Xml among user profiles is no longer supported because of security changes implemented by AVEVA. This is a security enhancement intended to prevent unauthorized users from gaining access to Historian.

The situation can be resolved after shutting down Historian Client (Trend, Workbook, Query,) and deleting server.xml located at C:\Users\[usename]\AppData\Local\Wonderware\ActiveFactory

Note: You can also rename server.xml rather than delete the file in case you need to revert to the original version of the configuration file.

Restart your Historian Client tool and manually enter the server connection configuration after which a new server.xml file will be created and updated.

fixing copying
Give feedback about this article

Recommended articles

TN - 1240 Creating a Watchlist Using an Import File

Read More

TN 1398 Determining Active Communications Server

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Logo

© 2025 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand