When an attempt is made to create or save a new schedule, you get the following error:
AccessXpert Hosted software v3 (all versions)
AccessXpert Premise Software v3 (all versions)
Mercury has a limit of 255 schedules, which you can customize up to 254 schedules as there is the default "Always" schedule already built in. This is a limit on the Mercury hardware.
It is highly encouraged customers to avoid utilizing all 255 unless absolutely necessary as you will run into the case below of not being able to add a new one should you need to (or a one-off).
Folders, and all objects within them, apply towards the instance limitations. If there are 6 folders, ALL schedules in the folders plus the schedules in the instance all count towards your 255 limit.
... 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 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.
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:
Prior to upgrading any devices within the environment, check for and find any servers with non-unique names
Detach the Automation Server (with the naming identical to the ES or any other server) from the ES
Rename the Automation Server with a unique name
Correct any binding path issues
Reconnect Automation Server to the ES
Upgrade the environment to 2.0.x
... View more
Unable to connect to Access Expert as the Feenics Mercury Service stops and will not restart after a system reboot.
Access Expert Premise Software (AX) v3
If the Mercury service is failing to start the most common issues are:
Service Administrator password was changed
Feenics API is not running
Service Administrator password was changed:
Update the password within these configuration files to match the new admin password
c:\program files (x86)\feenics\web api\settings.conf
c:\program files (x86)\feenics\mercury service\settings.conf
Feenics API not running:
Check the API by opening the Internet Information Services and checking to make sure the Feenics website is running.
Make sure the default site is not running.
You can also check the bindings on the website
Port 80 and binding of '*'
... View more