Issue Time synchronisation is often an issue on large BMS installations. A central time signal is normally required to make sure all controllers, terminals or workstations have the correct time. If there is no internet connection available then the time has to be synchronised from a central source. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Sigma Continuum Vista SmartStruxure Windows XP Windows 7 Server 2003 Server 2008 R2 Warning 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. Cause No internet connection available to synchronise the system time. Resolution Important The methods below contain steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. If using Windows XP, please use the following link - http://support.microsoft.com/kb/314054 If using Server or Windows 7 OS, please use the following link - http://support.microsoft.com/kb/816042 This has been tested for Time updates to an AS by simply using the PC IP address as the primary NTP Time Server. If the firewall is turned on you also need to make sure UDP 123 is open. Please note that Windows will add a dispersion to the time that may cause issues with time synchronization, please see Automation Servers ignore time sync message sent from Windows NTP server that uses local internal clock for details.

Issue The network administrator requires that the SQL Andover97 password be changed every three months.  How will this affect the Continuum System? Is it necessary to do a Database Initialization each time the password is changed? Product Line Andover Continuum Environment Andover97 SQL Database Initialization Cause Once the Andover97 password has been changed, the workstations will lose their connection with their access to the database until the workstation (not the database) can be initialized with the new password. This will be indicated by a Database Fault error at the workstations.  Resolution The proper way to change to transition to the new password is to: Shut down all cyberstations. Change the Andover97 password in SQL. Launch Continuum Database Initialization. Select Workstation and enter the new password on the Database page, then select OK. Relaunch all cyberstations.  Once the password is changed, it is only necessary to do perform a workstation initialization (not a database initialization), but this must be done on each workstation.   Refer also to the following article that discusses how Continuum uses the sa password: When is the SQL System Admin (sa) password required?

Issue Satchwell CZU Mk3 Zonemaster Controller requires replacement. Product Line Field Devices Environment Stand alone Fan Coil Unit Temperature Controller. Satchwell CZU Mk 3 Zonemaster Controller. CZU 3201 CZU 3202 CZU 3203 Cause Obsolescence of Satchwell CZU Mk3 Zonemaster Controller. Resolution Replacement of Satchwell CZU Mk 3 Zonemaster Controller with S-E Satchwell CZU Mk 4 Zonemaster Controller. The CZU 4201 may be used to replace the following CZU Mk 3 Controllers :- CZU 3201, CZU 3202, CZU 3203 N. B. CZU 3201 Controllers provided an additional -9 to +9 V d.c. output enabling connection to peripherals such as the Satchwell NSU 1401 Night Set-back Override Unit, TSU 1402 Two Step Auxiliary Unit and SSU 1403 Signal Selector Unit. CZU 3202 and CZU 3203 Controllers provided an additional -0.5 to +9 or -9 to +0.5 V d.c. output enabling connection to the Satchwell NSU 1401 Night Set-back Override Unit. Additional outputs are not provided on the CZU 4201 Controller and in those applications where these are required then it will be necessary to consider an alternative Controller to the CZU 4201. Details of the CZU 4201 may be viewed  here. A remote Satchwell Adjustable Room Temperature Sensor such as the DRT 3451, or a remote Satchwell Duct Temperature Sensor from the DDU range of Sensors may have been installed and connected to the Controller. Any existing remote Satchwell Temperature Sensor may be retained for connection to the CZU 4201. Should the remote Satchwell Adjustable Room Temperature Sensor require replacement then this may be replaced by an S E STR 612 Adjustable Room Temperature Sensor. Details of the STR 612 may be viewed here. Should the remote Satchwell Duct Temperature Sensor require replacement then this may be replaced by an S E STD 670 Duct Temperature Sensor. Details of the STD 670 may be viewed here.

