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 . Please 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 After upgrading to Continuum 1.94, Cyberstation throws the following error.  Failed to call pILiveData -> GetLiveData().  ACDataServices has an error. 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. 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: You do need to have the Video Monitor option enabled on your 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 isn’t 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 Is it important to stop these errors? Environment CyberStation 1.9x Cause 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 Resolution If the below 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. 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   In either case, 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

Issue Both BACnet MS/TP and Modbus typically provide a robust and reliable communications channel allowing the Automation Server to effectively manage a large collection of equipment over extended distances. When the system does not come up operating as expected due to the communications integrity, considerable effort can be consumed troubleshooting or working-around the fault observations. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, TAC IA Series Environment Automation Server with BACnet MS/TP or Modbus RS485 networks connected to Port A or Port B. Cause The configuration of the RS485 network can create conditions that reduce the tolerance for EMI noise on the bus, electrical ground differences, transmission signal loss through the cable and/or component performance. Resolution A collection of application notes and Quick Start Best Practices Guides are available on the subject of BACnet MS/TP and Modbus RS485 network connections to the StruxureWare Automation Server.  These application notes and quick start guides provide recommendations in the areas of – BACnet MS/TP & Modbus RS485 Network Termination Network Biasing Options and Techniques Unit Load and associated Maximum Node Count Recommendations Isolated RS485 Interfaces and related Expanded Unit Load Cable Specifications and Suggested Cable Selections Cable Routing and Recommended Lengths The documents describe configurations of cable, network length, node counts and bias arrangements providing compliance with the EIA/TIA-485 Standard and TSB-89-A Guidelines with the objective of optimizing system tolerance for noise, grounding and transceiver component variations.  Most of the application notes and quick start guides target specific product families which include the Andover Continuum b3 Family, TAC I/A Series MNB Family, Legrand Power Meters and the Viconics VT7000 series sensors. There is also an application note and quick guide directed toward other “Generic” RS485 MS/TP and Modbus devices where the user is guided through a sequence of information collection steps to determine the appropriate recommendations.  The collection of application notes and guides are available on the Schneider Electric download center. The list of links below will take you to the applicable download page. AN01-RS485-Generic Application Note – General MS/TP & Modbus I/F to Automation Server Quick Guide-RS485-Generic Best Practices Guide - General MS/TP & Modbus AN02-RS485-B3 Application Note – Continuum B3 I/F to Automation Server Quick Guide-RS485-B3 Best Practices Guide - Continuum B3 I/F AN03-RS485-MNB Application Note – I/A Series MNB I/F to Automation Server Quick Guide-RS485-MNB Best Practices Guide – I/A Series MNB I/F AN04-RS485-Legrand Application Note – Legrand Meter I/F to Automation Server Quick Guide-RS485-Legrand Best Practices Guide – Legrand Meter I/F AN05-RS485-VT7000 Application Note – VT7000 Series I/F to Automation Server Quick Guide-RS485-VT7000 Best Practices Guide – VT7000 Series I/F Note:    If using the download center for the first time, you will need to register. See Register for The Exchange Download Center for more information. The Download Center requires the use of Internet Explorer (version 8 or higher), Google Chrome or Firefox browsers. Additional information is available in the Hardware Reference Guide Access the StruxureWare Building Operation Web Help. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange. ... View more

