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 for assistance. Issue Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update". Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server ... View more

Issue There are some BACnet devices that advertise support for services such as RPM, COV etc  but malfunction when the service is used.  An example of such device is the Johnson Controls TEC2627VVT which advertises support for RPM but fails to upload its objects when SBO uses RPM to get the object list. Product Line EcoStruxure Building Operation Environment BACnet Automation Server Enterprise Server Cause Some BACnet devices with inconsistent protocol implementation are unable to process some BACnet services such as RPM, COV etc. Resolution In versions 1.8.1 and onwards allows the user to create a rule under the BACnet interface to configure SBO not to use the service, the rule is then applied to particular BACnet devices specified by 'Vendor Identifier' and 'Model Name' creating in effect a black list of such devices. After applying the hot fix follow these steps to create the rule:   Using a text editor such as 'Notepad' create a text file and enter the device's vendor ID (5)  and model name (TEC2627VVT) followed by the rule (no-rpm, no-cov ) using the format seen in the screen shot below. (You can name the file anything you want), Save the file to desired location on the PC.   Under the BACnet interface create a new 'Document' object in the 'Application' folder. NOTE: the object MUST be named 'service_blacklist' all low case. Click 'Next' then import the text file created in step 1 and save the 'Document' object.   Reboot the server.   Once the device is on the black list, SBO will not send 'readPropertyMultiple' requests to the device, it will use only single 'readProperty'.   When disabling RPM and COV for a particular device the blacklist would be as follows. (no-COV rule added in 1.8.1.23701 and included in the later full release builds) X Y          ---- if model claims rpm, but fails          ---- if model claims cov, but fails           And this syntax can also be extended for multiple devices from different vendors at the same time.   ... View more

Issue Offline alarms received from Continuum controllers every few minutes and log error 0x00006c0e Broadcast Storm AKA Error transmitting and/or 0x00006c03 Driver fatal error during operation. Product Line Andover Continuum   Environment Continuum Net Controller II Continuum ACX 4 Controller Continuum CX Gen 1 Continuum bCX4040 Continuum bCX9640 Continuum BCX4000 Cause Excessive ARPs and/or other broadcast traffic on the network. Resolution When troubleshooting controller offline issues that are suspected to have excessive broadcast traffic as the root cause it is important to understand how to interpret Wireshark capture to determine whether too much broadcast on the VLAN  is indeed the problem. Note that taking the percentage of broadcast traffic in a Wireshark capture while a good starting point cannot in itself be solely used as proof that excessive broadcast is indeed the root cause of the controllers going offline, this is because in the absence of much unicast traffic the broadcast traffic will make up most of the packets resulting in a misleading high percentage. A much better way to determine whether the controller maybe going offline due to excessive broadcasts is to look at the average broadcast packets per second over a 15-20-minute capture. The screen capture below shows the  statistics  from a 20 minute capture filtered by broadcast traffic (eth.dst == ff:ff:ff:ff:ff:ff)  The capture shows that about 63% of the traffic is made up of broadcast at an average of 24 packets per second. The Continuum controllers on the network were going offline multiple times an hour. Note that the Continuum controllers are initially able to handle a much higher rate of broadcast traffic, tests performed in the PSS lab show a CX9680 can handled about 10 times  the amount shown here sustained for 5-10 minutes but over a much longer period of time such as several days or weeks the amount of broadcast traffic shown was enough to cause the controllers  to go offline. The screen capture below shows the statistics after the root cause of the excessive broadcast was identified and fixed. The problem at the site in question here was a defect in the network switch that was making the switch duplicate ARP traffic. Note that Cisco switch model Catalyst 4500 is also effected by the firmware bug. Current version which fixed the issue: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.05.E RELEASE SOFTWARE (fc2)   Previous version which caused the broadcast problems: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.02.E RELEASE SOFTWARE (fc2) ... View more

Issue After upgrading to Continuum 1.94, Cyberstation throws the following error: Failed to call pILiveData -> GetLiveData().  ACDataServices has an error. Product Line Andover Continuum Environment Continuum 1.94 Schedule Error Cause This behaviour is due to a bug that was described in TPA-BOST-12-0002 00 Schedule Exception Errors. Resolution Install the CyberStation v1.94 SP1 - Software which can be found on the Exchange Extranet. ... View more

