Issue Product specifications and application details for the SE 7000 or SE 8000 range of room controllers are required. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE8000 • SSL SE7000 Cause Full details of the products are required. Resolution The best source of information is in the online Product Selection: Room Controller Selector Tool This tool will allow you to select the correct unit for your application, then from the different tabs you will be able to see: Product Overview, Spec's, Dimensions, related accessories and to download the required documentation from the Links tab. Note: The installation guide can be downloaded from the Links tab and contains detailed application setup, product specification and dimensions. For BACnet versions of the controllers the PIC's statements can currently be downloaded from the Viconics section of the BTL official site using the corresponding VT7xxx part number, see link: BTL Listings for Room controllers Note: The SE8000 and SE8300 Series BTL Certification Listing is anticipated for late 2015.

Issue Can't display values from a Modbus IP device where it is using a data type of swapped Longint (32 bit). Environment Continuum Modbus IP XDriver (2nd Generation) v2.00012 and below CX9680 ACX5720, ACX5740 bCX1-9640, bCX1-4040 PM9C Power Meter Cause Modbus IP Xdriver did not support the swapped Longint (32 bit) data type. Resolution Support for this data type was added to the Modbus IP XDriver (2nd Generation) in v2.00018 which is available on The Exchange Download Center at the link below: E01_0210_215 Modbus TCP driver.zip

Issue Microsoft Security Update KB2744842, issued on September 21, 2012, prevents Internet Explorer 9 from remotely executing possibly malicious executable code contained in web pages. This security update prevents the Java applets used to display the G3 graphics from being downloaded into the browser.  After this security update is installed the graphic page will be displayed as a blank white page with or without a boxed red X in the upper left corner of the graphic page. For more information on the vulnerability, refer to Microsoft Security Bulletin MS12-063, available from the Microsoft web site. Use of alternate web browsers such as Google Chrome or Mozilla Firefox are not affected by the installation of this update. Environment I/A Series G3 ENS or ENC with web access Internet Explorer 9 being used to display the graphics pages. Cause Microsoft security update prevents Internet Explorer 9 from executing potential malware infected modules. Resolution If the ENC or ENS station is running the I/A Series G3 software release 3.4 or earlier, there is no module upgrade available to correct the issue.  A new web.jar module is available that allows Internet Explorer 9 to download and execute the Java applets used when displaying I/A Series G3 graphics. If the site is running G3 release 3.5.34, you will need to upgrade to release 3.5.39 with the latest security patches before installing the 3.5.403 web.jar file. If the ENC or ENS station is running I/A Series G3 release 3.5.39, upgrade the web.jar to release 3.5.41.1.  If the ENC or ENS station is running I/A Series G3 release 3.6.x, upgrade the web.jar to release 3.6.48.1. The upgraded web jar files are available on The Exchange Download Center. After installing the new web.jar module, the following cache folders must be cleared on any computer that has been used to attempt to view the G3 graphics from an unpatched G3 station running on an ENC or on an ENS-1 system. Clear the IE9 "temporary internet files" cache using the following procedure: From within Internet Explorer 9, select Internet Options from the Tools menu. On the General tab, select Browsing History then click [Delete]. Uncheck all check boxes except "Temporary internet files" then click [Delete]. Close the Internet Options window. Delete the wbapplet cache folder.  The location of the folder is  //users//niagara where is the login name of the current Windows user.  This folder can be accessed by typing the location into the Windows search box on the Windows Start menu. Clear the Java browser cache using the following procedure: Open Java from the Windows control panel. Click the [About] button on the General tab to verify what version of Java is installed. If running Java 6, On the General tab, in the "Temporary Internet Files" section of the window, click [Settings] then in the "Delete Temporary Files" window, make sure that "Downloaded Applets" and "Downloaded Applications" checkboxes are checked then click [ok] to delete the files.  When the delete process is complete, click [ok] to exit.. If running Java 7, On the General tab, in the "Temporary Internet Files" section of the window, click [Delete Files...] then make sure that "Downloaded Applets" and "Downloaded Applications" checkboxes are checked then click [ok]. Close the Java Control Panel window.  Note: These three caches must be cleared regardless of the browser being used if the web.jar file is been updated on the ENS or ENC being accessed.  If accessing some systems with the old web.jar file and some systems with the new web.jar file, it may be necessary to clear these caches any time you switch from accessing a system with the old web.jar file to a system with the new web.jar file.    There are two ways to resolve the issue when running G3 release 3.4 or earlier: Upgrade the installation to a newer I/A Series G3 software release (3.5.x or 3.6.x or when available, 3.7.x).  This is the preferred option because these newer releases correct many known issues with the release 3.4 and earlier versions. Use a browser that is not affected by the Microsoft Security update.  The known unaffected browsers include Mozilla Firefox, Google Chrome and Microsoft Internet Explorer version 7 or 8.

Issue Unable to connect to webClient using Mac and Safari as the browser. Environment webClient (all versions) Mac OSX Safari Cause Using an unsupported browser and operating system configuration. Resolution The only browser supported is Internet Explorer (IE), see the Compatibility matrix for details of supported hardware and software for webClient.

