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 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. 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  

Issue Unable to add trend /extended trend logs after upgrading from SBO version 1.8 to 1.9 Product Line EcoStruxure Building Operation Environment Upgrade from v1.8 or below to v1.9 or above Cause The number of trend log records in the server have exceeded the limit. No new trend log or extended trend log can be added to the server. See Architectural Guidelines v1.8 and Architectural Guidelines v1.9, The maximum number of trend log records in an Enterprise Server is 2.5 billion, and  SmartStruxure server device (AS, ASP,ASB) is 10 million In v1.8 and before, these trend record limits were soft limits. From v1.9, these are now hard limits. Thus it is not possible to save more than these amounts.  Resolution The logging numbers should be reduced below these limits 

Issue Not getting the pop-ups or the sound when alarms are generated in the Vykon 2.50 Alarm Service (VAS).  However, alarms are being logged to the VAS. Environment  R2, Niagara version 529, 532, 535 Cause No cause stated. Resolution The new vas-2.301.536.v1.jar and vasClient jar files were created to correct the pop-up issue. This resolution applies to the VAS 2.50 Client and the vas-2.301.532.v2.jar. VAS 2.301.536.v1 JAR Files and Client can be downloaded from The Exchange Download Center. Installation of the new vas-2.301.536.v1.jar file Stop the Enterprise Server running the VykonAlarmService Open Windows browser and go to C:\niagara\nre\modules Rename the current vas-2.301.532.v2.jar with the “.old’ extension Copy the new vas-2.301.536.v1.jar file to C:\niagara\nre\modules Restart the Enterprise Server.   Installation of the new vasClient.jar file Stop the VAS 2.50 client. Open Windows browser and go to C:\Program Files\Tridium\Vykon Alarm Service Client 2.50\lib Rename the current vasClient.jar with the “.old” extension. Copy the new vasClient.jar file to C:\Program Files\Tridium\Vykon Alarm Service Client 2.50\lib Restart the vasClient. The vasClient alarm pop-up, along with its sound, should now be displayed when an alarm is generated.

Issue Not receiving any messages or transactions from a single link even though the other links are working. Environment I/NET Seven (any revision) Xenta Server 2.x Cause Xenta Servers of this revision will sometimes lockup if a high volume of IP traffic is received and not send through any events or alarms through to the designated Hosts, even though everything else appears to be operating correctly.  You can locate this issue by viewing the I/NET Command "inet ip" through the Xenta Server web interface.  What you will see is an usually high number of messages in the Msg column (as shown below): Resolution To re-establish AMT from the link, the quickest fix will be to reset the Xenta Server.  This can either be done by a simple power reset or a Warm Start command through the Web Interface, Tools, Commands option.  This will usually get the device up and running. If you are running an old version of software then it is always recommended to have the latest version firmware in the Xenta Servers.  This can be downloaded from The Exchange