Issue Files required to install StruxureWare Building Operation WEB Reports Server Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Cause Tutorial for configuring Web Reports Resolution StruxureWare Building Operation WEB Reports Server Release To start installation, download WebReports Operating Guide and Web Reports Reference Guide Installation Outline: The WebReports Reference Guide provides detail information about hardware, software requirements, and steps required to configure the applications. The following steps are an overview of the complete installation. Points 1-4 are easily and/or automatically done using "SBO Reports Preparation" available from the Buildings Community. This tool is not officially supported, but has proven to be helpful in many cases. Install and Configured required Windows applications, roles, and features. Outlined in Sections 3.4 of the WebReports Reference Guide Download and install SQL Server 2008 R2 Standard with Advanced Services it requires version 10.5 or later. Follow configuration steps found in Section 3.5-3.6 of the WebReports Reference Guide SQL 2008 R2 Standard with Advanced Services file name SQLEXPRADV_x64_ENU.exe Install .NET framework 4 per WebReports Reference Guide section 3.7 Ensure that the Enterprise server is running on another machine, or at this point install and configure it on the local machine Install WebReports Server using the processes defined in WebReports Reference Guide section 3.9 and 3.10 The online help guide for StruxureWare has an excellent tutorial which will walk you through configuring the report Server, and running your first reports: Administering Reports If you wish to create custom reports. Please follow the instructions as outlined in How to create custom reports in StruxureWare Building Operation WebReports APPENDIX A: Verifying system is ready for reports installation Before installing WebReports, but after configuring Windows Roles and Features, SQL and install .NET 4.0,(SBO 1.5 uses .NET 4.5) the user should always: Check to see that SQL Server is up and running Check that the user you are planning on installing Webreports with can connect to SQL and Microsoft Reporting Services. Log into SQL using SQL Server Management Studio User should be able to connect and view databases. Connect to the MS Reporting Services URL You can obtain the URL by: Start->All Programs-> Microsoft SQL Server 2008 R2->Configuration Tools->Reporting Services Configuration Manager. Once logged into Reporting Services Configuration Manager click on “Report Manager URL” and click the URL Verify that Reporting Services Manager page loads without error. If you run into issues with the above, a possible solution is to turn of User Account Control Settings. This can be disabled by going to the Windows Control Panel, selecting User Accounts, selecting "Change User Account Control Settings" and moving the slider all the way down. You must restart the PC for this change to take affect. Repeat the above steps and contact PSS if you are still unable to validate the system. APPENDIX B: Upgrading a report server installation As described in appendix A, the logged in Windows user is used to install the report server, and this user must have access to the SQL database. That is also true when upgrading the report server installation, so make sure you are logged into Windows with the correct user. Another option is to SHIFT + right click the installer, and select "Run as other user". ... View more