Issue Unable to access to JACE-645 via its Ethernet Port. The following is seen when connected to the JACE's Serial Shell. Product Line TAC I/A Series Environment JACE-645 (TRD-T-645) Cause The boot sector of the nand flash has become corrupt and/or the nand flash chip may have failed. Resolution The unit cannot be recovered in the field. The options are: An attempt can be made to re-image the unit but this may not be always successful. Contact Product Support for further details. Replace the unit. Refer to PA-00502 - End of Commercialization for JACE 600 and JACE 700 for replacement options.

Issue USB LON adapter from Echelon (PS3 Part Number:ECH-75010R) is not recognized by Workplace Tech. Environment USB LON adapter (ECH-75010R) Workplace Tech Cause The ldv32.dll file (Open LDV driver) loaded with Workplace Tech (located in C:\Program Files\WorkplaceTech directory) is an older version of the driver and it does not support USB interfaces. Resolution Download the latest version of the LDV driver (153-0212-01A_OpenLDV340.exe) The latest version of the LDV driver can be downloaded from the Echelon website (www.echelon.com) and it contains support for USB devices. In order to download from Echelon’s website, a (free) user account is required. Once it is created, proceed to “Recommended Downloads” and the LDV driver will be listed (towards the bottom) as "OpenLDV 3.4 Network Drivers for Windows Vista/XP/2000/Server 2003 (includes drivers for i.LON 10/100/600 RNI, PCLTA-20/21, PCC-10, and U10/20". The LDV driver is also posted on The Exchange Download Center. Install the new LDV driver Copy the ldv32.dll file from the C:\lonworks\bin directory, and paste it into the C:\ProgramFiles\WorkplaceTech directory. This driver is required for Workplace Tech version 5.6 or earlier. After installing the driver, Workplace Tech will now recognize the USB adapter.

Issue Information for UL 864 Smoke Control for Continuum Environment Continuum Cause Information is needed for UL 864 Smoke Control using Continuum Resolution There are a number of documents available on Exchange Online, click the following links to navigate to the document: Documents listed in the section include: UL 864 Power Supply Install UL 864 IO module Install UL 864 i2/b3 8xx-V Install UL 864 Infinet Smoke Control Design UL 864 Bacnet Smoke Control Design UL 864 Continuum Smoke Control Design UL 864 Fire Alarm Annunciation System Guide

Issue Does the LCM driver support tunneling? Product Line TAC IA Series Environment R2 UNC with LCM driver Cause Tunneling is needed to make programming changes to the LCM's. Resolution It is possible to tunnel through the UNC to the LCM's, but it requires an RS-232 connection from the UNC to one of the LCM's.  See the LCM Integration Guide F-27422-2 for details.

