Building Automation Knowledge Base

Issue What are the differences between the Niagara G3 ENS-UNL, ENS-LMT-100 and ENS-LMT-3? Environment Niagara G3, Workbench all versions Cause The Enterprise Network Server datasheet does not indicate these part numbers and their differences.  Resolution - ENS-UNL (formerly ENS-1) Enterprise Network Server (ENS) with support for connection to Unlimited Enterprise Network Controllers (ENC). - ENS-LMT-100 Enterprise Network Server (ENS) with support for connection to 100 Enterprise Network Controllers (ENC). - ENS-LMT-3 (formerly ENS-LMT) Enterprise Network Server (ENS) with support for connection to 3 Enterprise Network Controllers (ENC). Note: All ENS includes Workbench as standard. - ENS-LMT-100-UP Upgrade from ENS-LMT-3 to ENS-LMT-100 - ENS-LMT-UNL-UP Upgrade from ENS-LMT-100 to ENS-UNL Upgrade of controller limit from 3 to no limit requires purchase of both upgrade parts. * Upgrade of controller limit from 3 to no limit requires purchase of both upgrade parts.  

Issue This issue has been seen Modbus TCP between I/A Series G3 ENC and Eaton PXM meters where the PXM does not respond to the ENC within the message timeout period.  The ENC discards the request and sends a new message with a different transaction ID. The Eaton PXM meter responds using the previous transaction ID causing the ENC to discard the message and generate an error. Environment I/A Series G3, ENC-410, ENC-520 Cause Transaction IDs become out of sequence. Resolution The driver now recognizes that the device is responding out of sequence and resets the session with the device. Upgrade ModbusTCP module to revision 3.5.34.1 or newer. 

Issue Getting error for Weather Server:  ERROR [19:32:28 06-Sep-11 EDT][http.proxy] Error resolving www.weather.gov java.net.UnknownHostException: www.weather.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:369)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.net.BHttpProxyService.get(BHttpProxyService.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getAdvisories(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) WARNING [19:32:29 06-Sep-11 EDT][weather] Unable to load advisories for zone MIZ061 java.net.UnknownHostException: www.weather.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:360)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.naming.BIpHost.openSocket(BIpHost.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getAdvisories(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) ERROR [19:32:29 06-Sep-11 EDT][http.proxy] Error resolving www.nws.noaa.gov java.net.UnknownHostException: www.nws.noaa.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:369)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.net.BHttpProxyService.get(BHttpProxyService.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) WARNING [19:32:30 06-Sep-11 EDT][weather] Updating current conditions failed for WeatherReport java.net.UnknownHostException: www.nws.noaa.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:360)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.naming.BIpHost.openSocket(BIpHost.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) Environment Niagara G3, Workbench all versions Cause No address entered for DNS or IP Address incorrectly entered. Resolution Configuration for the DNS is located under the ENC/ENS Platform.   Open the Platform Select TCP/IP Enter the IP address for the DNS in the DNSv4 Servers slot and save changes. The network administrator should be able to provide the correct DNS address.

Issue I/A Series R2 Enterprise Server station is unable to connect to the SQL database The following errors are seen in the Enterprise Server station's Standard Output: ERROR: Could not open database connection [/SQL2005/services/DatabaseService] java.sql.SQLException: Charset 0x0904D00031/Cp850 is not supported by the JVM. "The program can't start because MSVCR71.dll is missing from your computer. Try re-installing the program to fix this problem." Environment I/A Series r2.301.529 SQL Server 2005 Java Runtime Environment 1.6 Cause JRE 1.4.1 which I/A Series R2 uses does not know how to support the CP850 character set. Even though the computer has been installed with JRE 1.6, I/A Series R2 is still using JRE 1.4.1. Resolution To enable I/A Series R2 to use JRE 1.6, follow these steps: Download and install JRE 1.6 if it has not been already installed. The latest version can be found here http://www.java.com/en/download/manual.jsp. Go to Windows Services and stop the Niagara service. In Windows Explorer, go to \niagara\r2.301.529\nre\ and rename the 'jre' folder to 'jreold'. In Windows Explorer, go to C:\Program Files\Java (this is typically the path of the Java install). Copy the 'jre6' folder including its contents and paste it to the \niagara\r2.301.529\nre\ directory. Rename the 'jre6' folder to 'jre'. In Windows Explorer, go to \niagara\r2.301.529\nre\lib and open the 'nre.properties' file using a text editor program (eg. Notepad). Comment out the 'java.options...' parameter. Add the parameter shown below, save and close the file. Start the Niagara service and run the station. Check in the Standard Output window to see if the error has been cleared and that the DatabaseService has successfully connected to the SQL database. ######################################################## # # File:  nre.properties # #    NRE properties # # Revision History #   21 Aug 03   Brian     Original version. # ######################################################## # Virtual machine to use: jview|hotspot vm=hotspot #vm=jview                       # List of Java options to pass thru to the VM (hotspot only) # Used with original install 1.4.1 # java.options=-Xmx1024MB # List of Java options to pass thru to the VM (hotspot only) # USed with 1.6 java -Xmx1G   Notes: This solution can be applied to a similar error but with a different charset encoding error other CP850. You may encounter the following error when you try to run WorkPlace Pro after performing this fix. "The program can't start because MSVCR71.dll is missing from your computer. Try reinstalling the program to fix this problem." To resolve this, go to \niagara\r2.301.529\nre\jre\bin and locate the file MSVCR71.dll. Copy this file to the C:\WINDOWS\system32 directory.