Issue There are many issues that can happen at Cyberstation and some methods are needed to troubleshoot. Product Line Andover Continuum Environment Continuum webClient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There are a number of steps and tools that can be used to troubleshoot Cyberstation Resolution This is a large subject that encompasses software and hardware, so this isn't a comprehensive list, but should offer some methods and tools to help troubleshoot Cyberstation or Webclient. Typically errors that are Cyberstation or Webclient related will display some sort of an error message on the screen which can be used to diagnose the problem. Isolated or System Wide - Is the issue happening on 1 or multiple Workstations? If so, it could be a system wide issue, but if it's just one workstation then it is isolated to this PC and could be an install, Windows OS, hotfix or hardware issue. Continuum Compatibility Matrix - A number of issues can happen if Continuum Service Packs or hotfixes or Windows Operating System (including Service Packs), Microsoft SQL Server, Internet Browser version and the version of Continuum or Webclient do not match the matrix. See document Andover Continuum Software and Firmware Compatibility Matrix Cyberstation Error - Is there an error message that is being displayed. A list of some Cyberstation specific errors can be found by pressing F1 with Cyberstation open, select index, type in Error, select error messages, Cyberstation How do you locate error messages in Cyberstation? Windows Error - Is there an error showing in the Windows event viewer? This step can be extremely useful when troubleshooting Cyberstation problems from issues installing Cyberstation or SQL to problems happening because of a Windows Operating System issue. Typically there are errors, event ids and details that when determined that they occur at the time of the problem, can be used to search the web for a solution. These can also be sent into support for some help analyzing the issue. Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Windows Service Pack or hotfixes- Were any Windows Service Packs or hotfixes recently applied to this PC that could be affecting this installation? To display all the hotfixes on a PC, see the following MS article: https://social.technet.microsoft.com/wiki/contents/articles/4197.windows-how-to-list-all-of-the-windows-and-software-updates-applied-to-a-computer.aspx Installed Software- Since the issue started happening has any additional software been installed on the PC. Take a look in Start> Settings> Control Panel> Add/Remove programs(XP) or Programs and Feature (Other Windows OS) and see what may have been recently installed. Antivirus / Malware -  On some occasions we have seen Cyberstations or Webclient PCs affected by viruses or malware. If an issue is specifically related to one PC and particularly if that PC is exposed to the internet, but doesn't have any Anti-Virus software installed, it could be infected. Updating Anti-Virus definitions and Malware/Spyware programs and running scans is recommended to clean up the PC. Hardware Issues - PCs will break over time from wear and also from Power bumps. Memory, NIC cards and Hard Drives are typically what go first. Memory - Many PC manufacturers supply memory diagnostic features in the system bios to detect if a RAM module is bad. This will often show in a certain spot every time in a certain program, not necessarily Cyberstation and can actually indicate that is can't access a memory reference. Hard drives - drives can crash or certain files can become damaged. Checkdisk and windows attempts to keep the drive clean, but sometimes reformatting the Hard Drive and reinstalling the Windows OS will correct the issue. If it's a physical issue with this drive then the problem could come back and a new hard drive may be needed. NIC (Network Interface Cards) - can cause connection issues and affect system performance. Not all NIC cards are created equal and at times integrated NIC(built into the motherboard) can be less robust than a third party NIC card. See the following for extensive troubleshooting advice, but often swapping the card is easier. http://support.microsoft.com/kb/325487 Graphics Displays - Some issue are more related to Pinpoint or Video. Check the graphics display and see if the most up to date video driver has been installed. Run any diagnostic that may be supplied by the video card manufacturer or swap out the card. Windows Device Manager - In Windows device manager you may see a black exclamation point on a yellow field which indicates the device is in a problem state. There can be many reasons this can happen and is beyond the scope of this article. See the following MS article for more information. https://support.microsoft.com/en-us/help/310123/error-codes-in-device-manager-in-windows System Info and Belarc Advisor - These tools can be used to see what hardware and software is installed on the PC. System info is installed with Windows. https://support.microsoft.com/en-au/help/184075/description-of-microsoft-system-information-msinfo32-exe-tool This can be sent into Product Support as a .nfo file and can be brought up with details. This information can be difficult to work with. Belarc Advisor - This is a free tool that can be installed on a PC and will display the information in a very readable  browser format. This tool will often find things that may have shown in System Info, but were difficult to find. http://download.cnet.com/Belarc-Advisor/3000-2094_4-10007277.html Restore Point - Windows XP, Vista and Windows 7 all have the ability to restore the system to a previous place in time by using Windows Restore Point. This is a Windows Operating System function and has some risks associated with it, but can be very useful to get back to especially when the issue is happening on a Stand Alone setup. https://support.microsoft.com/fil-ph/help/959063/what-is-system-restore If the restore point doesn't work then a reinstall or the OS could correct the issue or lastly a reformat of the hard drive and a complete reinstall of the Windows Operating System and then reinstall Cyberstation or Webclient. ... View more

Issue Status does not change. Environment CT current transformer H909HV-S6 Cause Although current flow is present, the current transformer status does not change. Resolution This issue was caused by the incorrect wiring between the Current Transformer and the DDC controller. To clarify this, please see below. The drawing shown as part of the installation instructions appears to show that four connections to the DDC controller are required, this is not connect, only two are required. The status output connections consist of two terminal sets, but only one connection is required from each. To download the H909HV-S6 datasheet please click HERE. ... View more

Issue SPU 1201 Universal Pressure Switch – Specification No. 131-1-201 SPU 1202 Universal Pressure Switch – Specification No. 131-1-202 Product Line Field Devices Environment Site requesting a Universal Pressure Switch Cause SPU1201 and SPU1202 obsolescence Original PDF specification sheet is available here: DS21602-0203.pdf. Resolution The SPU1201 and SPU1202 have been made obsolete per the supplier. The closest replacement options that we have are listed below: SPU1201 is a 0.2 – 4.0 Bar device. The replacement options are SPP920 Series SPU1202 is a 12 – 250 mBar device. The replacement options are SPP920 Series Refer to Product Announcement PA-00166 for the SPP920 series Differential Pressure Switches for neutral and slightly aggressive liquids and gases. ... View more