Issue Troubleshooting sending email alarms from a Xenta Server. Product Line TAC INET, TAC Vista Environment Xenta Server Xenta 511, 511:B, 527, 701, 711, 721 and 731 XBuilder SMTP Server Cause There are many reasons why an emailed alarm from a Xenta Server wouldn't reach the desired destination inbox. This document walks through the most common settings and networking issues and how to overcome them. Resolution Some Xenta Servers can be configured to send out alarms via email – 511, 511:B, 527, 701, 711, 721 and 731. Typically, following the instructions found in the TAC Vista Xenta Server – Web Server Technical Manual will result in successful delivery of email alarms. However, there are some factors that can hinder these email messages. This document is intended to address a few of the most common troubleshooting techniques to resolve these problems. The Basics The first step to getting Xenta alarms to email out is to properly configure the XBuilder project. Reference Chapter 5.2 Configuring the TAC Xenta Server for Email Forwarding in the TAC Vista Xenta Server – Web Server Technical Manual. Enter the address of the Simple Mail Transfer Protocol (SMTP) server as well as the authentication information (if any). If no SMTP server or login information has been provided, contact an IT professional at the customer's site to obtain this information. Alternately, for testing and demo purposes, Schneider Electric's SMTP server can be used – smtpservice.buildings.schneider-electric.com (port 25 or port 2525). If using Schneider Electric's SMTP server, set the Authentication to "TAC." Once the Xenta Server is correctly configured, set up Alarm Receivers in the XBuilder project. The steps for this can be found in Chapter 4.3 Configuring Receiver Groups in the TAC Vista Xenta Server – Web Server Technical Manual. Consider configuring the Alarm Receiver to email a distribution list as opposed to individual email addresses. Then the distribution list can be edited and maintained by the IT staff without ever having to access XBuilder projects or Xenta Servers. If everything is set up correctly, test the email capability by logging into the web interface of the Xenta Server and navigating to Utilities > Tools > Communication Tests. Enter a test email destination and hit "Test" as shown in Figure 1.  Figure 1. Test Send E-mail Message If the email arrives as expected, then the SMTP settings are all correct. A final test of the alarm receivers and alarm properties can be accomplished by forcing an alarm condition. If the email does not arrive as expected, check the following possible errors, or proceed directly to the next section of this document titled "Check SMTP Connectivity." Could not send the e-mail, error in mail configuration If this error results from sending a test email, then the settings in XBuilder need to be revisited and verified. Failed deliver e-mail, connection couldn't be established, check e-mail address If the test results in this error, proceed to the next section of this document titled "Check SMTP Server Connectivity." Check SMTP Server Connectivity In order to use an SMTP server, a connection must be established. In this example, the provided SMTP server is "smtp.ACME.com." Xenta Servers have a built in test function for determining the status of some of the defined devices. Log into the web interface and navigate to Utilities > Tools > Communication Tests.  Figure 2. Communication Tests From this screen, the connection between the Xenta Server and any of the defined gateways and servers can be verified. Select the radio button for Mail server 1 (SMTP) and hit test. Some possible results of the test are: ‘Mail server 1 (SMTP)’ is on-line If the mail server is online, but the test email still is not delivered, then the cause is most likely the authentication credentials of the Xenta Server. Check with an IT professional to verify the login account name and password that have been provided. Check that it has been correctly entered as described in the section of this document titled "Check SMTP Server Settings." If all of this is set up correctly and verified, proceed to the section of the document titled "Xenta Server Indicates No Errors." ‘Mail server 1 (SMTP)’ is off-line If the mail server is offline, then no communication exists. Make sure the SMTP server settings are correct. Refer to the section of this document titled "Check SMTP Server Settings." Also check the TCP/IP settings as described in the section of this document titled "Check TCP/IP Settings." If the SMTP server is outside the network, ensure that the default gateway is defined and test its availability with a communication test as shown in Figure 2. Lastly, connect to the network using a laptop and attempt to ping the SMTP server. If it is unavailable, contact an IT professional for assistance. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Figure 3. Failed Ping Example C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Figure 4. Successful Ping Example In Figure 4, the ping has returned four successful results. This will confirm that cables are connected properly, IP addresses are set, and any necessary gateway routers are communicating. It does not indicate ultimate success in connecting to the SMTP server. To check connectivity with the SMTP server, use a simple telnet command on port 25 (or the specified port) from a command prompt. C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com... Figure 5. Telnet command. If there is an error connecting, you will see this: C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com...Could not open connection to the host, on port 25: Connect failed Figure 6. Failed Telnet Command. If the connection succeeds, the command prompt will clear and show a new line beginning with 220. Type the word "helo" and press enter. The SMTP server should again respond but this time with a line starting with 250. Exit the telnet session by typing "quit" and pressing enter. 220 smtp.ACME.com ESMTP helo 250 smtp.ACME.com quit 221 smtp.ACME.com Connection to the host lost. C:\> Figure 7. Successful Telnet Session. If a connection can successfully be established through telnet, then the ports are open and SMTP messages should be successfully received from the Xenta Server. That does not guarantee they will be relayed by the SMTP server, so if emails are still not being delivered, continue troubleshooting with the next section titled "Xenta Server Indicates No Errors." Command not found If a telnet attempt results in the command prompt error "command not found" it is most likely because telnet is not enabled. In newer operating systems (Windows Vista/Windows 7) this feature is not enabled by default. To enable telnet: Go to Start > Control Panel > Programs and Features On the left side, select Turn Windows features on or off Scroll down to Telnet Client and check the box (see Figure 8 below)  Figure 8. Enable Telnet Client. Failed convert dns-name into ip-number If using DNS names for the SMTP server instead of IP addresses, a DNS server must be defined. A DNS server is responsible for resolving DNS names to IP addresses. Make sure the DNS server is online with a communication test as shown in Figure 2. To bypass any problems with DNS, enter the SMTP server IP address instead. This can be obtained by pinging the server as shown in Figure 3. Check SMTP Server Settings The SMTP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > SMTP.  Figure 9. SMTP Settings The fields shown in Figure 9 for "Outgoing mail server port" are not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and below, it is not possible to alter the default SMTP port. It is hard-coded at 25. The Primary SMTP will be provided by the site's IT staff. If authentication is required, then an account name and password must be provided by the IT staff. If the SMTP server is available, but no emails are being sent out, the authentication parameters need to be checked. Any further investigation at that point will require contacting an IT professional for assistance. Refer to the section of this document titled "Xenta Server Indicates No Errors" for some troubleshooting questions to pose. Also refer to "Contacting an IT Professional" for documents to use to facilitate these conversations. If no SMTP server has been provided, then Schneider Electric's SMTP server can be used. To use Schneider Electric's SMTP server for testing or temporary purposes, enter "smtpservice.buildings.schneider-electric.com" into the outgoing mail server. Mail server ports 25 and 2525 are available. Authentication is set to "TAC." This does not require an account name or password. This method is only recommended for testing purposes. Schneider Electric makes no guarantees as to the availability of the SMTP server. To ensure the email alarms are being delivered as promised, use an SMTP server with some guarantee of up time. Even if an SMTP server has been provided, consider defining Schneider Electric's SMTP server as a secondary server. It is not always a viable solution due to some network security settings and availability, but may increase the overall success rate of your email delivery by providing some redundancy. Check TCP/IP Settings The TCP/IP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > TCP/IP.  Figure 10. TCP/IP Settings The most important items to check on this screen are Default gateway and DNS server. If the default gateway is not properly defined, then external SMTP servers will be unavailable. If the DNS server is not properly defined, then SMTP servers defined by DNS names will be unresolved. Either enter a valid DNS server, or manually resolve the IP address by pinging the server as shown in Figure 3. If using Schneider Electric's SMTP server, DNS must be defined. Xenta Server Indicates No Errors If the test email was sent, but not received, and no errors were recorded, the focus should now shift to troubleshooting the SMTP server itself. Assistance from an IT professional will be helpful at this stage. Things to check include: Check the incoming/outgoing messages from the SMTP server. See if the messages from the Xenta Server are arriving but not being sent out. Many companies will set up an "allowed" list that will only pass emails from recognized IP addresses, and all else is filtered as spam. Make sure the Xenta Server's IP address is listed on the acceptable list. Ask what port the SMTP communication is using. Port 25 is typically used for SMTP communication, but some companies will change this for security purposes. Request that port 25 be opened for SMTP communication from the Vista Server. If this is not an option, the port can be changed in XBuilder/System Program versions 5.1.3 and later. See the section of this document titled "Changing the default SMTP Port" for instructions. Xenta Servers are hard-coded to use UTF-7 encoding. They require this encoding to support Swedish characters. UTF-8 is the most common encoding in America and Europe. Some networks may filter UTF-7 messages as spam. While this is not readily configurable, it can be manually changed by editing some files. Use an FTP program (Internet Explorer) to connect to the Xenta you are trying to change and download the \sys\langstring.cfg file. Edit the file and modify the following lines to replace all instances of 7 with an 8: ALARM_CODE_1= =?utf-7?Q? ALARM_CODE_3=charset=UNICODE-1-1-UTF-7 Upload the edited file back to the Xenta device and then cycle the power. The device will now use UTF-8 character encoding which is more commonly used in the United States. Remember that reloading the system program will erase these changes. Some companies will block all POP messages on the network. This will disable the ability to use external SMTP servers. Make sure POP messages are allowed or that the SMTP server is internal to the network. If you are trying to use an SMTP server of a different ISP than the one Vista Server is connected to, this will most likely be blocked by the SMTP server. This is known as mail relaying – something spammers can and will abuse. Changing the default SMTP Port Changing the default SMTP port is not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and before, the only options are to request for the IT department to allow use of port 25, or upgrade to version 5.1.3 or later. If you are using XBuilder/System Program version 5.1.3 or later, adjusting the default SMTP Port can be done through the web interface as shown in Figure 9. It can also be adjusted in XBuilder as shown in Figure 6.  Figure 11. Changing the SMTP Port in XBuilder Contacting an IT Professional If you need help contacting the customer's IT department to gather and share the correct data, use the document attached in Appendix A: IT Request for Information. A completed example is shown in Appendix B: Sample IT Request for Information. Disclaimer The information contained in this document is subject to change without notice. It is also subject to change with versions of TAC Xenta Servers. If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC building automation system installed on your site has the capability to email facilities personnel in certain situations. Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system. TAC Xenta Servers use standard Simple Mail Transfer Protocol (SMTP) for these messages. An SMTP server must be provided in order for these messages to be delivered. The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP):   Authentication required (choose one): Yes No Account name (if applicable):   Password (if applicable):   To distribution list (if any):   Required UDP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses):   Unit e-mail address:   From IP address:   Desired UDP port:   Appendix B: Sample IT Request for Information The TAC building automation system installed on your site has the capability to email facilities personnel in certain situations. Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system. TAC Xenta Servers use standard Simple Mail Transfer Protocol (SMTP) for these messages. An SMTP server must be provided in order for these messages to be delivered. The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP): smtp.ACME.com Authentication required (choose one): Yes No Account name (if applicable): emailuser Password (if applicable): password123 To distribution list (if any): facilities_staff@thebuilding.com Required UDP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses): facilities_staff@thebuilding.com Unit e-mail address: xenta@server.com From IP address: 10.10.10.20 Desired UDP port: 25