Issue As part of installing InVue, what are the licensing requirements? Environment InVue 1.1 Cause InVue software re-installation on new server hardware. Resolution Two license files are required.  One license is for the Wonderware core and one license is for the add-on programs (like TreeTech, interface drivers, hrdbdde driver, etc...). The Wonderware license file was typically provided on a 3.5" floppy diskette.  The filename is wwsuite.lic.  It is installed in the following path:  C:\Program Files\FactorySuite\Common\License Install the file by using Wonderware's License Utility (available via Start > Programs > Wonderware FactorySuite > Common > License Utility). The license file for the add-on programs is provided during the software installation process.  Unlock codes must be provided to allow the programs to run.  A 30-day temporary license is provided during installation. The filename is WIBSSuite.lic. It is installed in the following path:  C:\Program Files\Siebe\WIBs\Core When the unlock codes are provided, use the Purchase WIB Software shortcut (placed on the desktop during software installation) to enter them.

Issue Customer is installing a new server computer and the host operating system is Windows 7 64-bit.  Will the current version of OPRIF (Operator Interface) version 11.6 operate properly if installed? Environment DMS OPRIF 11.6 or PSOPRIF 11.6 or Operator Interface 11.6 Cause Upgrade of computer hardware and unavailability of Windows XP Resolution OPRIF 11.6 will only operate on a Windows 7 64-bit operating system with XP mode installed. For a compatibility chart, see Product Announcement PA-00163.

Issue BACnet controller objects that have not been overridden are displayed on I/A Series R2 graphic screens in the purple color as if they were overridden. Environment I/A Series R2 (Niagara) Graphic screens displaying values representing physical BACnet controller inputs. Cause Purple BACnet values (I/A Series R2 graphic override color) are internal BACnet points that can not be modified (display only).  This behavior is normal and began to appear in MNB controller firmware versions 1.2 and higher.  Per the BACnet specification, read-only type points must be set to indicate an override condition.  The root cause is a design change required by the BACnet specification to bring the controllers into compliance for BTL certification.  The ASHRAE BACnet Specification 135-2004 specifies that the "read-only" type objects (e.g. Analog Value, Binary Value, etc.) OVERRIDDEN flag is: Logical TRUE (1) if the point has been overridden by some mechanism local to the BACnet device.  In this context "overridden" is taken to mean that the Present Value property is not changeable through BACnet services. In this case, the override is meant to indicate to Niagara that the point is locally overridden (by the controller) and cannot be changed by the Niagara BACnet service (or user). Resolution There are several approaches that can be used to display these objects without the background showing the purple color. One approach is to use a native Niagara AI object to buffer the value where the override condition is not transferred.  In addition, if the BACnet points and Analog Input objects reside in a poll-on-demand container, the BACnet points will not be polled unless a gx type object is added and directly attached to the BACnet point.  The graphic page will have a gx type object linked to the Analog Input object (displaying the value without the override) and another gx type object (invisible) linked to the BACnet point to start the point polling. A second approach is to configure the GxText object so that the object property "statusColorEnabled" is false. 