Issue TAC Vista to SmartStruxure interface is now available. It is possible to use SmartStruxure solution as the new user interface while maintaining TAC Vista running underneath. All controllers, TAC Vista Workstations, and TAC Vista Server(s) remain in place. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure Solution EcoStruxure Web Services TAC Vista SmartStruxure Interface 1.0 Cause Vista interface needs to be created in SmartStruxure so that SmartStruxure can get data from TAC Vista Resolution On the Vista server(s) install the TAC Vista SmartStruxure Interface first. Refer to TAC Vista to SmartStruxure Interface will not connect when TAC Vista and SmartStruxure are installed on the same machine if there are any issues installing or getting the two programs to communicate when on the same PC. In StruxureWare Workstation, on the Enterprise server object or the Automation server object right click and create new interface, and select the EcoStruxure Web Service interface in Workstation. Click next. In the Server, enter the IP address of Vista server. If it is local, just use localhost. Enter the username and password of Vista Server. Pay attention that only the user in the default System user group can be used. Don't try to create other System group. And all the letters in the password field need to be in capital letters. This is a defect that will be addressed in the next release of TAC Vista to SmartStruxure interface. Please be selective with the port that you are using. If the Vista to SmartStruxure Interface program is on the same PC as the Enterprise server than a different port other than 80 or 443 will have to be used. Please refer to TAC Vista to SmartStruxure Interface will not connect when TAC Vista and SmartStruxure are installed on the same machine if the two softwares need to be on the same machine. Click Create. The next step is to Host TAC Vista objects into SmartStruxure. Refer to How to host TAC Vista objects using Web Services in StruxureWare Building Operation for the guide of how to host Vista objects into SmartStruxure. NOTE: There is a defect for Version 1.0 of TAC Vista to SmartStruxure interface under Non-English operation system. The EcoStruxure Web Services interface will not come online in SmartStruxure. Refer to TAC Vista to SmartStruxure Interface does not connect in non-English Operation System for solution. ... View more

Issue A Door configured with Magstrike status as Door Status re-locks after 2s  even when Door Strike Time is set to 10s. Environment Continuum Access Control Cause The Door output will relock after the Door Strike Time or when the Door is opened. Since you are using the mag lock status as the Door status (not the preferred method), then as soon as the Door is unlocked, the mag lock is de-energized which turns off the Door Status which then relocks the Door 1s later. Resolution You need to monitor the actual physical status of the Door to indicate when it has physically opened and shut. Either that or remove the input from the Door object by setting the Door Status channel to 0. This should allow the Door to stay open the DoorStrikeTime. You can also use a PE program to get around not having a DoorStatus that monitors the actual Door. This post on the Community discusses this and has some good comments about using this type of Door control with the maglock status instead of a true Door Status switch and is worth a read. Below is an example Plain English program that can help monitor the Door for ValidAccess then hold the Door unlocked for the DoorStrikeTime. 1: If Door1 ValidAccess is On then Goto 2 If Door1 ExitRequest is On then Goto 2 2: Door1 = UnLocked If TS > Door1 DoorStrikeTime then Goto 3 ' wait for DoorStrikeTime 3: Door1 = Locked Goto 1 ... View more