Issue Can not logon with the Mobile App Building Operation Technician Tool.  Logon screen appears but app closes after selecting Logon No objects are displaying in my Custom View folder or other locations  Can not view or acknowledge alarms My alarm display colors as set in Workstation are not displaying correctly in the mobile app  Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool 1.0.0 / 1.1.0 Building Operation Enterprise Server and SmartX Server 1.9.3 and below Cause May be various cause that are not allowing the Mobile App to connect to the server (Enterprise or Automation Servers), including EcoStruxure Web Services (EWS) Configuration Setting, folder names, User permissions and Alarm configuration.  Please review the different options below for assistance. Resolution Please note: Mobile experience to be replaced with EcoStruxure™Building Operation v2.0 WebStation For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool   When logging into the Technician Tool it times out This has been seen before and was caused by the Windows Firewall. If you are able to ping back and forth between the enterprise server and iPad/iPhone, then it may be a firewall issue. You can either shut down the Windows Firewall or use Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port to set up firewall rules.  Unable to connect to server or "Contact  technical support" message given When logging in to the Technician Tool, specify the HTTPS port in the SERVER field (EX: 192.168.10.20:446).   The mobile app uses the feature from Building Operation StruxureWare call EcoStruxure Web Services, as such a majority of issues can stem from this setting.  If you are having issues logging into the Enterprise Server or Automation Server using the Technician Tool check the following: Software installed on both the Enterprise and Automation Servers must be 1.3.0.938 or later? Ensure the EWS Server Configuration settings are enabled in the server. As a minimum Serve Value and Serve Alarm must be set to true Browse allows object to browsed if not set, no objects will be displayed Ensure the user has sufficient permission to log in and MUST be member of the default domain Values are not displaying in the Custom View folder or other locations Custom View folder must be located in the root directory of the Enterprise Server Check the EWS Configuration settings and ensure Browse is set to true - refer to item 2.2 above. In the EWS Configuration there is a tab labeled "Filter Hardware Folder"; Filters can be assigned By Path or By Object, check that the nominated folder or object has been filtered. Can not view or acknowledge alarms In the EWS Configuration settings ensure that the Alarm Acknowledge setting is set to true. Also check that the Alarm has no additional 'Enforcement', such as Cause / Action - these alarms can only be acknowledge through Workstation. My alarm display colors as set in Workstation are not displaying correctly in the mobile app Unfortunately the Alarm colors are hard coded within the Mobile App - this feature may be provided in a future release.  Date for this is currently unknown.