Issue Installing Echelon Network Interfaces on Windows 7 Operating Systems Environment Microsoft Operating Systems: Microsoft Windows 7 (64-bit and 32-bit) Windows Server 2008 R2 (64-bit), Windows Vista (32-bit) Windows XP (32-bit) Windows Server 2003 (32-bit) Echelon Network Interfaces: i.LON 10 Ethernet Adapter i.LON 100 Internet Server i.LON 600 Internet Server PCLTA-21 PCI Network Interfaces PCLTA-20 PCI Network Interfaces PCLTA-10 ISA LonTalk Adapter PCC-10 PC Card Network Interface SLTA-10 Serial Network Interface (requires separate driver) SmartServer and SmartServer 2.0 U10 USB Network Interfaces U20 USB Network Interfaces Cause Installing Echelon Network Interfaces on computers with newer Windows Operating Systems. OpenLDV 4.0 Resolution Install and use Echelon OpenLDV network interface driver version 4.0 and above. You can download OpenLDV 4.0 from the Echelon website here Echelon Network Interface(s) manuals can be found here. Echelon has released OpenLDV 5.0. It can be downloaded from here. 

Issue The lib-2.301.532.v1.jar file is missing objects that were present in previous builds.  Here is list of those objects: lib\programObjects\hvac\RemainingOverrideTime.sns lib\programObjects\hvac\StartupInhibitor.sns lib\programObjects\hvac\TriStateOutput.sns lib\programObjects\lon\BooleansToMfgNvTypeBits.sns lib\programObjects\lon\BooleansToSnvtStateTypeBits.sns lib\programObjects\lon\FloatToSnvtHvacModeEnum.sns lib\programObjects\lon\MfgNvTypeBitsToBooleans.sns lib\programObjects\lon\SnvtLevDiscEnumTransposition.sns lib\programObjects\lon\SnvtStateTypeBitsToBooleans.sns lib\programObjects\lonHoneywell\XL15AnvoFTStatusDemux.sns lib\programObjects\lonHoneywell\XL15AnvoLogicOutputDemux.sns lib\programObjects\lonHoneywell\XL15AnvoStStpStatusDemux.sns lib\programObjects\miscellaneous\MinMaxAvg.sns lib\programObjects\miscellaneous\NumberRamp.sns lib\programObjects\miscellaneous\PulseGenerator.sns lib\programObjects\miscellaneous\WatchdogTimer.sns lib\programObjects\muxDemux\DateTimeDiscreteComponents.sns lib\programObjects\muxDemux\ExtractTextSegment.sns lib\programObjects\muxDemux\ParseString.sns Environment Niagara R2 version 532 Cause A compiling error with the jar file. Resolution This error has been corrected in a new 'lib' jar file: lib-2.301.533.v1.zip.

Issue Getting the error message “Can not access controller” when downloading to an MNB-300 controller with WorkPlace Tech 5.7.7. Environment WorkPlace Tech 5.7.7 Cause Corrupt database Resolution   Use backup copy of application or create a new application.

Issue Unable to successfully use Gmail SMTP server to send out alarms via email from I/A Series G3.  Various errors can be seen in the console output. Some of the errors are indicated below but they may not be limited to these. Error: BOutgoingAccount could not dequeue persistent email: 550 The address is not valid java.lang.Exception: Valid CryptoService not found Environment Enterprise Network Server / Enterprise Network Controller I/A Series G3 version 3.5 and above I/A Series G3 maintenance builds version 3.4.55 and above Cause Improper configuration of the EmailService's OutgoingAccount and missing CryptoService in the station. Resolution Procedure and properties settings required when using the Gmail SMTP Server: Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC. Add the OutgoingAccount to the EmailService. In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings. Hostname: smtp.gmail.com Port: 465 (this is the TCP port SMTP over SSL uses) Account: example@gmail.com Password: Your Gmail account password Enabled: true Use Ssl: true (Gmail requires SSL) Transport: SMTP Use Authentication: true (Gmail requires authentication when sending out emails) You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email. If you are still having an issue with authentication, it may need to allow less secure apps to access your Gmail account. Refer to https://support.google.com/accounts/answer/6010255?hl=en for details.  Notes: CryptoService enables the SSL feature in the G3 station. The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 (crypto 3.4.64 / crypto 3.5.34) from The Exchange Download Center. Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license. feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"

Issue Getting “Lost Sync with system clock - resetting control engine” warnings messages in R2 Enterprise Server? Environment Niagara R2, Enterprise Server, UNC-520, UNC-410 Cause The cause could be any one or a combination of several things listed in the resolution. Resolution The following settings should be verified in both the UNC and Enterprise Server. The following settings are for the Enterprise Server (ES): serverEnabled = true if syncing with UNC. clientEnabled = true if the ES is getting its time from an internet time sync server or site’s server. If not, clientEnabled= false. clientResetTolerance: the default is 30 sec with is too tight. Set it for a minute or more. (Remember to enter value as seconds, not minutes.) timeProtocolServer*: If clientEnabled = True, then all three slots should contain an address of a time sync server. If only one server is being used, then all three slots should be filled in with the one time sync server (same server). No slot should be left blank.   UNCs TimeSyncService settings: serverEnabled = false clientEnabled = true clientResetTolerance: the same would apply as the server timeProtocolServer*: the same would apply as the server reboot the UNC after any changes.

