New in the Community? Get started here

Schneider Electric Exchange Community

Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.

Register Now
Building Automation Knowledge Base
Showing results for 
Show  only  | Search instead for 
Did you mean: 
PSST, your community homepage is getting a new face - stay tuned and experience the change in few days

Issues upgrading an Automation Server to 2.0.x when connected to an Enterprise Server



Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance.


Issues upgrading Automation Servers (AS, AS-B, AS-P) connected to an Enterprise Server (ES) from versions prior to 2.0.x to a version that is 2.0.x. ES and one Automation Server will upgrade but no others connected to that same ES will upgrade and will show an error while attempting to download the new software. 

Product Line

EcoStruxure Building Operation


  • Building Operation Automation Server v1.9.x
  • Building Operation Enterprise Server v1.9.x



If the Automation Servers within the ES environment are not uniquely named, and/or are the same name as the ES, an error will be received if upgrade is attempted stating "Deploy upgraded database failed".


As found within the Enterprise Central section of the 2.0 Release Notes, "All servers must have unique names".


*NOTE* Renaming the Automation Server will break any paths to that Automation Server, as such they will need to be corrected.


Follow these steps to address this issue:

  1. Prior to upgrading any devices within the environment, check for and find any servers with non-unique names
  2. Detach the Automation Server (with the naming identical to the ES or any other server) from the ES
  3. Rename the Automation Server with a unique name
  4. Correct any binding path issues
  5. Reconnect Automation Server to the ES
  6. Upgrade the environment to 2.0.x
Labels (1)
100% helpful (1/1)