Issue Troubleshooting guide for LON bus communications Environment MNL controllers (MNL-50, MNL-100, MNL-110, MNL-130, MNL-150, MNL-200, MNL-V1R, MNL-V2R, MNL-V3R) Cause Troubleshooting guide for LON bus communications Resolution TPA-RKFD-09-0011.00 is a checklist which provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document.

Issue Troubleshooting sending email alarms from a Vista Server Mail error 1 – MAIL client needs to be configured first Mail error 2 – Couldn’t connect to server. Error:0  Mail error 2 – Couldn’t connect to server. Error:10022 Mail error 2 – Couldn’t connect to server. Error:10061 Mail error 3 – Couldn’t send message. Response:550 Mail error 3 – Couldn’t send message. Response:503 Unable to relay Product Line TAC Vista Environment SMTP Server Vista Server Workstation Cause There are many reasons why an emailed alarm from a Vista Server wouldn't reach the desired destination inbox.  This document walks through the most common settings and networking issues and how to overcome them. Resolution Vista can be configured to send out alarms via email.  Typically, following the instructions found in the TAC Vista Technical Manual will result in successful delivery of email alarms.  However, there are some factors that can hinder these email messages.  This document is intended to address a few of the most common troubleshooting techniques to resolve these problems. The Basics The first step to getting Vista alarms to email out is to configure the Server Setup.  Reference Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  Enter the address of the Simple Mail Transfer Protocol (SMTP) server as well as the authentication information (if any).  If no SMTP server or login information has been provided, contact an IT professional at the customer’s site to obtain this information. Once Vista Server Setup is correctly configured you must restart the Vista Server. After the Server has been stopped and restarted, set up an Alarm Control Object and an Alarm Receiver – Email.  The steps for this can be found in Chapter 18 Alarm Processing in the TAC Vista Technical Manual. Consider configuring the Alarm Receiver to email a distribution list as opposed to individual email addresses.  Then the distribution list can be edited and maintained by the IT staff without ever having to access Vista. If everything is set up correctly, test the email alarm receiver by forcing an alarm condition.  The alarm should show up in the Vista Alarm Queue as well as at the alarm receiver’s designated inbox.  If the email does not arrive as expected, proceed to the next section of this document titled “Check Vista for Alarms/Errors.” Check Vista for Alarms/Errors If emails are not showing up when expected, the first place to begin the investigation is in Vista Workstation’s Alarm Queue.  There are helpful messages that may appear based on some criteria.  The Alarms will all come from $EE_Mess object under the Vista Server.  Sort the Alarm Queue by Last Change if the alarm just happened, or by Object ID to find the $EE_Mess alarms. Server-$EE_Mess Mail error 1 – MAIL client needs to be configured first Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10022 Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10061 Figure 1.  Vista Alarm Queue Mail Errors There are three possible errors that can be seen in the Vista Alarm Queue.  They should occur within a few seconds of the alarm if there is an error connecting to the SMTP server.  If the alarms are acknowledged or disabled, they may not show up in the Vista Alarm Queue.  The other place to look for them is under the Vista database folder on the hard drive.  Inside the database structure there is a folder called $log.  Inside this folder should be a file called b0warlog.txt.  Open this file and scroll to the time/date where the alarm occurred.  If an error occurred, the same text that appears in the Alarm Queue will appear in the error log in a slightly different format.  An example: Mon Aug 17 08:16:26 2009 alrdisp >> Error from SMTPSendMail: Mail error 1 – Mail client needs to be configured first Three possible alarm conditions are discussed here: Mail error 1 – MAIL client needs to be configured first This error refers to the TAC Vista Server Setup.  Refer back to Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  If the server is setup correctly, be sure that the server has been restarted since the last change.  Changes in Server Setup will not take effect until the next time server is run. Mail error 2 – Couldn’t connect to server.  Error:0 Unknown cause. Mail error 2 – Couldn’t connect to server.  Error:10022 This error means that the SMTP server is unreachable.  If using a DNS name for the SMTP server, double check the spelling.  If everything looks correct, move to section of this document titled “Check SMTP Server Connectivity” and follow the steps described there. Mail error 2 – Couldn’t connect to server.  Error:10061 This error means that the SMTP server has been reached, but Vista was not allowed access to the server.  Double check the authentication username and password.  Re-enter the password to ensure it is correct (only dots are shown for privacy).  There are three different authentication modes to choose from: CRAM MD5 – (Safest) Password is coded with Message Digest 5. AUTH LOGIN – (Standard) Password coded with base64 method. LOGIN PLAIN – Password is sent uncoded. If the correct authentication mode has not been provided, it may require trying all three until the mail error clears.  If all three result in an error, contact an IT professional to be provided with a valid username and password.  Use the section of this document titled “Contacting an IT Professional” for a template to request this information. Mail error 3 – Couldn’t send message.  Response:550 Unknown user Unknown cause. Mail error 3 – Couldn’t send message.  Response:503 Must have sender and recipient first. Unknown cause.  If no errors occur in the Vista Alarm Queue or in the Vista alarm log text document, refer to the section of this document titled “Vista Indicates No Errors” for more troubleshooting techniques. For troubleshooting unknown errors, read Troubleshooting sending emails using WireShark. Unable to relay If an error "Unable to relay" is returned, this is most likely because authentication is not sent to the SMTP server. Go to Vista Server settings At the email tab set proper authentication (Vista Technical Manual Chapter 3.3 explain this more in detail) You may need to consult with the IT department on site Check SMTP Server Connectivity In order to use an SMTP server, a connection must be established.  In this example, the provided SMTP server is “smtp.ACME.com.”  Pinging is the lowest level of internet communication.  A successful ping will not guarantee communication with an IP device, but a failed ping will guarantee no communication.  Open a new DOS command prompt (Start > Programs > Accessories > Command Prompt).  Ping the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Figure 2.  Failed Ping Example In Figure 2, a request to ping the SMTP server has failed.  Check that the computer where Vista Server resides has internet connectivity (Start > Settings > Network Connections).  Make sure the connection status is Connected, navigate to an internet website, or ping a known IP address.  If those fail, check the computer’s IP settings.  Figure 3.  TCP/IP Properties - Obtain IP Automatically If the computer is set to obtain an IP address automatically make sure that an IP address has been assigned.  Figure 4.  Local Area Connection Status If no IP address has been defined, then the DHCP server is not available and the computer is not connected a network.  Check the physical connections and contact an IT professional to determine why the DHCP server is not assigning the PC an IP address. If the TCP/IP properties are configured to use a static IP address (which is common in applications where WebStation or ScreenMate are employed), then the DNS server address must also be defined if a DNS SMTP server is used.  Figure 5.  TCP/IP Properties - Static IP If DNS is causing problems, it is possible to bypass this by using the IP address for the SMTP server as opposed to the DNS name. Look back to Figure 2 to obtain the SMTP server’s resolved IP address.  In this example, the IP is 10.10.10.10.  Figure 6.  Using IP Address of SMTP Server When everything is set correctly, try to ping the SMTP server again.  This time, it should go through successfully, which is an indication that most of the basic settings are correct – but should not be viewed as indication that email messages will successfully be delivered by the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Figure 7.  Successful Ping Example In Figure 7, the ping has returned four successful results.  This will confirm that cables are connected properly, IP addresses are set, and any necessary gateway routers are communicating.  It does not indicate ultimate success in connecting to the SMTP server. To check connectivity with the SMTP server, use a simple telnet command on port 25 (or the specified port) from a command prompt. C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com... Figure 8.  Telnet command. If there is an error connecting, you will see this: C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com...Could not open connection to the host, on port 25: Connect failed Figure 9.  Failed Telnet Command. If the connection succeeds, the command prompt will clear and show a new line beginning with 220.  Type the word “helo” and press enter.  The SMTP server should again respond but this time with a line starting with 250.  Exit the telnet session by typing “quit” and pressing enter. 220 smtp.ACME.com ESMTP helo 250 smtp.ACME.com quit 221 smtp.ACME.com Connection to the host lost. C:\> Figure 10.  Successful Telnet Session. If a connection can successfully be established through telnet, then the ports are open and SMTP messages should be successfully received from the Vista Server.  That does not guarantee they will be relayed by the SMTP server, so if emails are still not being delivered, continue troubleshooting with the next section titled “Vista Indicates No Errors.” Command not found If a telnet attempt results in the command prompt error "command not found" it is most likely because telnet is not enabled. In newer operating systems (Windows Vista/Windows 7) this feature is not enabled by default. To enable telnet: Go to Start > Control Panel > Programs and Features On the left side, select Turn Windows features on or off Scroll down to Telnet Client and check the box (see Figure 8 below) Figure 11. Enable Telnet Client. Vista Indicates No Errors If no errors show up in either the Vista Alarm Queue or the $log folder, then Vista has successfully contacted a valid SMTP server.  Review Chapter 18 Alarm Processing in the TAC Vista Technical Manual.  Make sure that the alarm is using the correct Alarm Handler that is assigned the correct Alarm Receiver that has the correct valid email addresses defined. If the alarms are set up correctly, the focus should now shift to troubleshooting the SMTP server itself.  Assistance from an IT professional will be helpful at this stage.  Things to check include: Check the incoming/outgoing messages from the SMTP server.  See if the messages from Vista are arriving but not being sent out.  Many companies will set up an “allowed” list that will only pass emails from recognized IP addresses, and all else is filtered as spam.  Make sure the Vista Server’s IP address is listed on the acceptable list. Ask what port the SMTP communication is using.  Port 25 is typically used for SMTP communication, but some companies will change this for security purposes.  Request that port 25 be opened for SMTP communication from the Vista Server.  If this is not an option, the port can be changed manually using registry settings.  See the section of this document titled “Changing the default SMTP Port” for instructions. Look at the selected Text encoding in the Vista Server Setup.  Unicode (UTF-8) is the most common in America and Europe.  If encoding is set to UTF-7, some SMTP servers will filter the messages out as spam. Some companies will block all POP messages on the network.  This will disable the ability to use external SMTP servers.  Make sure POP messages are allowed or that the SMTP server is internal to the network. If you are trying to use an SMTP server of a different ISP than the one Vista Server is connected to, this will most likely be blocked by the SMTP server. This is known as mail relaying – something spammers can and will abuse. Changing the Default SMTP Port Vista defaults to using Port 25 for all SMTP communication.  This is the standard port for SMTP and is typically used by SMTP servers.  However, because it is so well known as the SMTP port, some companies prefer to change this as a security measure.  Request that port 25 be made available to the Vista Server.  Unfortunately, sometimes this is just not possible because of security procedures.  If a different port is required, it is possible to manually change the port by navigating through registry keys. Open up the Registry Editor on the Vista Server PC (Start > Run… > regedit).  Navigate to: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > TAC AB > TAC Vista > 5.1.2 > SMTP Depending on the version of Vista, the path may change slightly.  If a 64-bit operating system is being used, the path will be: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > TAC AB > TAC Vista > 5.1.5 > SMTP Navigate until the SMTP folder is located.  Inside the SMTP folder, the SMTP settings that were set with Vista Server Setup can be viewed.  There is also an additional registry key defining the port.  Figure 12.  SMTP Registry Settings If there is no registry key for Port, create one.  Right click in the key view window, but not on an existing key.  Select New > DWORD Value.  Name the new value “Port.” Double-click the Port registry key to edit.  Radio buttons convert the value from hexadecimal to decimal.  Ports are typically described in decimal values.  Switch to decimal, enter the required port number, and click OK. Figure 13.  Editing Port Registry Key Verify that the value had changed in the registry.  Vista should now be sending out SMTP communication on the required port. Contacting an IT Professional If you need help contacting the customer’s IT department to gather and share the correct data, use the document attached in Appendix A:  IT Request for Information.  A completed example is shown in Appendix B:  Sample IT Request for Information. Disclaimer The information contained in this document is subject to change without notice.  It is also subject to change with versions of TAC Vista.  If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP):   Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable):   Password (if applicable):   Text encoding (if filtered):   To distribution list (if any):   Required TCP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses):   From name:   From email address:   From IP address:   Desired TCP port: 25 Appendix B:  Sample IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP): smtp.ACME.com Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable): emailuser Password (if applicable): password123 Text encoding (if filtered): UTF-8 To distribution list (if any): facilities_staff@thebuilding.com Required TCP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses): facilities_staff@thebuilding.com From name: Vista Server From email address: vista @server.com From IP address: 10.10.10.20 Desired TCP port: 25