Issue Downloading new NXE or APB files using Lonmaker for controller updates Product Line Other, TAC Vista Environment Lonmaker 3.2 Cause Updating of software in a controller for more features or fixes. Resolution To update a new NXE or APB in a Lonworks controller using lonmaker follow these steps. 1. Download the NXE or APB file you intend to use. If it is a 100 series controller the files are available on extranet. Here is the link to the Xenta 100 series NXE files.   2. Locate the device you wish to upgrade in you Lonmaker drawing and select the load option 3. The next option screen will indicate the existing template name. Retain this name if the SNVTs are not changing. You may want to create a new template name if the SNVTs are being amended. 4. Select the Next option and then in the image name area browse to the NXE or APB file you want to download to the controller. 5. Select the next option then select the state you would like the device to be in after the new NXE has been downloaded. Then select the finish button. The application will then be downloaded to the selected controller.

Issue After installing or upgrading from EBO 2.0.x to EBO 3.x.x or EBO 4.0.x, the Enterprise Server or Enterprise Central will not start. When the "Start Service" button is pressed in the Building Operation Software Administrator the server status is stopped and does not change and no activity is seen in the system log area. Product Line EcoStruxure Building Operation Environment Enterprise Server Enterprise Central Cause The vcruntime140.dll file is missing from the Window’s system32 folder. Resolution The vcruntime140.dll file is installed as part of the Visual C++ Redistributable for Visual Studio 2015 installation. Visual C++ Redistributable for Visual Studio 2015 can be downloaded from the link below. https://www.microsoft.com/en-in/download/details.aspx?id=48145   If you have later versions Visual C++ Redistributable for example Visual C++ Redistributable for Visual Studio 2017, Visual Studio 2015, 2017, 2019, and 2022 can be used to save uninstalling version 2017. https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170  

Issue When installing or upgrading Cyberstation, is the SQL sa password required? Product Line Andover Continuum Environment Cyberstation and Web Client installation or upgrades Database Initialization application SQL 2005 and 2008 versions as per the compatibility matrix for the version being installed V1.9x Cause Sometimes the database initialization asks for a "sa" password, other times not, what determines this? Resolution During first installation of SQL it will ask for a new System Administrator (sa) password to be created. When creating a new Continuum database the SQL sa password will be asked for or another password with full domain administrator rights could be used. When updating an existing database you will sometimes be asked to enter the sa password, this is determined by the Database Initialization application. If the version it is upgrading from requires changes to be made to the SQL table structure, a new table created or new stored procedures to be created, then the sa password will be required, otherwise it will not be asked for. NOTE: The "Andover97" account is not an "sa" account. The "Andover97" account needs to be the owner of "ContinuumDB" database and must have full access to it.

Issue There is no built-in Credential Type for the HID 37-Bit badge with no site code (H10302). Product Line Security Expert Environment Security Expert Server Access Card Format Cause Security Expert does not have the HID 37-Bit badge (H10302) with no site code as a built-in available Credential Type. Resolution 1) In the Security Expert Client, select Sites -> Credential Types 2) Create a new Credential Type with a name of your choosing. 3) Under Configuration, select the Format as Wiegand. 4) In the field labeled Wiegand or TLV Format, enter the following exactly as written:                                                        A,FACILITY,0,MSB,BIN__B,CARD,35,MSB,BIN__PBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBP_EXXXXXXXXXXXXXXXXXX.................._..................XXXXXXXXXXXXXXXXXXO 5) Save   NOTE: This article assumes that the reader is familiar with creating and deploying Custom Credentials, If this is not the case, then please reference the Complex Transition Programming section of the Transitioning Continuum Sites to Security Expert - Transition Guide

Issue Daylight Savings time changed in the U.S. and methods are needed to synchronize time Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Methods for synchronizing controller time Resolution The following document was email out when Daylight Savings changed in the U.S. and contains 2 methods for synchronizing time Click Here to download the pdf document.