Issue I/A Series R2 (Niagara) Enterprise Server displays "ERROR: Cannot subscribe: Invalid node : (specifies node)". Environment I/A Series R2 (Niagara) Enterprise Server, all versions. Cause These errors are related to invalid subscriptions (swids) typically caused by changing the parent container or object name on the UNC without deleting and recreating the associated external link. The swid name changed but the external link is still referencing the invalid swid.   Resolution Review the links specified in the error message(s) and correct them.

Issue If a database is downloaded to the controller after the box has been balance will it lose the balance data? Product Line TAC IA Series Environment All versions of MNB VAV controllers MNB-V1 MNB-V2 Cause In MNB VAV controllers the flow balance data is preserved in a different area of EEPROM than the application data. Resolution Balance data in an MNB VAV controller is not affected by the downloading of its database.

Issue Cannot ping the MNB-1000 to test network connectivity.  Looking for an alternative method of network diagnostics, possibly by use of the second Ethernet port on the MNB-1000. Environment MNB-1000 (firmware 1.510 and later) Also can be used, but not required, with earlier firmware versions. Cause All Ethernet functions except for BACnet UDP messaging and router management functions has been disabled in the MNB-1000 firmware versions 1.510 and newer.  This prevents the use of Ethernet ICMP messaging (PING command, etc.) for diagnosing the Ethernet connection to the MNB-1000 controller. Resolution A computer can be plugged into the second (lower) Ethernet port on the MNB-1000 to allow network troubleshooting, device configuration and programming.  Plugging in a computer into the second port and assigning it an address on the same subnet as the MNB-1000, you can then ping other devices on the network to verify outgoing network connectivity.  Since the ICMP messaging has been disabled in the MNB-1000 itself, you can also ping the computer on port 2 from other computers on the Ethernet network to verify incoming connectivity.  NOTE: When performing troubleshooting in this manner, you need to remember that the MNB-1000 itself still will not respond to PING commands but will pass the ping commands and all other Ethernet or IP messages through to the second ethernet port. 

Issue Does Niagara G3 provide a way of importing existing ENC PxViews into an ENS?  Environment Niagara G3 version 3.5 or later Cause Importing existing ENC PxViews into an ENS is a time saving process. Resolution Niagara G3 does provide a way of importing existing ENC PxViews into the ENS with the use of exportTags, specifically PxViewTags. Open the exportTags in the Palette Drag and drop the SupervisorExportTagNetworkExt to the NiagaraNetwork of the ENS (server). Drag and drop the SubordinateExportTagNetworkExt to the NiagaraNetwork of the ENC. Enable the joinProfile in ENC: Expand the NiagaraNetwork of the ENC  Expand the ENS’ station. Double-click on the Join Profile and select Enable - Save. Setup the ENC’s PxViex File Structure: Expand Files Folder in the ENC and then expand joinProfile Expand ENS_profile.bog file and then expand niagaraStation Double-click the Points folder (The ENC’s PxViews will be setup here) Right-click in the ViewPane and select New Folder You may want to give the folder the same name as the PxView being exported The Folder structure should be the same PxViex folder structure as in the ENC’s PxView structure. Add folder for each PxView to be exported to the ENS Right-click on ENS_profile.bog and Save. Placing PxViewTags in PxViews PxViewTags are placed in each PxView being exported to the ENS. From the Palette, open exportTags and expand the Extensions folder Drag and drop a PxViewTag into the ENC’s PxView folder to be exported Configure each PxView’s Property sheet to point to the folders you created under Points in the ENS_profile.bog file. Double-click on the PxViewTag to set its properties For Supervisor Station, select ENS from the drop-down menu. - Save For Station Slot Path, click on the folder to display the “Select Parent Target” window. Expand NiagaraStation and then expand Points.  Select the corresponding PxView Folder and click OK For Px View, select the PxView to be displayed Click Save to save changes. Repeat steps for each PxView being exported to the ENS Do a Join to export PxView to ENS Once the above is setup a join can be performed.  A join can be accomplished in two ways. Join #1 Expand the NiagaraNetwork of the ENC Right-click on SubordinateExportTagNetworkExt, select Actions and then Join Join #2 Expand the NiagaraNetwork of the ENC and expand the ENS station Right-click on Join Profile, select Actions and then Join If everything was configured correctly, messages stating that both the Supervisor and Subordinate joins were successful will be displayed. If all goes well, then the ENC’s PxViews should appear in the Point folder of ENC under the ENS’ NiagaraNetwork. Notes: There were no provisions for importing the nav file during development of the exportTags. The file structure will also change once the ENC station.bog file is loaded on the Supervisor. For more detailed information on PxViewTags reference the NiagaraAX Export Tags Technical Document. This document is located in docs folder of the Niagara build root directory.