Issue PCT does not run properly following installation. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) 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. Cause Certain environmental settings may need to be adjusted in order to successfully install PCT. These settings are not described in the Project Configuration Reference Guide. Resolution If you have issues successfully running PCT after installation, check the following items: Enable Virtual Hardware Acceleration in BIOS Use this tool to check if virtual hardware acceleration is already enabled on your PC: Intel: https://www-ssl.intel.com/content/www/us/en/support/processors/processor-utilities-and-programs/intel-processor-identification-utility.html AMD: https://support.amd.com/en-us/search/utilities?k=virtualization Disable all Ethernet Adapters except the one in use (Only applies to Server Mode): It may be necessary to check Windows Device Manager for hidden network adapters Disable the Windows firewall Disable Anti-Virus Software A true local account may be needed to install and/or run PCT due to Group Policy or other factors. Use Run as Administrator for both installing and running PCT Note: You can right-click the PCT icon, open properties, select the “Compatibility” tab, and check the box “Run this program as an administrator” Test PCT by opening up the software application, creating a project, creating a server, and opening it up in WorkStation If PCT opens and works then enable Windows firewall and Anti-Virus program. - User may need to allow PCT in Windows firewall and PCT utilize port 9091 as default. - User may need to add exceptions within Anti-Virus software settings. We recommend installing Microsoft Fix 50410 to prefer IPv4 over IPv6. This software can be found here: - https://support.microsoft.com/en-us/kb/929852 - Choose the following download: Prefer IPv4 over IPv6 in prefix policies.