Issue Niagara G3 revision 3.5.25 guest login can result in NullPointerException. When using the guest account, depending on the authentication scheme being used the following error could be encountered when accessing the station from the browser: java.lang.NullPointerException at com.tridium.web.WbServlet.logon(WbServlet.java:272) at com.tridium.web.WbServlet.service(WbServlet.java:86) at com.tridium.web.SysServlet.serviceSpecial(SysServlet.java:149) at com.tridium.web.WebProcess.service(WebProcess.java:66) at com.tridium.web.SysServlet.service(SysServlet.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at com.tridium.httpd.ServiceThread.handleRequest(ServiceThread.java:283) at com.tridium.httpd.ServiceThread.run(ServiceThread.java:85) Environment I/A Series G3 Cause The web.jar file is outdated. Resolution Upgrade web.jar file revision 3.5.25. to web.jar file 3.5.403.  Procedure details: Download web.jar 3.5.403 install new jar file in Enterprise Server or ENC

Issue Is it possible to use a new Xenta (v.3.84) with an old version of TAC Vista? Environment TAC Vista 5.x TAC Xenta 302, TAC Xenta 301, TAC Xenta 401, TAC Xenta 28x Cause New orders for Xenta programmable controllers always come as the latest version. If there is a need to add or replace a device in an old installation will there be a problem? Resolution It is ok to use newer version of Xenta controllers in older TAC Vista installations. It is also okay to downgrade to an earlier 3.x version if desired. For more info see TAC Vista Compatibility Matrix.

Issue A modem is already connected to a remote site's tap. Settings in the modem need to be changed. Can this be done by dialing into the modem in its present configuration? Product Line TAC INET Environment I/NET remote site communicating via dialup modem Cause The remote site's modem needs to be connected to a PC or Laptop. Resolution No, a modem can not be configured by using its present configurations. Windows HyperTerminal is suggested to edit modem settings.  Refer to TCON 226 (Dial Applications) and TCON 101 (Taps and Repeaters). For emulated tap set up, refer to the appropriate Controller TCON. Issue A new SCU 1284 out of the box that you are setting up and it shows up with an * in Netcon. Product Line TAC INET Environment SCU 1284 Netcon Cause SCU's manufactured before 2009:  There is really nothing wrong with the SCU itself, but there may be an Eprom on the board that is not the correct one. It is the one that is used for the SCU 1280. Newer SCU's: This is generally caused by an incorrect setting in the MCU configuration Resolution Verify that you have the correct MCU configuration settings.  An SCU 1284 should be set to DPU.  An SCU 1280 or 1200 should be set to DIO.  Check Network configuration to see if the issue has cleared up. If it has not cleared up try the following: Delete the item from Network Configuration and allow it to repopulate. Ensure that the DIP switch is set to the correct address. Follow the instructions to reset the SCU located in Reset Instructions for 1200 Series SCU.  Then reload the bin file. If you are still having issues then the best option is to send that unit back and have it replaced with another.

Issue New MNET-CI and MNET- Air Balance software for MicroNet 2000 controllers is compatible with Windows XP and Vista. Environment MicroNet 2000 software;  MNET-CI and MNET- Air Balance, Version 4.0 Cause Release of software  MicroNet 2000 software;  MNET-CI and MNET- Air Balance, Version 4.0 Resolution New versions of MNET-CI and MNET- Air Balance software for MicroNet 2000 controllers are compatible with Windows XP and Vista. The software is bundled with the 6 PSI tools in a zip file, PSIv4.1.zip.  The zip file includes an installer and a READ.ME file that includes Release Notes and Installation Instructions. The same converter, MN-CIM, that works with existing version of MNET-CI and MNET-Air Balance, will also work with the new version. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available)

Issue Receiving Large Incorrect numbers in the log viewer. Environment Continuum 1.9X Windows XP Netcontroller II 9680 Cause NetController II needs updates. Resolution Go to: The Exchange Download the latest  NetController II  Flash. Edit the controller. Update OS Reload the controller.

Issue Need to re-license I/A Workplace Tech, have already used 3 of the 365 day licenses. Is there a way to add another one?   Environment I/A Series WorkPlace Tech Tool Software  Cause Renewal license limitation. Resolution Use the file WPTLExtractor.exe. This exe file allows for up to (15) - 365 days license renewals. Review TPA-RKFD-09-0025 for additional information.

Issue Need to add some RTD sensors to a 7716 PCU. I need a P8RTD expansion card. Environment I/NET site Cause  Can I order a P8RTD expansion card? Resolution This expansion card is obsolete. Please refer to the TCON096 for current information on accessories and expansion for the 7716.

Issue Do NPRs use downloadable firmware? Environment I/NET site Cause Do NPRs use downloadable firmware? Resolution Like many I/NET devices, the NPR has downloadable firmware. Refer to Chapter 5, Controller Functions. (TCON209, 2-26)

Issue Can I add a NC2 9680 controller to Continuum 1.74 Environment Continuum 1.74 CX 9680 NC2 Cause CX 9680 compatibility with Continuum 1.74 Resolution Controller NC2 9680 is supported on Continuum Cyberstation with 1.74 service pack 2 Go to the Buildings Exchange Extranet Download and install SP2 for each Continuum workstation on site. Follow the directions in the readme file located in the service pack.