Issue When trying to create or update a Security Expert database the error 'Invalid Database Server is displayed Product Line EcoStruxure Security Expert  Environment EcoStruxure Security Expert  Microsoft SQL Server Cause The path to the SQL Server from the Client is incorrect or inaccessible and will not resolve Resolution There are a number of resolutions to this issue depending on the cause. This article mainly focuses on a configuration where the Security Expert and Microsoft SQL Server are on separate PCs. The error can happen locally also but is less likely. One or more of these resolutions may be required to fix the issue. 1. The Server / Instance name is incorrect when typing it into the Database Server dialogue box during installation. (Local SQL Server) Default Database Server Dialog Box    There can be some confusion on what to enter into the dialogue box because, by default, the instance name and the main database name are the same. Ex. Server Name\Instance Name    Database       localhost\SecurityExpert            Security Expert   (Remote SQL Server) Ex. Server Name\Instance Name    Database       SVR19SQL19\SecurityExpert     Security Expert Note: If just the ServerName SVR19SQL19 or SVR19SQL19\SecurityExpert\Security Expert The Invalid Database Server error would occur   Copy and Paste the Server and Instance Names using SQL Management Studio (SMSS) This method can help to avoid typing errors Install SMSS on the same PC that has Security Expert Installed or use SMSS on the SQL server with Remote Desktop From the Connect to Server dialog> Server name, select <browse for more...> Select Network Server and then select the remote SQL server and click OK Right Click> Copy on the blue highlighted server name and instance Paste into the Security Expert Database Server Dialog box   For a detailed description of Instanced and Database, click on the following link Microsoft Database and Instance Article  Note: Try using the IP address instead of the SQL server name. 2. Make sure SQL Server Service is running on the remote SQL server 3. If using a named instance, make sure the SQL Server Browser Service is running on the remote SQL Server 4. Ensure Firewalls have an open port for SQL server (default 1433) 5. Make sure the SQL Server is configured to allow remote connections 6. The Windows account being used to do the Security Expert Installation must have access to create the database on the remote SQL Server.  7. Check the Windows Application and System logs on the Security Expert and SQL Server for errors related to the Security Expert Install, DNS or Connection errors 8. Examine the SQL Server Log for error messages   Ex. If Active Directory is being used, the error “The SQL Server Network Interface library could not register the       Service Principal Name (SPN)” This issue can be fixed by giving the domain account the appropriate permissions in Active Directory. Permissions required are:  ServicePrincipalName: Read  ServicePrincipalName: Write   Log in to the server running your Active Directory service and execute the following steps: Run Adsiedit.msc In the ADSI Edit snap-in, expand Domain [YourDomainName], expand DC= RootDomainName, expand CN=Users, right-click CN= [YourAccountName, and then click Properties. In the CN= AccountName Properties dialog box, click the Security tab. On the Security tab, click Advanced. In the Advanced Security Settings dialog box, select one (any) of "SELF"'s row Click Edit, Open Permission Entry dialog box. Make sure the Principal is "SELF", Type is "Allow" and "Applied to" is "This Object Only", in the Properties section, select the properties below: Read servicePrincipalName Write servicePrincipalName Click OK to apply all changes and exit the ADSI Edit snap-in Finally, you need to restart the SQL Service(s) that use the account in question.   9. If you are still unable to get passed the "Invalid Database Server' error, please open a case with Technical Support.

Issue UNC-520 heartbeat LED had no activity but the UNC appears to be running without issues.  Environment I/A Series Universal Network Controller - UNC-520 Warning Cause The UNC CPU idle is at 0% which resulted in the UNC heartbeat LED not having any activity (always off).  In this case,  this is caused by changing the ControlEngineService executionFrequencies to faster values and objects' executionParameters frequency set to faster or fastest. The station is using large amount of CPU resources.  Resolution To correct this make the following adjustments:  In the ControlEngineService properties, Config tab, change the executionFrequencies back to the default values of fastest at 500ms, faster at 1s, normal at 2s and slower at 5s.    Change the objects' executionParameters frequencies back to the default setting of normal. You can used the AdminTool object to perform a search and replace and changed all the executionParameters frequencies to normal.  There may be a need to change these values from the default values to optimize the UNC performance. Refer to the Niagara Capacities Engineering Notes for details. You should contact Product Support if you are unsure of these settings. 

Issue I/A Series G3 Office Demo laptop a dialog box indicating "This machine is now licensed" followed by an error "Workbench is not licensed to run on this machine". Environment I/A Series G3 (all versions) Cause The computer date is earlier than the license generated date. Resolution Run the Niagara Console program for the G3 version.  Type the following command to view the license information. c:\niagara\niagara-3.5.34>nre -licenses The results will provide information to assist in diagnosing the problem.  In this case, the Licenses indicates that the current date is earlier than the license generated date.   Correct the date and time on the computer.