Issue In Vista 5.1.8 the line break character of the internal trend log file format was changed from the previous CR+LF to LF.  This can break some third party reporting and editing tools. Environment Vista 5.1.8 Cause In Vista 5.1.8 the line break character of the internal trend log file format was changed from the CR+LFof previous versions to LF Resolution Apply Hotfix 38 to Vista 5.1.8.  This restores the trendlog file format used in previous versions.

Issue TAC Xenta programmable controllers (28X, 30X, 401) can have trend logs stored in memory on the controller.  Each programmable device has a different amount of storage space allocated to trends. Product Line Field Devices Environment Xenta programmable controllers (280, 281, 282, 283, 300, 301, 302, 401, 401:B) Cause The settings of a Xenta trend log (how often a point is read, how much data is stored) need to be made with the memory capacity in mind. Resolution This information can be found on the following data sheets :  Xenta 280, Xenta 300, Xenta 401. Each of the programmables can hold up to 50 trend log definitions.  But the frequency of the polling and length of storage for the trends need to be altered.  The limitation in memory is how many data points can be stored, and is dependent also upon the data type. Trend Logging in the TAC Xenta 280 Total logging capacity approx. 650 floating point numbers   or approx. 1,300 integers   or approx. 10,000 digital values   Trend Logging in the TAC Xenta 300 (HW2 or higher) Total logging capacity approx. 4,000 floating point numbers   or approx. 8,000 integers   or approx. 60,000 digital values   Trend Logging in the TAC Xenta 401 Total logging capacity approx. 7,000 floating point numbers   or approx. 15,000 integers   or approx. 110,000 digital values