Issue There are a couple of part numbers available for the expansion module cables, which ones are for which devices? Environment xP modules Cause Not sure which cables are for which xP modules. Descriptions and documentation on iPortal is inadequate. Resolution There are three xP module cables available: The 01-0100-484 cable is a replacement for the xP-Display module cable and this is meant to be for the xP-Display only, not for any of the other xP I/O modules. The xP I/O modules such as xPDO4 require either the xP-Mod-Cable-3 or xP-Mod-Cable-10. Be aware that you will only be able to extend the xP network for a maximum of 10Ft. See this iPortal datasheet or on Exchange Extranet for details. ... View more

Issue  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope. Environment Infinet Field Bus MSTP Field Bus Cause Documentation Resolution See  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope.pdf ... View more

Issue Information on the features that Video Monitor supports and details on how to configure it on a Continuum Workstation. Product Line Andover Continuum Environment Continuum v1.90 and above. Cause There does not seem to be a specific manual for Video Monitor. Resolution What Is Video Monitor? Video Monitor is CyberStation's powerful video-surveillance tool. Video Monitor, available in CyberStation Version 1.9 and higher, allows you to view live and recorded video images from cameras assigned to doors or points that trigger alarm events. It allows you to monitor doors, immediately capture video images from doors, unlock a door, monitor door status, monitor a person's access to doors, and get alarm information as soon as it happens. You customize the way Video Monitor operates using its powerful configuration tool, Video Administrator. Using Video Administrator, you can attach up to 16 cameras to a door or point. Video Monitor is launched when an event associated with the door or point triggers an alarm. Another video surveillance monitoring tool, VideoLayout, is also available for video matrix-frame viewing. The system may be configured to use either Video Monitor or Video Layouts as your primary video interface to alarms. Also see reference to supported features in the Feature Blast for v1.90 when Video Monitor was first added to Continuum. Configuration There is a large amount of information in the Continuum on-line help files that discuss how to configure Video Monitor in detail. See the Continuum online help contents and search for "Video Monitor."   Note: The Video Monitor option must be enabled on the Continuum Security Key to able to set this up and use it. This comes standard in v1.90 and above and can be enabled on your Key if it is not already. ... View more

Issue An update from 1.94 to 1.94 SP1 will generate an "Installation error! Microsoft ODBC SQL Server Driver SQL Server Implicit conversion from data type datetime to int is not allowed. Use the CONVERT function to run this query." Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A column in the db doesn't get converted properly SQL Server Implicit conversion from data type datetime to int is not allowed Use the CONVERT function to run this query. Resolution To correct this issue apply the following hotfix AFTER installing 1.94 SP1 but BEFORE running the database update Hotfix for DataBase Update Error ... View more

Issue A database update from 1.94 to 1.94 SP1 will generate an Installation error [Microsoft][ODBC SQL Server Driver][SQL Server Implicit conversion from data type datetime to int is not allowed Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A column in the db doesn't get converted properly. The SQL Server Implicit conversion from data type 'datetime' to 'int' is not allowed. The CONVERT function has to be used to run this query contained in the hotfix. Resolution 1. To correct this issue apply the following hotfix AFTER installing 1.94 SP1 but BEFORE running the database update 2.  Locate the hotfix on Exchange using the following link:  https://ecobuilding.schneider-electric.com/search#keyword/14191/tab/documents 3.  Find the item entitled:  "Error when Updating the Continuum DB while Upgrading to CyberStation 1.94 SP1 - TPA-CONT-13-0003.00" 4. Select download and read the release notes and install the hotfix Upgrading to CyberStation 1.94 SP1 - TPA-CONT-13-0003.00   ... View more

Issue The following errors are in the Windows Application Event Viewer: Email, Failed to send email - MAPILogonEx failed in InitSession function!, Result is 80040111 Email, Failed to send email - Email (MAPI) initialization failed in InitSession function!, Result is 80040111 Email, Failed to send email - InitSession failed in CACEmail::Init, Result is 80040111 Product Line Andover Continuum Environment CyberStation 1.9x Cause If the errors are only logged on startup of CyberStation then they are not likely an issue. However, if these are being logged more than just on startup they may indicate other issues, such as RPC errors. Resolution If you are not emailing alarms these errors may be able to be stopped. Run a listview [1] of all EventNotifications and display the AlarmOptions attribute. Check if the word email shows up. Edit the EventNotifications where it does show up and remove all emailing from the Actions tab. CyberStation creates some of these EventNotifications in the templates folder and they are setup for emailing by default. ... View more