Issue How to enable Continuum site for use with Endura DVRs and cameras. Product Line Andover Continuum, Pelco Environment Continuum V1.91 and above Pelco Endura DVR See the Video Compatibility matrix for supported Pelco Endura products on the various Continuum versions, Cause Want to enable Continuum for use with Endura but unsure which security keys support the addition of the option and what the option provides. Resolution Why is this option required? The Endura -E option for Continuum security keys is required to be able to: Configure VideoServer objects in Continuum to use Endura DVRs. Use VideoAdministrator and VideoMonitor to configure and view Endura cameras. It is not required to be able to configure and view cameras from DigitalSentry DVR's or to view Endura cameras using VideoLayout objects that have already been configured. Which Workstations can have the option added? SU and LAN Cyberstation security keys can be enabled with the Endura -E option. This option cannot be added to the WEBC key for WebClient Servers. If configuring Endura cameras is required, a Cyberstation with the -E option must be used. WebClient browser users are able to use the VideoLayout to view DigitalSentry and Endura cameras. The Endura option is only available through the upgrade process through Repairs. There is no part number to specify to enable Endura at the time of ordering the security key. Once you have the serial number of the key, contact Repairs below. Email: tacus.wlcrepair@schneider-electric.com How to tell if the option is enabled? If the system is operating normally (not in Demo Mode), open up a Video Server object. If the key is video enabled it should look like this: If it is not enabled, the Pelco Endura option is not available: ... View more

Issue After installed I/NET, DBCreate will never pop up to create a new database, which will cause I/NET never launches. Backup and Restore button are greyed out when opening DBCreate, which also will cause I/NET fails to launch. When restoring database, an error will show up, saying that version is incompatible with this server. When restoring the database, an access deny error will show up. Unable to create a backup of an I/NET Seven Database using DBCreate, gets a backup failed error. When restoring I/NET database backup from another server in DBcreate, it shows an error: Error dropping PRIMARY KEY 'PK_DvrServers': Could not allocate space for object 'sys.sysserefs'.'clust' in database 'InetDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause SQL default instance is not created correctly. SQL2005 BCM is not installed correctly if SQL2008 is used, or there is a database version mismatch for I/NET. This is usually caused by restoring new SQL database to old version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Windows permissions are not enough to do the restoring Functionality of the host pc and the database seems to be inconsistent. If the database size limit is reached, I/NET database will fail to update. The backup of the database will be fine, but when trying to restore onto another computer, it will also fail. Resolution If you are using I/NET 2.4x, and already have a named SQL instance on the computer (for example, TAC Vista 5.1.7 or higher has been installed, with a named instance installed called TACVista), I/NET may fail to recognize it, while also fail to create a default instance. Similar kind of warning will pop up during the I/NET installation: Under this condition, use your current SQL server installer or browse to /SQLExpress folder of I/NET installation CD, to manually create a new default instance. You can refer to the guide within the /SQLExpress folder about how to create it. As long as the default instance is created, DBCreate will pop up immediately and a new database can be created. If 64 bit Operation System is used, refer to Installing I/NET Seven on a 64-bit operating system for the detailed guide. Also refer to Installation guidelines for installing I/NET and Vista on the same PC for more details about installing I/NET and TAC Vista on one computer. If SQL 2008 or SQL 2008 R2 is used, be sure to follow the correct steps about how to install them: I/NET Seven with SQL 2008: I/NET Seven with SQL 2008 Installing I/NET Seven on a 64-bit operating system: Installing I/NET Seven 2.42 or higher on a 64-bit operating system If SQL 2008 is installed correctly, please refer to Data Base maintenance before performing an upgradeto perform a forced upgrade for the database. Refer to Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate: Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate Refer to DBCreate backup access denied using Windows Server 2008 R2 Standard and Microsoft SQL 2008 R2: DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2. Refer to Unable to Create a backup in DBCreate: Unable to Create a backup in DBCreate. Refer to Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached: Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached. ... View more