Issue Is I/NET capable of translating “large” key/card numbers (i.e., numbers greater than 24,000) directly to a lower number? Environment I/NET site with access control Cause I/NET capable of translating “large” key/card numbers (i.e., numbers greater than 24,000) directly to a lower number? Resolution The I/NET system is capable of translating “large” key/card numbers (i.e., numbers greater than 24,000) directly to a lower number, without the use of the Key/Card Translation table. However, this functionality requires that the SLI and DPU binary loads are I/NET 2000 revision 2.x or I/NET Seven revision 1.x (or later) compatible, and that DIP switch 7 at the DPU is ON. For DPUs with earlier firmware versions, the use of the Key/Card Translation table is still required when key/card numbers are greater than 24,000. Refer to TCON300 for more details.

Issue Is there a way to translate Cyberstation to a language other than English and use different SQL collation sequences and code page? Product Line Andover Continuum Environment Continuum Cyberstation Cause Standard Cyberstation installation installs the SQL using Code Page 850 1.x Strict compatibility. Resolution The link below is to the Language Translation support guides. These provide detail on how to translate the Continuum Cyberstation user interface to a different language. It also details in Chapter 3 how to use a different SQL sort order. This would allow the use of different character sets for use in personal names Language Translation Support Guide V1.81 Language Translation Support Guide V1.94 Also, there is an additional Continuum Language Support document available in MSWord format Here. For Arabic specifically, additional MSWord Document Here.  There are freelancers that can be of assistance to help with your site. Upwork is a site with potentially low-cost translators. NOTE - No testing has been done with Continuum v2.0 due to a lack of demand for translation See Andover Continuum v2.0 Language Translation

Issue Transferring an I/NET Seven system from one PC to another Product Line TAC I/NET  Environment I/NET Seven Site Cause Customer needs to transfer I/NET between two computers Resolution Perform the following steps: Install I/NET Seven on the new PC. Using DBCreate.exe, create a backup of the I/NET database. Copy the backup to the new PC and restore it using DBCreate. If the database needs to be upgraded it will prompt you.  Proceed with the upgrade.  Copy the save files, graphic pages, archives, any custom reports, custom symbols, and custom BIN files (ICI bin files) to the new PC using the same directory path as the previous PC to guarantee that graphic links will still work. The following are default paths for these files assuming it was not an upgrade from I/NET 2000. If it was an upgrade from I/NET 2000 please consult TCON298 the Getting Started guide which includes I/NET 2000 paths. Default location for Archives: C:\Program Files\INET Seven\Arch\ Default location for BIN Files: C:\Program Files\INET Seven\Data\ Default location for Reports: C:\Program Files\INET Seven\Reports\ Default location for Save Files: C:\Program Files\INET Seven\Sav\ Default location for Bin Files: C:\Program Files\INET Seven\Data\ Default location for Graphics: C:\Program Files\INET Seven\ Take a screen capture or write down the active configuration profile in I/NET configuration and manually fill this information into I/NET configuration on the new PC and make it the active configuration profile. Transfer the communication medium to the new PC (serial cable or Ethernet cable) and if communicating via NPR’s set the IP address of the new PC to match that of the old PC and remove the old PC from the network to avoid IP address conflict. Start up I/NET, login, and edit the Host Computer->Network Configuration to verify that the PC is communicating with the controllers.

Issue Transfer SNVT (network variables) between lon devices in a TAC Vista Classic scenario. Can't bind in classic network; how to send SNVTs from one lon device to another? Environment TAC Vista Classic scenario LonWorks devices Cause If you are using TAC Vista in a classic scenario, no real SNVT bindings can be made. Resolution Use object transfer to send the values. Note that the server have to be running for the values to be transferred. For more info on how to set up object transfer, see Chapter 14 in the TAC Vista Technical Manual.

Issue Why are transactions/messages showing up in double, triple, etc in I/NET Product Line TAC INET Environment I/Net revisions 2.xx Cause The table linking for each of the reports and establishing a link between RptIndividualHistorz.TenantNdx and the RptCards.TenantNDX Resolution In versions of I/NET when using the I/NET client as a remote client, you must uncheck all the Host Masks on each remote client, otherwise, the Messages and transactions show up multiple times. If not using a Remote Client, the following solution may help you. Refer to the TCON301.