Issue Multiple Menta Variable errors in the TAC Xenta 700 error log and, if running TAC Vista, also in the event log Environment TAC Vista 5.1.7 TAC Xbuilder 5.1.7 Xenta 700 system software (firmware) 5.1.7-51 (5.1.7-SP2) or 5.1.7-52 Cause When releasing TAC Xenta 700 5.1.7 SP2, an error was introduced to the firmware if the ERROR block exists in the TAC Xenta 700 Menta object. The error you see in the Xenta 700 error log will look similar to the following: 138   2013-01-15 14:29:18 minor   menta menta           138  alarmstate.anyun       Menta: Variable error   (Error#:62466) Resolution This issue has been fixed in the TAC Xenta 700 5.1.7 SP3 release, available for download at Exchange Extranet. After a successful update the firmware version will read 5.1.7-53.

Issue An Energy Expert system is being moved to a new server and/or the virtual image is being upgraded. The historical records held in the SQL database of the Power Monitoring Expert (PME) system need to be backed up and properly restored on to the new server. Product Line EcoStruxure Building Operation Environment EcoStruxure Energy Expert (formally Power Manager) Power Monitoring Expert (PME) Enterprise Server Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause The system administrator has deemed it necessary to upgrade the Windows server that the Energy Expert system is installed on for security and/or resource reasons. Resolution It is important to remember that an Energy Expert installation is really just two Schneider Electric offers, EcoStruxure Building Operation and Power Monitoring Expert, installed together and set up to pass information back and forth. This means that appropriate steps must be followed for each system to backup the historical data and properly restore it on the new server. For more detail regarding how the system is laid out, please see the Difference between EcoStruxure Energy Expert (Power Manager) and Power Monitoring Expert (PME). Steps to move an Energy Expert database Backup the Power Monitoring Expert (PME) SQL database, dashboards and reports. The Configuration Manager tool available on the Exchange can be used to back all of these items up automatically. Run the tool on the existing server and it will create a zip file to be used later on when restoring to the new server. See Migrating a PME 8.0 System to a New Server for more information. The Schneider Electric Technical FAQs website also contains many other helpful troubleshooting articles for PME including different versions of the product. Return the Energy Expert license(s) from the Floating License manager in order to move them to the new server. For more information see Video: Licensing Guide for Power Monitoring Expert (PME) 8.x and 7.2.x and ENM 8.3.x. If moving the Enterprise Server, make a historical backup of the EcoStruxure Building Operation (EBO) ES from the existing server. See Backup of StruxureWare/EcoStruxure Building Operation AS and ES for more information. If the Enterprise Server and other EBO licenses are installed on the existing server, then they may need to be returned as well so they can be moved to the new server. See Removing a Local License or Returning a Network License for more information. Next the ETL project files must be retrieved and saved so they can be moved to the new server (if using architecture 1 in the Energy Expert offer). Go to the file location below and save all ETL project files that are needed on the new server. C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs If moving the Enterprise Server, install the EBO software on the new server, rehost the EBO licenses, and restore the EBO server backup(s). See Restoring the EcoStruxure BMS Server for more information. Install the Energy Expert software (the software includes PME, ETL and the integration utility). The information on how to download the Energy Expert software can be found on the Exchange. Once the software has been installed, the Energy Expert license can be hosted to the new server in the Floating License manager. Next, install the PME Configuration Manager tool on the new server. The zip file from step 1 can be loaded using this tool to restore the SQL database, PME dashboards and PME reports. Add the previously saved ETL project files to the same location on the new server C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs Since the server has changed, the configuration settings must be updated in the ETL projects to reflect the new server name. The settings in the EWS interface on the EBO server will also need to be updated as well. Note: It may be easier to delete the existing EWS interface in EBO and then use the integration utility to create a new XML import file to simply rebuild the interface.

Issue Monitor the communication integrity of sub-LAN smoke control points Environment sub-LAN controllers Smoke Control Cause Smoke control systems must maintain communication with the sub-LAN controllers at all time. Interruptions in communication must be immediately known and responded to. Resolution Create a single point that will go OLD if communication is lost to any of the smoke control sub-LAN controllers. Refer to TCON 231, Smoke Control Systems, Manual, sub-LAN monitoring for more information.

Issue When the card reader is set to "CARD and PIN" it will wait for 10 seconds for the valid pin after a valid card has been swiped. There is no visible setting to set to be able to change this PIN timeout. Product Line Security Expert Environment Security Expert Server SP-C Cause The default timeout setting of 10 seconds between displaying a card and entering PIN can in some situations be too short. In other situations it may even be that the timeout of 10 seconds is too long for security reasons. There is therefore a need to adjust this timeout value. Resolution From SP-C firmware version 2.08.0843 and forward, there is a Door command called DualCredPendingTime that enables adjusting the timeout for supplying credentials for authenticating a user, such as Card and PIN. In Security Expert Client, go to Programming > Doors. Select the door you want to configure on the left. Expand COMMANDS Enter DualCredPendingTime = # where # is the timeout time in seconds. See example with a 20 second timeout set below. See also the Security Expert Release Notes page 30.

Issue What is the replacement or repair options for the Model 7728 Series I/SITE I/O Controllers? Product Line TAC INET Environment I/NET site Model 7728 Series I/SITE I/O Controllers Cause Failure or issue with the 7728 controller. Resolution For repair there is a set price one can acquire from the repair department.  For replacement: Order a 7798B Put a CLX card on it Order a 7718 controller for the triac outputs It is complex, but the 7728 was a blend of all of these components.  For the 7728, here is the TCON114 and the Marketing Brochure.

Issue What Techniques can be used to troubleshoot Modbus TCP/IP X Driver? Product Line Andover Continuum Environment Continuum Modbus TCP/IP X Driver Cause Advice/ tips required to help isolate & determine Modbus IP communications problems. Resolution The first thing to check is that you are using the latest release of the driver and manual, also that it is the correct one for the controller model you are using, currently V2.00002 for the 1st Generation controllers (e.g. Netcontroller CX9900 etc) and V2.00018 for the 2nd Generation controllers (e.g. Netcontroller II and bCX1). Download Modbus TCP/IP xDriver. Ensure you are using only 1 XDriver for all your Modbus IP comms, if say you are using Comm1 as your X Driver enabled port then all of the Modbus IP points must be under Comm1, you cannot have 2 X Driver ports loaded with this X Driver (See Can multiple Modbus TCP/IP XDrivers be installed on a single 2nd Generation NetController?). The following points should be checked with reference to the Modbus TCP/IP X Driver Manual downloaded with the software: Set the X Driver accordingly for Client or Server mode (Client mode and will be polling the 3rd party devices, server mode responds to requests for data). Check that your Configuration point has been setup correctly as a Infinity String and the parameters are correct for the mode you are using. For Client mode check that Param 1 is set to a polling rate that the 3rd party devices can cope with also that Param 3 is long enough for the devices to respond between 20 and 60 seconds. Use Parameter 4 to enable the error logging in an appropriate date format, this will then put the errors into the String array behind this point, ensure you have set the log size to say 50, automatic log and the interval to be 0 (a semi automatic log See How to log data only when a point changes). This will then log the error in the string each time they occur, you can view these errors with a function that loops for the log size printing out each line to the Message Window, or put a number of lines of the error log array lines on a graphic as lines of text. Create a Remote Device Status point to monitor the state of the remotely connected Modbus IP servers, again this can be put on a graphic to show which devices are on/offline. By selectively disabling or removing some of the X Driver points you can limit the polling to certain devices, that way each device can be tested in turn. Another tool that can help debugging Modbus IP comms is Wireshark as it allows you to monitor the IP comms between the Client and the Servers. Check the correct addressing and function codes are used in the polls and that the servers are responding correctly. As per the Compatibility Matrix check that your NCII has a compatible firmware loaded for the Cyberstation software used (2.0x or 2.1x) In Client Mode, ensure the 3rd party system does not poll the driver too fast, see Typical data throughput rates for Modbus XDrivers. Ensure the Xdriver Objects (usually Numerics) have correct details within the Parameter Fields. An incorrectly formatted IP address can cause the Controller to Cold Start following a download. The quickest way to check the Parameters is to load the Controllers with all the objects apart from the Xdriver Configuration String, then create a listview with parameters 1 to 6.  

Issue Minimum CFM not maintained when MR-VAV-AX goes into un-occupied mode. Environment I/NET MR-VAV-AX Cause As shown on Page 51 of TCON 147, this is part of the design of the VAV.  Resolution If you must maintain a minimum CFM. Remove any schedules or calculation point extensions that may cause the box to go to unoccupied state. Set the Loc Occ (Local Occupancy) to Occupied and disconnect local occupancy sensor Set the MCI Occ to on As stated in TCON 147 page 51.  When in any un-occupied Mode, Minimum CFM is not used. The system will toggle between 0 CFM and Cooling High Flow depending on box load.  Also note that if Central Plant Heat is not enabled. Then there will be no call for heating when Un-occupied.