Issue SMS messages for alarms stop being sent after functioning for a period of time. The messages are stuck in the queue which can be seen in the SmsService's 'Queue Size' property. Messages in the queue are sent when the GSM modem is reset (power cycle). Problem will reoccur again after a period of operation. Environment I/A Series G3 Enterprise Network Server Cause The GSM modem appears not to be able to handle the messages being sent from the I/A Series G3 SmsService. Resolution In the SmsService properties, increase the 'Inter Message Delay' time. In this particular case, the delay has been increased to 1 second. The 'Inter Message Delay' is defined as: The delay between each command send to the GSM modem. By default this is set to zero. However, some older GSM modems may require this to be increased if there are problems with communication.

Issue ENC is licensed for ASD but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacasd" when attempting to access the ASD Network property sheet. Environment I/A Series G3, ENC-520 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses Tridium.license (Tridium 3.6 - never expires) TAC_LLC.license (TAC_LLC 3.6 - never expires) Certificates Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   Tridium.license (Tridium 3.6 - never expires)   TAC_LLC.license (TAC_LLC 3.6 - never expires) Certificates   Tridium.certificate (Tridium - never expires)  TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue. If you have previously installed the TAC_LLC.certificate in any other version of the G3 software, you can import that certificate into the version you are currently running. Open Workbench and connect to the subject ENC. Open the Platform then select License Manager. In the License Manager, select [Import] under the certificate section of the window. Browse to the "certificates" folder under any other G3 installation folder and locate the TAC_LLC.certificate file.  If the file is not found, check the "certificates" folder of another G3 folder.  Click on the TAC_LLC.certificate file name then click [OK]. The certificate will automatically be copied and installed.   If public ethernet connectivity is available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center. Use Workbench to import the downloaded file.

Issue The message "Could not invoke the command "New"" is displayed when attempting to right-click in the Drivers View Pane and add a BACnetNetwork. Also, the message "Cannot perform the drop" is displayed when attempting to drag and drop a BACnetNetwork driver from the Palette into the Drivers folder. Environment Niagara G3, Enterprise Network Sever, ENC-520, ENC-410 Cause NA Resolution Uninstall WorkBench Delete remaining folders and files from Niagara build directory Reinstall WorkBench

Issue The following error messages are displayed in the Application Director output windows when attempting to add additional histories to a existing SQL database. javax.baja.sys.BajaRuntimeException at javax.baja.rdb.history.BRdbmsHistoryExport.insertMetaRecord(BRdbmsHistoryExport.java:679) at javax.baja.rdb.history.BRdbmsHistoryExport.exportRecords(BRdbmsHistoryExport.java:279) at javax.baja.rdb.history.BRdbmsHistoryExport.doExecute(BRdbmsHistoryExport.java:202) at auto.com_tridium_rdb_sqlserver_history_BSqlServerHistoryExport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1232) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1050) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.ThreadPoolWorker$WorkerThread.run(ThreadPoolWorker.java:266) Caused by: java.sql.BatchUpdateException: Invalid column name 'INTERVAL_'. at net.sourceforge.jtds.jdbc.JtdsStatement.executeBatch(JtdsStatement.java:944) at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297) at javax.baja.rdb.history.BRdbmsHistoryExport.insertMetaRecord(BRdbmsHistoryExport.java:673) ... 8 more Environment G3 Niagara, 3.4 and later, SQL Cause The term INTERVAL was a keyword in some SQL dialects, so the column name was changed from INTERVAL to INTERVAL_ in the database schema. The database schema changed between 3.3 and 3.4. Resolution The following changes needed to be made to the SQL database. Altered the existing HISTORY_CONFIG table in the SQL database to change the column to INTERVAL_. Altered the HISTORY_CONFIG table, added a column called SYSTEMTAGS, set up as VARCHAR(500). Changed SOURCE column length to VARCHAR(500) in the HISTORY_CONFIG table