Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Email notifications fail to send from the I/A Series R2 Enterprise Server. The error message displayed is: datax:nohandler for: notification Product Line TAC IA Series Environment I/A Series R2 Enterprise Server Cause The NotificationService in the Enterprise Server station has its archiveMode property set to archive_disabled . This is the default configuration and prevents notifications from being processed. Resolution Update the Enterprise Server station configuration: Open the NotificationService settings in the Enterprise Server station. Change the archiveMode property from archive_disabled to archive_local . Save and restart the service if required. This change enables notifications to process correctly.

Issue When attempting to open a Niagara R2 Enterprise Server station, the following error occurs: Cannot open web server socket. [ServerLoop.run] java.net.BindException: Address already in use: JVM_Bind Product Line TAC IA Series Environment Niagara R2 Enterprise Server all version Cause Windows IIS uses Port 80 by default, which conflicts with the Niagara R2 Enterprise Server station database that also uses Port 80. This prevents the Enterprise Server from binding to the port. Resolution Disable IIS if not required: Open Control Panel → Add/Remove Programs → Add/Remove Windows Components. Deselect Internet Information Services (IIS) and complete the removal. On Windows 7, set World Wide Publishing Service to Manual in Services to prevent auto-start. If IIS is required, change the Niagara R2 Enterprise Server port: Open WorkPlace Pro Admin Tool and stop the Enterprise Server. Open the Enterprise Server station offline. Right-click the station → Properties → Config tab. Change httpPort to a new port (e.g., 8080) and click Apply. Save and restart the Enterprise Server. Update all references (address tables, browser URLs) to include the new port (e.g., http://192.168.1.142:8080 ).

Issue An end customer wants to enable SSL (Secure Sockets Layer) on their Niagara R2 control system for secure communication. They need to know if SSL is supported. Product Line TAC IA Series Environment Niagara R2 Cause Niagara R2 was developed before SSL/TLS became a standard requirement for secure communication. The platform does not include native SSL support, and its architecture cannot accommodate SSL without significant redesign. Resolution SSL is not supported in the Niagara R2 environment. To meet security requirements, consider the following alternatives: Use a VPN tunnel to secure communication between Niagara R2 and external systems. Implement network-level security measures such as firewalls and IP filtering. Plan for migration to a newer platform (e.g., Niagara AX or N4) that supports modern encryption standards.

Issue A Niagara R2 station running on a laptop with LON integration does not communicate with MNL controllers connected through an Echelon USB-LON adapter. The station appears to be running in Admin Tool, but no controller communication occurs. Product Line TAC IA Series Environment Niagara R2 Echelon USB-LON adapter Cause WorkPlace Tech and Niagara R2 are both configured to use the same USB-LON adapter for LON communications. This creates a resource conflict, typically on the LON1 interface. Resolution Close WorkPlace Tech or reconfigure its communication settings so that LON1 is not used. Restart the Niagara R2 station. Verify successful adapter initialization by checking the standard output window for: LON Card Resetting!! LON Card reset complete!! Opened lonworks LON1 >>> Lon Driver opened!

Issue Can JAR files from Niagara R2 version 532 be used with a UNC running version 330? Product Line TAC IA Series Environment Niagara (all versions) Cause Attempting to fix a known issue by upgrading to a newer JAR file while maintaining the currently installed Niagara version. Resolution JAR files must match the installed Niagara build version. If the UNC is running version 330, only JAR files ending in 3xx should be used. If the UNC is running version 532, only JAR files ending in 5xx should be used. Mixing JAR files from different Niagara builds is not recommended and may cause instability or integration issues.

Issue Users want to know if the BACnet object_name property for an I/A Series R2 or G3 station can be modified. Product Line TAC IA Series Environment I/A Series R2 UNC-410 I/A Series R2 UNC-520 I/A Series G3 ENC-410 I/A Series G3 ENC-520 Cause The BACnet object_name is automatically generated by the system using: The station name The assigned BACnet device instance number For example: Station name: BldgA Device instance: 500 Resulting object_name: BldgA_500 This behavior is hardcoded and cannot be overridden. Resolution The BACnet object_name cannot be changed by the user. To influence the object_name, you must rename the station or change the BACnet device instance number. There is no direct property or setting to manually edit the object_name.

Issue Unable to log into LocalHost via the I/A Series R2 Admin Tool despite trying all known usernames and passwords associated with the PC. Product Line TAC IA Series Environment I/A Series R2 UNC I/A Series WorkPlace Pro / Admin Tool Cause The I/A Series R2 Admin Tool requires a local Administrator account for authentication. Domain-based accounts cannot be used for login. Resolution Confirm you are logged in as a user with Administrator privileges. If necessary, create a new local user and assign it to the Administrators group: Right-click My Computer → Manage. Expand Local Users and Groups → Select Users. Right-click in the right pane → New User. Enter: Username: IAAdmin Password: P@ssword Configure options: Uncheck User must change password at next login. Check User cannot change password and Password never expires. Click Create, then Close. Add the new user to the Administrators group: Right-click IAAdmin → Properties → Member Of tab → Add → Enter Administrators → OK. Close Computer Management. Log into the Admin Tool using: Username: IAAdmin Password: P@ssword If domain policy prevents creating local accounts, contact your IT department for assistance.

Issue Does the database file for a ProView display vary in size based on the amount of programming done to it with Niagara R2? Product Line TAC IA Series Environment Niagara R2 all versions ProView display Cause A backup of an empty ProView display and a backup of a ProView display programmed with 30+ screens and dozens of bindings produced the same file size: 49 kB. This indicates that the backup file does not store detailed programming data in a way that affects file size. Resolution No, the database file size remains constant regardless of programming complexity. Any ProView display backup created using the Niagara R2 wizard will be 49 kB, whether the display is empty or fully programmed.

Issue When adding a BACnet Binary Output object for a Functional Devices RIBTW2401B-BC RIB relay module in I/A Series R2, the device goes offline (status shows down). The output window displays: ERROR: Unable to convert class tridium.foundation.dataspecies.DsEnum from ASN type 9 tridiumx.bacnet.asn.ASNException E_BACNET_ASN_INVALID_TAG {tagNumber 9 current tag 0} BACnetDevice: RIB01 is now down Product Line TAC IA Series Environment I/A Series R2 BACnet Functional Devices RIBTW2401B-BC Cause The RIBTW2401B-BC device has an issue processing device status polling when priorityArray points are queried. It responds incorrectly to the UNC’s status message request due to a problem in its BACnet stack. Resolution Disable the device ping mechanism in the I/A Series R2 UNC’s BACnet Service → Device Status tab. Reboot the UNC after making the change. Ensure you backup the station when prompted to save the configuration changes.

Issue In Niagara R2 Workplace Pro, users need to know the default size of a Container’s Workspace and the maximum allowable settings to properly view large shadow objects. Product Line TAC IA Series Environment Niagara R2 Cause Large shadow objects cannot be fully displayed in the Workspace because the default width and height settings are too small. Resolution Default Workspace Size: Width: 800 Height: 550 Maximum Workspace Size: Width: 1500 Height: 1500 To modify these values: Right-click the Container. Go to Properties → Visual tab. Adjust width and height as needed within the maximum limits.

Issue Third-party systems cannot read SNMP traps from I/A Series stations using the provided MIB file. Product Line TAC IA Series Environment I/A Series R2 SNMP integration I/A Series G3 SNMP integration Cause The issue occurs because different versions of I/A Series use different MIB files. R2 requires TridiumR2-MIB (introduced in version 2.301.528 and above). G3 uses TridiumR3-MIB.my for versions 3.4 and earlier. From G3 version 3.5 and above, MIB files can be generated locally in Workbench. Resolution Verify the I/A Series version: R2 (≥ 2.301.528) → Use TridiumR2-MIB. G3 (≤ 3.4) → Use TridiumR3-MIB.my. For G3 version 3.5 and above: Use Workbench’s right-click menu on the local SNMP device to generate a MIB file. Refer to Niagara AX 3.5 SNMP Driver Guide, pages 3-17 to 3-21 for details. To view the MIB file in Workbench: Navigate to File > Open > Open Ord or press Ctrl + L. Enter: local:|module://snmp/tridiumMib/TridiumR3-MIB.my Ensure the correct MIB file is provided to the third-party system.

Issue A Niagara R2 UNC station fails to start and displays the following error in the Standard Output Window: FATAL: Cannot boot station from sns java.lang.IllegalStateException: NodeProperty.readExternal: tridium.foundation.TRuntimeException E_INVALID_DSTABLE_CODE {165.16} Product Line TAC IA Series Environment Niagara R2 UNC-410 Niagara R2 UNC-520 Cause The UNC is missing a required Lon module (jar file). In this case, the lonTrane module was not installed, causing the station to fail during boot. Resolution Review the Standard Output Window error messages for references to missing jar files. Identify which Lon devices are configured in the station. Install all required Lon modules (jar files) on the UNC. Example: If Trane Lon devices are present, ensure the lonTrane module is installed. Restart the UNC station after installing the missing modules.

Issue When converting a Niagara R2 server station from XML to DB, the process fails with the following error: Could not create node "tridium.apps.ProgramNode". tridium.foundation.IllegalChildException E_ILLEGAL_CHILD_DUP_NAME Product Line TAC IA Series Environment Niagara R2 Cause The conversion fails because two Program objects in the XML file have duplicate names, which violates the naming rules during DB creation. Resolution Open the XML file using an editor such as Notepad++. Navigate to the line and character indicated in the error message (e.g., line #865566, character #98 ). Identify the Program object with the duplicate name. Rename the object by adding an extra character (e.g., append 1 or a to the name). Save the XML file and close the editor. Re-run the XML-to-DB conversion process.

Issue After the system clock was inadvertently set ahead and later corrected, the daily archive and backup processes in an I/A Series R2 station stopped running. The Last Daily Archive and Last Backup Time entries show future dates. Product Line TAC IA Series Environment I/A Series R2 ES and UNC stations Cause The computer system clock was incorrectly set ahead for several days. After correcting the clock, the station retained future timestamps for archive and backup operations, preventing scheduled tasks from executing. Resolution There is no direct method to reset these timestamps in the station UI. However, you can edit the station database XML file: Save Runtime Database In Admin Tool, log into LocalHost, select the running station, and use DB Admin → Save Runtime Db. Stop the Station After saving, stop the running station. Convert DB to XML In DB Admin, select the station and perform Convert Local from DB to XML. Edit XML File Locate the config.xml file in the station’s backup folder. Search and update the following tags to a past date: <LastBackupTime> <LastDailyArchive> <LastArchiveTimestamp> (all occurrences) Save the file. Convert XML Back to DB Rename the old config.db file for backup. Use DB Admin to convert the edited XML back to DB. Verify Time Settings Ensure the computer time is correct and time sync service uses a reliable NTP server. Restart the station and confirm archive/backup functions resume.

Issue An existing Niagara R2 MicroSmart integration has been operational for several years. Recent changes required reprogramming of some MicroSmart controllers (points added, deleted, or renamed). How should these changes be uploaded to the existing station in the UNC? Product Line TAC IA Series Environment Niagara R2 MicroSmart integrations (all versions) Cause Changes were made to building HVAC equipment, requiring updates to point configurations in MicroSmart controllers. Resolution The MicroSmart driver references the point list stored in the PointListManager of the IbsMsService. To reflect changes in the station: Any modification to point type, order, ID, engineering unit, or status ID requires uploading a new point list. Review the MicroSmart Driver Engineering Guide (F-27327), Chapter 3, Sections 3.3 and 3.3.1 for detailed instructions on: Updating unit displays Updating GX page “displays”

Issue Emails are sent when an alarm is acknowledged in Niagara R2, even though this behavior may not be desired. Product Line TAC IA Series Environment Niagara R2 Cause The MailRecipient object has the routeAcks property set to True, which routes acknowledgment events to email recipients. Resolution To prevent emails from being sent when alarms are acknowledged: Open MailRecipient Configuration Navigate to the MailRecipient object in the Niagara R2 station. Modify routeAcks Property Go to the Config tab. Set the routeAcks property to False. Apply Changes Click Apply to save the configuration. After this change, acknowledgment events will no longer trigger email notifications.

Issue How does a digital command (scheduled or manual override) from a Niagara R2 station get transferred to control a supply fan wired to a Microzone II controller? Product Line TAC IA Series Environment Niagara R2 ASD driver Microzone II Cause Limited familiarity with the Network 8000 product line and its integration with Niagara R2. Resolution Link Niagara Output to Microzone Input Connect the output of the native Niagara object to one of the digital inputs of the MZ2EmsDi object. Verify Microzone EMS Control Ensure the Microzone’s emsControlDefault property is set to On. Check this under Properties > Config for the Microzone’s Shadow object. Confirm EMS Block Status Using PSI serial tunneling, verify that the EMS block’s EMS attribute shows ON. ON indicates the Microzone is under UNC control; OFF means standalone operation. Link to Fan Control The digital command from the UNC station will appear at the corresponding DV output of the EMS block in the Microzone. Link this DV output to the block responsible for fan control.

Issue Users want to display a custom message when an alarm returns to normal in I/A Series R2, but the system only shows the alarm text field. Product Line TAC IA Series Environment I/A Series R2 alarms Cause Alarmable objects in I/A Series R2 do not include a field for “back to normal” text. Only an alarm text field is available. Resolution There is no option to configure custom text for when an alarm returns to normal. When the alarm clears, the alarm message text field will be empty.

Issue After replacing the Niagara R2 Enterprise Server hardware, alarms no longer print because the dot-matrix printer was connected via a USB adapter instead of the original parallel port. Product Line TAC IA Series Environment Niagara R2 Enterprise Server Dot-matrix printer used for alarm printing Cause Niagara R2 does not support USB-connected printers. The original hardware provided a parallel or RS-232 port, which is required for printer communication. Resolution Use a printer connection via: RS-232 serial port, or Standard 25-pin parallel port USB printer connections are not supported by Niagara R2.

Issue Microsmart controllers do not respond to Niagara R2 schedules after a brief power outage. The UNC appears online, but Microsmart shadow objects stop updating. Product Line TAC IA Series Environment Niagara R2 (all versions) Microsmart controllers (all versions) Cause When building power fails for less than 60 seconds: The UNC performs a graceful shutdown using its backup battery but never fully powers down. Microsmart controllers reboot and come back online. The UNC assumes controllers are still online, but the link between Microsmart shadow objects and physical points is lost during the outage and does not automatically recover. Resolution Reboot the UNC to re-establish communication between Microsmart shadow objects and the controllers. Verify all schedule links after reboot to ensure proper operation.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Unable to Send Email from I/A Series R2 Enterprise Server – Error “datax:nohandler for: notification”

Niagara R2 Error: Cannot Open Web Server Socket (Port Conflict)

Niagara R2 SSL Support – Is Secure Sockets Layer Available?

Niagara R2 Station on Laptop Fails to Communicate with LON Controllers via USB Adapter

Compatibility of Niagara R2 JAR Files Between Different Versions

Can BACnet Object_Name Be Changed in I/A Series R2 or G3?

Cannot Log into LocalHost Using I/A Series R2 Admin Tool

Niagara R2 ProView Display – Database File Size Consistency

I/A Series R2 BACnet Binary Output Causes Functional Devices RIBTW2401B-BC to Drop Offline

Niagara R2 Workplace Pro – Default and Maximum Container Workspace Size

I/A Series R2 and G3 SNMP Integration – Correct MIB File Usage

Niagara R2 UNC Station Fails to Boot – Missing Lon Module

Niagara R2 XML-to-DB Conversion Fails Due to Duplicate Program Object Names

Resetting Last Daily Archive and Backup Time in I/A Series R2 Station

Niagara R2 MicroSmart Integration – Updating Station After Controller Reprogramming

Prevent Email Notifications When Alarm Is Acknowledged in Niagara R2

Niagara R2 Digital Command Integration with Microzone II

I/A Series R2: No Custom Text for “Alarm Back to Normal”

Niagara R2 Enterprise Server Does Not Support USB-Connected Dot-Matrix Printers

Microsmart Controllers Not Following Niagara R2 Schedule After Power Failure

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!