Issue N4 software installation stops because; azul-zre-compact3-qnx7-arm tridium-qnx7-n4-titan-am335x software is missing Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Cause A valid license including the features that meet the dependencies is not installed. Resolution Install a valid license containing the jre8J8000Azul, jre8Qnz7Zulu and qnx7, jreQnx7Zulu features before attempting to commission the Jace 8000

Issue Downloading new NXE or APB files using NL220 Product Line TAC Vista Environment NL220 Warning 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. Cause Downloading new or old firmware versions into application specific controllers. Resolution Before performing this update, make a backup of the NL220 project. In case something happens and the configuration parameters are lost, there will be something to reference. Go to extranet and download the latest NXE and APB files. In NL220, right click on the controller to be upgraded and go to Network > Upload configurations. This will update the database with the current configuration in the controller.   Next, right click on the controller again and go to Network > Replace. A box will open that is titled Commissioning a node. The option "Upload configuration from old node if present" should be checked. This will insure that the values in database are current with the controller. Under Configuration download, "Download all known database values" needs to be selected. This will download the configuration parameters back into the controller once the update is complete. Finally under Template, "Download a program to the node" should be checked. The file that was downloaded off of extranet earlier can now be browsed in. Note: The option ‘Keep current configuration on node’ is misleading. By selecting this option it will not download parameters to the node. So when you download the new APB file, the controller will retain the configuration parameters found in the APB file not what was originally on the node.   Click Continue

Issue Require details on how to setup a counter to count input activations and trigger an alarm after a certain number has been reached. Product Line EcoStruxure Security Expert Environment Security Expert Cause Unsure how to program a counter and require an example. Resolution Need to create: 2x Data Value (Data Up, Data Compare) 2x Variable (Up Count, Compare) 3x Programmable Function (Door Up Count, Value Compare, Reset Alarm) 2x Output (vAlarm OP, vReset OP)   Instructions: Virtual Outputs Under Programming | Outputs create two (2) new outputs. One will be the alarm trigger, the other the alarm and counter reset. Save changes.   Data Value Under Automation | Data Values create two Data Values to store the appropriate data in the system. Set the Preset Value for Data Up to 0, and for Data Compare to the number of activations you want to trigger an alarm at. In the example, this is 2. Save changes.   Variable Under Automation | Variables create two Variables to count in the correct scale for each Data Value. Up Count: Set the Scale to 1, MaximumValue to the top end of your counting scale and the Data Value to the Data Up Data Value created earlier. Save changes. Compare: Set the Scale to 1, MaximumValue to the top end of your counting scale and the Data Value to the Data Compare Data Value. Save changes.   Programmable Functions Under Automation | Programmable Functions create three new Programmable Functions. Door Up Count to increment the counter register, Value Compare to compare the current register against the setpoint, and ResetAlarm to reset the alarm output Door Up Count: Set Type to Register Counter and Mode to Normal On the Register Counter tab set Input to Count to the physical input you want to count, Counter Register to Data Up, tick Increment on Input Open, tick Log Counter events, and set Reset Output to vReset OP. Save changes. Right-click the new Programmable Function just created and select "Start". Value Compare: Set Type to Value Compare, Mode to Normal. On the Value Compare tab set Activate Output When Above Setpoint to vAlarm OP,  Analog Input Data Variable Register to Data Up and Set Point Data Value to Data Compare. Save changes. Right-click the new Programmable Function just created and select "Start". Reset Alarm: Set Type to Logic Control and Mode to Normal. On the Logic Control tab set Logic Function Mode to 3 - Inverted Follow Pulse On First Output, First Output To Check to vReset OP and Output To Control to vAlarmOP. Save changes. Right-click the new Programmable Function just created and select "Start".   Test the Functions: Create a Floor Plan with Compare, Up Count, vAlarm OP and vReset OP added so this can be monitored in real-time. Pulse the monitored Input and confirm Up Count increments. When it gets to the set point value confirm vAlarm OP goes on to trigger an alarm. When vReset OP is enabled confirm the Up Count is reset to 0 and vAlarm OP is disabled.