Issue StruxureWare Building Operation Satchwell MicroNet Integration - Supported MicroNet devices Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment StruxureWare Building Operation 1.3, 1.4, 1.5, 1.6 Satchwell MicroNet devices Cause Not all variants of older Satchwell MicroNet devices that use the SNP protocol and IAC   are supported by StruxureWare Building Operation.  Resolution Refer to MicroNet Devices on StruxureWare Building Operation Web Help (log on required) for a list of supported devices.  In Building Operation, MicroNet device is the family name for the following devices: Standard MicroNet devices: MN300, MN440, MN500, MN620, MN LCD, MN Touch Screen, and MicroNet Manager Interface MN 50 Series: MN350, MN450, MN550, MN650, MN LCD, MN Touch Screen, and MicroNet Manager Interface SNP and Intelligent Advanced Controller devices: MMC3601, MMC4601, IAC400, IAC420, IAC600, IAC Touch Screen, and Modem Interface Unit Unifact: URC2201, URC1201 Unifact Pro: URC-40N-100, URC-41N-10x, URC-50N-100, and URC-51N-10x All these devices are supported in Building Operation. ... View more

Issue What files are saved, to where and why is this used. Environment MPM-VA MPM-UN MPM-GW Cause The running database of a SmartStruxure Lite MPM controller is in the controllers volatile memory (RAM), in order for this data to be preserved during a power failure or reboot this needs to be saved to non volatile memory (Flash) Resolution The save period is for backing up the controller database to flash memory, this can be set to Never, Hourly or Daily. All programming and runtime information is then saved to the controllers flash memory so that it is not lost during a power failure or controller reset. Stored data includes Controller status, configuration changes, updates such as trended information or setpoint changes, and Lua scripts. ... View more

Issue Managing servers with Microsoft System Center Environment A site with Schneider Electric SmartStruxure Cause Microsoft System Center is a set of server products aimed specifically at helping corporate IT administrators manage a network of Windows Server and client desktop systems. Microsoft Servers (previously called Windows Server System) is a brand that encompasses a line of Microsoft server products. http://www.microsoft.com/systemcenter  Microsoft Software Asset Management (SAM) Is there a way to integrate Microsoft System Center with Schneider Electric SmartStruxure? Resolution Integration of Microsoft System Center with Schneider-Electric SmartStruxure has not been tested, nor is it supported. With System Center, the management of Server environments is outside of the installation and use of Schneider Electric SmartStruxure. ... View more

Issue Sites need guidance on how to setup custom ABA cards in Continuum. Environment CyberStation NetController I (CX99xx) NetController II (CX9680) AC1Plus IOU Module ACX57xx Cause The implementation of ABA cards in Continuum access control systems was designed to comply with the ISO 7811 ABA standard for magnetic stripe card. Because of this, the system only reads  one field (the PAN or Primary Account Number) from the ABA card, this field contains a number of up to 19 digits which is used as the card number. Continuum Custom ABA feature provides for maximum flexibility by allowing the 19 digit PAN field on track 2 of the mag stripe to be organized in sub fields such as site code etc. Resolution A summary of the steps to configure Custom ABA cards in Continuum is available through the CyberStation Online Help.  Open the help on the Continuum workstation and search for "Defining a Custom ABA String Format"           ... View more

Issue Using special characters or certain regional characters in the VisiSat Points gallery Environment special characters regional characters VisiSat Points gallery alt Cause This issue is specific to VisiSat version 2.1 Build 185. VisiSat 2.1 older releases (Builds 14, 17,137,148 sp1) are not affected. Example of some of the special characters available: Ù, Ú, Û, ©, è, é, ®, ±, ¼, ½, ¾, Ò, Ó, Ô, Õ. ° (Degree “alt+248”) Resolution Details of the issue and some options available to you are covered in TPA-SACH-12-0005.00 - VisiSat Build 185 Pointlist issue. ... View more

Issue Using AOL as email provider the following error messages comes every two days: 2014-06-12 15:11:06 E-mail was NOT sent: 521 5.2.1 MUST COMPLETE IMAGE PUZZLE BEFORE SENDING. PLEASE GOTO http://challenge.aol.com/spam.html Environment SmartStruxure Lite MPM AOL Cause This is AOL trying to stop people using its email service to generate spam, you are now required to periodically enter a series of numbers or letters from a web page in addition to normal username and password authentication. Resolution See AOL help to understand the issue further. This post on the internet also notes the issue and unfortunately this is something that AOL has added and is not under our control. ... View more

