I agree for the simple fact that it is always good to keep up with any features that have become common across products. Drag and drop would be a nice addition. Originally posted 2015-05-20 02:39:00 UTC
... View more
A warning banner is displayed at the top of the Workstation window that states "A license violation has been detected." even though a valid evaluation license has been activated on the machine or site.
The user will also find another warning message on the LicenseManager screen, under the System folder, that provides greater detail. This message will state specifically what is missing, for example "An additional X automation server license(s) are required. Please purchase the required licenses."
EcoStruxure Building Operation
EBO Enterprise Server 2.X and newer
EBO Workstation 2.x and newer
The new scalable licensing structure established in version 2.0 requires licenses for each automation server device (and field devices if the system is a new database). The evaluation (demo) license will account for the required licenses as long as it is valid but sometimes can be stuck in a state where it has not been validated.
In the majority of situations, simply rebooting or performing a warm start of the Enterprise Server will clear this warning as long as there is a valid evaluation (temporary) license hosted in the license administrator the ES is referencing.
Restart the Enterprise Server.
Restart the License Server (if on a different machine as the ES). If required, restart the ES again.
Check for any errors in the License Server and verify that the Vendor Daemon is up and running. See Unable to log into WorkStation due to license error codes -12, -15, -18 or -97 for more details around this troubleshooting step.
If these steps have not resolved the issue, then open a support case with your local country support organization.
For more information about the enforcement of licenses see the EcoStruxure Building Management WebHelp article, Licensing Enforcement.
... View more
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 Services for assistance.
An Energy Expert system is being moved to a new server and/or the virtual image is being upgraded. The historical records held in the SQL database of the Power Monitoring Expert (PME) system need to be backed up and properly restored on to the new server.
EcoStruxure Building Operation
EcoStruxure Energy Expert (formally Power Manager)
Power Monitoring Expert (PME)
The system administrator has deemed it necessary to upgrade the Windows server that the Energy Expert system is installed on for security and/or resource reasons.
It is important to remember that an Energy Expert installation is really just two Schneider Electric offers, EcoStruxure Building Operation and Power Monitoring Expert, installed together and set up to pass information back and forth. This means that appropriate steps must be followed for each system to backup the historical data and properly restore it on the new server.
For more detail regarding how the system is laid out, please see the Difference between EcoStruxure Energy Expert (Power Manager) and Power Monitoring Expert (PME).
Steps to move an Energy Expert database
Backup the Power Monitoring Expert (PME) SQL database, dashboards and reports. The Configuration Manager tool available on the Exchange can be used to back all of these items up automatically. Run the tool on the existing server and it will create a zip file to be used later on when restoring to the new server. See Migrating a PME 8.0 System to a New Server for more information. The Schneider Electric Technical FAQs website also contains many other helpful troubleshooting articles for PME including different versions of the product.
Return the Energy Expert license(s) from the Floating License manager in order to move them to the new server. For more information see Video: Licensing Guide for Power Monitoring Expert (PME) 8.x and 7.2.x and ENM 8.3.x.
If moving the Enterprise Server, make a historical backup of the EcoStruxure Building Operation (EBO) ES from the existing server. See Backup of StruxureWare/EcoStruxure Building Operation AS and ES for more information.
If the Enterprise Server and other EBO licenses are installed on the existing server, then they may need to be returned as well so they can be moved to the new server. See Removing a Local License or Returning a Network License for more information.
Next the ETL project files must be retrieved and saved so they can be moved to the new server (if using architecture 1 in the Energy Expert offer). Go to the file location below and save all ETL project files that are needed on the new server. C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs
If moving the Enterprise Server, install the EBO software on the new server, rehost the EBO licenses, and restore the EBO server backup(s). See Restoring the EcoStruxure BMS Server for more information.
Install the Energy Expert software (the software includes PME, ETL and the integration utility). The information on how to download the Energy Expert software can be found on the Exchange. Once the software has been installed, the Energy Expert license can be hosted to the new server in the Floating License manager.
Next, install the PME Configuration Manager tool on the new server. The zip file from step 1 can be loaded using this tool to restore the SQL database, PME dashboards and PME reports.
Add the previously saved ETL project files to the same location on the new server C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs
Since the server has changed, the configuration settings must be updated in the ETL projects to reflect the new server name. The settings in the EWS interface on the EBO server will also need to be updated as well. Note: It may be easier to delete the existing EWS interface in EBO and then use the integration utility to create a new XML import file to simply rebuild the interface.
... View more