Issue Is a Menta License required in order to program  the Menta in a Xenta 711? Environment 711 Vista Menta licensing Cause Licensing is unlocked from the factory for "711 Menta." Resolution No License is necessary.

Issue Double clicking the BACnetNetwork used to open the BACnet Device Manager now it opens a BCP Device Manager that looks just like the BACnet Device Manager?  What is the BCP Device Manager? Environment I/A Series (Niagara) G3 Cause Installing Distech software to support their devices will result in the BCP Device Manager being installed for the BACnetNetwork. Resolution This is not an issue, just be sure to select the correct Device Manager for the devices you plan to work with.

Issue How and where should sensors be fitted and maintained? Product Line Field Devices Environment Temperature and humidity sensors Cause General advice is required for cleaning and maintaining temperature and humidity sensors. Resolution The most important thing about sensors is to fit them correctly and appropriately during installation as this will reduce the amount of maintenance required. Fit them in locations that are accessible as well as away from dust and dirt to reduce the amount of cleaning required. See Recommended locations for Temperature Sensors, Valves, and Actuators for further advice on sensor location. Check the specific installation instructions for the sensor used and verify they are fitted accordance with this. All sensors should be regularly checked for correct operation as part of a regular building maintenance plan and replaced if they are not operating correctly. Most sensors are sealed units and do not require maintenance, maybe just an occasional dust with a clean cloth to remove surface dust, these include duct and immersion temperature sensors, outdoor sensors and thermostats. Room temperature and humidity sensors usually have vents or gauzes to allow airflow over the elements; these should be regularly dusted and can be cleaned with careful use of a vacuum cleaner or air blower to remove dust or other particles from within the unit. Do not however use equipment that can produce excessive pressures like compressed airlines as this could result in damage to the sensor. If you do need to use cleaning products on the sensors, then first check the materials used on that specific sensor (see datasheet, most sensors use Polycarbonate or ABS plastics) then verify that the cleaning chemicals are safe for use on that type of plastic or metal. Chemical/ material compatibility data is widely available on external websites (e.g. http://www.coleparmer.co.uk/Chemical-Resistance )

Issue Site has a personnel database with about 10K records, the site is switching to dual credentials and has configured the Personnel Manager to use HIDCorp1000 as the default for card type 2 and xxx as the default for Site Code 2. Problem is when going to change the personnel the Card Type 2 field still comes up with Infinity37 and Site Code 2 of 0 instead of the configured defaults. Environment CyberStation Cause Any existing personnel in the database will come up with Infinity37 for the card number 2 and 0 for the site code 2 as those were the values populated in the SQL database for those fields when the system was configured for only one credential. When creating NEW personnel objects the fields show the configured default values. Resolution When creating NEW personnel objects the fields show the configured default values.

Issue Changing the NetController Model Type between 9900 and 9940 Environment NetController CX9900 NetController CX9940 Cause Update NetController model number in Continuum database Resolution Backup the database. Shut down Continuum as precautionary measure Open the SQL Enterprise Manager Open the SQL Query Analyzer Select the ContinuumDB To change from 9900 to 9940, type in update infinitycontroller set CntrlType = 44 where UiName = ‘Infinity1’ and execute To change from 9940 to 9900, type in update infinitycontroller set CntrlType = 42 where UiName = ‘Infinity1’ and execute Please note that you must change ‘Infinity1’ to match the Uiname of your controller Start Continuum up again and verify that the change was effective

Issue Cannot delete personnel profiles from personnel manager. Product Line Andover Continuum Environment Continuum 1.81 Cause Personnel profiles have become corrupted and can not be deleted. You can not rename areas without removing/replacing them in the profile. Resolution Procedure to remove corrupted personnel profiles: Start Continuum Run ACDEVApp.exe from the Continuum directory. Click Generate. Replace the 3 lines: <REQUESTOPERATIONS> </REQUESTOPERATIONS> </IACDEVREQUEST> ... with the following 6 lines, only replace the word ProfileName with the name of the profile being deleted: <REQUESTOPERATIONS> <DELETE> <OBJECT PATH="ProfileName"/> </DELETE> </REQUESTOPERATIONS> </IACDEVREQUEST> Press the "Process Request" button