Warning Issue Upgrading Reports Server from 1.4.1 to 1.5 Environment StruxureWare Building Operation 1.5.0 Windows Server 2008 R2 Reports Server WebReports Enterprise Server Cause Failure to follow upgrade guides may result in data loss. The most likely point of failure seems to be running the Reporting Agent Service on the Reports Server while upgrading the Enterprise Server. The Upgrade will error out if SQL2008 R2 is not upgraded to SP2 or .NET framework is not upgraded to 4.5 at the indicated points. Resolution This resolution process was developed from the System Upgrade Reference Guide and tested on a single PC. Windows Server 2008 R2 at StruxureWare Building Operation 1.4.1 running SQL2008 R2 SP1 and .NET 4.0 upgraded to StruxureWare Building Operation 1.5.0 SQL2008 R2 SP2 and .NET 4.5.  You can find and download all 1.5.0 released software and documentation by searching the Building Download Center for the tag "relsbov1.5" Backup Enterpriser Server, All Automation Servers and Report Server. Store backups on external media. If desired, create a Windows snapshot for a quick return point. Download all StruxureWare Building Operation 1.5 Installation files, SQL2008 R2 Upgrade files and .NET 4.5 installer. Close all StruxureWare applications In the Windows Server Manager, Expand Configuration and Select Services Browse to “StruxureWare Reporting Agent”, right click on it and select stop Open Software Administrator and stop the ES service. Close Software Administrator In the Windows Server Manager - Services section, stop the service “Building Operation 1.4 License Server” Run the .NET 4.5 installer. If prompted to restart, select Restart Later. If the PC restarts on its own, verify that all services listed above are stopped before moving forward. (repeat on all PCs) Run the License Administrator 1.5.0 installer Run the Enterprise Server 1.5.0 installer; select the Upgrade current version option. Note the ports used. Port 80 should not be used for http communication when the ES is installed on the Same PC as the Report Server. If desired install the Project Configuration Server.  Be sure that the HTTP port is not the same as what is used for the Enterprise Server and not port 80 Open Software Administrator and verify that both the Enterprise Server and PCS are running and using different ports Install Workstation. If you are upgrading from 1.4.1 to 1.5 and planning to delay the upgrade of the Automation Servers, you should install Workstation in parallel instead of upgrading Install Device Administrator. If you are upgrading from 1.4.1 to 1.5 and planning to delay the upgrade of the Automation Servers, you should install Workstation in parallel instead of upgrading At this time, upgrade any required Automation Servers. If upgrading from 1.4.0, all AS must be upgraded together. Install any required language packs If required, download and install the SQL2008 R2 upgrade to SP2 : http://www.microsoft.com/en-us/download/details.aspx?id=30437The default file name for the upgrade installer is SQLServer2008R2SP2-KB2630458-x64-ENU.exe In Windows Control Panel, go to Programs and Features Uninstall the “Building Operation Reports Installation” application only. This is the installer application for 1.4 Web Reports Run the Reports Server 1.5.0 installer Browse to C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation Reports Installer Right Click on SE.SBO.WebReports.Installer and select “Run as Administrator” For Setup Type, select “Upgrade both software and database” Fill in site specific information as instructed. For Reporting Agent, be sure to specify the exact Enterprise Server Address and port used. Follow the remaining prompts to install WebReports On completion, log into the StruxureWare WebReports interface and run a few test reports. ... View more

Issue Using the OPT Block with a StruxureWare Time Schedule Object. Environment Function Block Editor Cause The Xenta Time Schedule which the OPT Block has the ability to send a positive or negative minutes till next change. The StruxureWare Time Schedule dose not include this item. This is the online help article that defines the parts of the OPT Block Resolution In the Function Block Editor, create 3 RI blocks. One will be bound to the Value attribute of the Analog Schedule One will be bound the ScheduleDefault attribute of the Analog Schedule One to the TimeToNextTransition attribute of the Analog Schedule Create an XPB block with the function "A!=B". Connect the Value RI to A and the ScheduleDefault RI to B. Label this XPB "Status". Create an XPI block with the function "a?B*-1:B". Connect the status XPB block to "a" and the TimeToNextTransition RI to B. This Block can be connected to the TmL input of the OPT block. This is an export of the demo application below which shows the bindings. (right click and choose Save link as...)   ... View more

Issue  When starting SigmaX, an error is reported, the error is: - This application failed to start because side-by-side-configuration is incorrect.  Reinstalling SigmaX does not help. Product Line Satchwell Sigma Environment SigmaX error Side by side configuration Windows 7 laptop Windows 10 laptop Cause SigmaX error when trying to run on a Windows 7 laptop. Resolution Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps: Open an elevated command prompt. Click Start > All Programs > Accessories Right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. Type the following command, and then press ENTER: sfc /scannow The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions. More Information about SFC scan can be found in this document: http://support.microsoft.com/kb/929833 At the command prompt, type the following command, and then press ENTER: sfc /scannow The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache. The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows. Note Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished. Please see Error when trying to run SigmaX.exe and RegSigmaX.exe for further information about Microsoft C++ Redistribuatables ... View more

Issue How to create a set of manual logs to show the state changes of a digital point with time stamps. Environment CyberStation Any CX Any i2s Cause Documentation Resolution How to create a report for a digital input that shows the input change of state with a time stamp.pdf ... View more

Issue What is the Intel Floating point number as used in the Modbus X Driver? Environment Modbus RTU X Driver Cause It is not clear how the two special floating point function codes vary. Resolution There are two different floating point data formats (248 & 245) these are both standard 32 bit floating point numbers but the data bits stored in memory (or read over the protocol) differently. The 32 bits of Function 248 are stored as one string of bits, bit 0 through to bit 31. For the 245 format the upper and lower words are swapped around, so it stores the data as bits 15 to 0, then bits 31 to bit 16. This format is called Intel format as it is the way Intel microprocessors handle floating point data. Here is a link to information on floating point numbers FYI: https://en.wikipedia.org/wiki/Floating-point_arithmetic These 2 formats can also be called Big Endian (Function 248), or Little Endian (Function 245). Little Endian is also known as the Intel format. Information on Endianness can be found at: https://en.wikipedia.org/wiki/Endianness ... View more

Issue Echelon Node Utility with Loytec NIC-USB Network Interface Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Microsoft Windows 7 32-bit Echelon Node Utility 2.04 Echelon OpenLDV 4.0 Loytec NIC-USB network interface Loytec NIC driver version 4.1.3 Cause There is a need to run Echelon Node Utility using Loytec network interfaces. Resolution The easiest way to accomplish this, is to use the NodeUtil Launcher. This program scans the registry for known interfaces. It was created by an active Community member. * Do take note Schneider Electric Product Support does not provide support for the NodeUtil Launcher - for support please write the developer of the tool. Below are two methods to manually achieve this if you don't want to use the tool. Here are 2 methods to run Node Utility using Loytec NIC-USB network interface. Method 1 involves accessing the Windows registry to check the path name of the Loytec network interface. We are not modifying any entries in the registry but as always, we should be careful when we access the Windows registry. Using Windows registry incorrectly can cause serious problems that may require you to reinstall Windows. Method 2 will configure the Loytec NIC-USB to use LON1. If you have used an Echelon LonWorks interface as LON1, you will need to detach it before you can use this method. Method 1 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity Run Windows registry editor (Start > Run > regedit). Navigate to the path HKEY_LOCAL_MACHINE\SOFTWARE\LonWorks\DeviceDrivers. The interfaces will be shown here. Look for the interface with '_LDV'. Run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil using the command nodeutil -D"". See example below. Method 2 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity. Click on the 'Advanced' button. Check the option 'LON1 Support for device' and select the appropriate device in the drop down list. You will need to reboot the computer for this to take effect. Once the computer has restarted, run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil. Node Utility should now run. ... View more