Building Automation Knowledge Base

Issue Some security software will report that there are vulnerabilities for SSL of Xenta Server. Some vulnerabilities look like: SSL Server allow anonymous authentication vulnerability SSL Server allow Cleartext communication vulnerability  Weak encryption model Environment Vista I/NET Cause This is how Xenta Server designed to work. Resolution There is a security enhancement for Xenta Server in Xenta 5.1.9. Update the firmware to Xenta 5.1.9 will fix these vulnerabilities. You can download Xenta 5.1.9 from Buildings Download Center.

Issue Xenta 913 is locked up randomly, and it needs reboot to make it return to work. When referring to the error log on the web page, the following errors show up: event power PowerFail 1 System is safely shutdown (Error#:49154) event power InitSYS 1 System start - power on (WARMSTART) (Error#:49156) Environment Xenta 913 BACnet Cause Possible cause is the baud rate for BACnet communication is too high that Xenta 913 can't deal with it properly. Resolution It is recommended to decrease baud rate for BACnet communication to 9600 or 19200 bps, and then Xenta 913 should work fine now.

Issue When installing SQL server 2008 or SQL 2008 R2 to manually an instance for I/NET, Vista or Continuum, sometimes an error "Invoke or BeginInvoke cannot be called on a control until the window handle has been created" will show up. Environment SQL 2008 / SQL 2008 R2 Vista I/NET Continuum SmartStruxure Cause This issue is happening because of a behavior change in .NET that is exposing an issue with SQL Setup User Interface (UI). Resolution Generally, if you just rerun the installer, it won't hit the issue again. If this can't help, just manually create a C:\temp folder and it will work fine.

Issue HID Biometric reader product obsolescence. Environment HID Desfire and Mifare Smart card and Fingerprint readers. As used on Continuum and I/Net Access Control. Cause HID have discontinued these readers. Resolution HID have discontinued production of their SmartTOUCH SB10 and SBK10 Desfire and Mifare fingerprint readers. Part numbers affected are: HID Ref: 800-8052, SE P/N 654 1903 000 - SB10 Desfire Fingerprint reader. HID Ref: 800-8057, SE P/N 654 1904 000 - SBK10 Desfire Fingerprint reader with keypad. HID Ref: 800-8050, SE P/N 654 1901 000 - SB10 Mifare Fingerprint reader. HID Ref: 800-8055, SE P/N 654 1902 000 - SBK10 Mifare Fingerprint reader with keypad.

Issue When clicking on the Right Click Menu for I/NET Converted TGML Graphic on remote SmartStruxure Workstation, nothing happens even though I/NET has already been installed on this computer and I/O server has been registered as service. Environment SmartStruxure I/NET Seven 2.44a through to 2.48 Remote Workstation Cause On a 32 bit OS and a 64 bit OS machine, the I/NET Converted TGML Graphic are different because I/NET default software installation path is different: 32 bit OS: C:\Program Files\INET Seven\ 64 bit OS: C:\Program Files (x86) \INET Seven\ Since the Right Click Menu calls the I/NET program, if the graphic is converted on 64 bit OS machine on the Server, it will not work on the Client machine with 32 bit OS. And vice versa. Resolution NOTE: This right click menu option will only function when the graphics page is located on an Enterprise Server where a copy of I/NET is installed on the local Workstation. This feature provides access to graphic functions run using the installed I/NET software so will not work when that software is not locally available. It is therefore not available when using WebStation or when viewing graphics located within a SmartX Server. From I/NET version 2.49, this right click menu option will be removed from this editor and NO LONGER be available. there are mixed versions of 32 bit OS and 64 bit OS between ES and Remote Workstation, the I/NET graphics need to be converted on 64 bit OS machine. And then follow the steps below: 1. Manually create C:\Program Files (x86)\INET Seven\ folder on 32 bit OS machine. 2. Uninstall I/NET and reinstall it under the folder created instead of default one. Then the Right Click Menu should work now.

Issue Integrated NPR Dial on a Xenta 527 (Web) failed to connect Environment I/Net Site with Integrated NPR Dial Cause There is a current issue with Xenta 527 (Web) and the Firmware load of 5.1.9-15 at the present time. This release will not support the Modem connection. This issue has been given to Engineering for Repair. Resolution The "Work Around" is to go back a Firmware release. For the time being, until the 5.1.9-15 is fixed, load 5.1.8-10 in the Xenta 527 (Web) and the Modem will work in this load.

Issue Using I/NET Audible Alarms with Remote Clients No audible alarms with Remote Client configuration Product Line TAC INET Environment I/NET Seven Software 2.42 and newer I/NET Remote Client or Remote Client with I/O Server Cause The functionality was changed with the following TrackRecord 5940 fix in I/NET 2.42: Alarms in a Remote Client do not get an audible alarm Only clients configured as "Remote Client w/IO" are capable of routing alarms/events to the server. The masking on clients configured as "Remote Client" will not cause alarms/events to be routed to the server. On these clients, you can use the masking to get audible alarms with no danger of getting duplicate alarms.   Resolution To receive and activate audible alarms on a Remote Client, set the Distribution Group and Masking of the alarm point within AMT.   Note: This setting is only the case for I/NET 2.42 and above.  If this is setting is made in earlier versions of I/NET, it will cause alarms / events / trends to be routed to the server and possibly can cause duplicate events / trends to be sent to the server.  The following information is noted in TCON300: "Limitations to TAC I/NET Seven on Remote Clients   Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features:   Network functions                 Automatic DPU restore                 Archiving                 Dial after edit   Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed." "Limitations to TAC I/NET Seven on Remote Clients" Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features: Network function Automatic DPU restore Archiving Dial after edit Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed."  

Issue Distributed Link Architecture DLA with StruxureWare Building Operation Environment Large TAC I/NET Seven site with StruxureWare Building Operation installed Cause Does Distributed Link Architecture (DLA) supported with StruxureWare Building Operation as the front end? Resolution TAC I/NET allows you to define a system-wide total of up to 100 links in order to connect controller LANs to the TAC I/NET system. In the traditional TAC I/NET system, if you use Xenta 527 Routers (NPRs) to connect remote controller LANs (i.e., sites) to TAC I/NET, each site consumes one unique link address. This limits the traditional TAC I/NET system to a maximum of 100 sites. The purpose for adding Distributed Link Architecture (DLA) capabilities to NPRs, and to the TAC I/NET IOServer, is to allow multiple NPRs to share the same link number. In a system that is configured to use DLA-enabled NPRs, up to 64 sites can share a single link address. The shared link is referred to as a distributed link. The use of distributed links allows the TAC I/NET system to support up to 6400 sites. Note: TAC I/NET’s system-wide limits of 6,400 controllers and 100 link addresses must be observed, regardless of whether or not DLA functions are enabled. For example, if your TAC I/NET system already contains 6400 controllers, implementing DLA will not allow you to expand the system with additional sites of controllers. TAC I/NET Seven DLA is supported with Building Operation

Issue Bindings on every I/NET point in a converted graphic show the Server 1 instead of the correct server name Environment StuxureWare Building Operation Workstation I/NET 2.42 or higher Cause The INET Interface path parameter set in the Export INET Graphics to TGML converter does not revert to default after each conversion.   If the parameter is set to: /Server 1/INET Interface All binds will use that path even if the Server is named 'Building 1' Resolution OPTION 1 - Reconvert Graphics Change the INET Interface path to reflect the correct location. The most common is: ~/INET Interface The '~' symbol points the remainder of the path to the Server that the user is logged into during the import. If the user is not logged into the correct server, this may cause errors. INET Interface is the default name of the I/Net Interface but can be changed. For a site where the I/NET interface is named 'INET' and the Server is name 'Enterprise Server' the INET interface path could be set to: /Enterprise Server/INET OR ~/INET Option 2 - Change Server Name If every path on the I/NET interface references the incorrect server name: Change the Server Name to match the bindings Verify that the bindings now function with the matching Server Name Change the Server Name back to the desired name. The bindings should follow the name change.

Issue Logging on to IPM from the web and the default password is not recognized. An error comes up saying Invalid user. Product Line EcoStruxure Building Operation, TAC INET Environment StruxureWare Building Operation, I/Net Cause The default password can be used on the I/Net side but it is not being recognized when logging in from the StruxureWare IPM. Resolution To resolve this issue, the following step needs to be followed: From the original installation folder, find and unzip the Sboscripts.zip from ‘\InetWeb\UpdateScript' folder. Follow the SQL patch delivery process of I/Net. Run 'Sboscripts.exe' on a DOS prompt. Enter the SQL Server Instance name and login credentials for the script to run If the SQL Serve Instance name is not known, open up DBCreate and it would be displayed on the editor, more than likely it would be 'SQLEXPRESS" or blank per the INetDB Configuration. Once the script is complete, launch StruxureWare and enter the default passwords again and it should allow you to successfully log into the program.

Issue Windows installer fails to install an application Environment Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows XP Windows 7 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 8 Windows 8.1 Windows Server 2012 editions Windows Server 2012 R2 Cause Errors with the Windows Operating system are preventing the installation from completing. Resolution Run the file at the link below on the affected PC:   https://support.microsoft.com/en-us/mats/program_install_and_uninstall

Issue Correct Boot Up sequence for I/NET Enterprise Server Level Integration to StruxureWare. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET to StruxureWare Enterprise Server Level Integration Cause Sites which are recovering from a power failure are are using Remote Client with I/O may have certain failures within the system. A site where I/NET works on the local PC but devices seem offline from the Enterprise server may have had the Enterprise Server Start before the I/Net I/O Server A site where I/NET points can be controlled from the ES, but messages are not received by either the ES or I/NET AMT may have had the SQL server start after the ES or I/NET IO Server started. Resolution Restart the SQL Server or Server PC Restart the I/NET I/O Server and ensure it is running as a service Restart the Enterprise Server In order to add the I/NET I/O Server as a dependency for the Enterprise Server use the command prompt line below. Be sure to change the 1.X to reflect the current version of SBO installed. Open the Command prompt Enter the command: sc config "Building Operation 1.X Enterprise Server" depend= inet7iosrv

Issue I/NET action messages are triggering audible alarms AMT is not functioning as expected for points that have action messages associated with them. Environment I/NET Cause As a best practice, I/Net action messages should be masked and grouped the same as the point which is triggering the message. When this is not done, AMT gets harder to manage. Resolution Edit the Resident I/O configuration of  the point which is triggering the event action. Note the Distribution group and Mask Edit the Event Action that is being triggered. Ensure that the Event Action has the same masking as the Resident I/O point.

Issue Moving a Converted I/NET graphic for the ES level integration of I/NET to the AS level of Integration to I/NET Environment StruxureWare TGML I/NET Cause As sites expand, controllers that are currently integrated to StruxureWare using the Enterprise server may be connected to the USB interface to the Automation Server.  It is possible for these relocated controllers to continue to use the same graphics. Resolution Recreate the exact folder location of the graphic on the AS. For Example, if the graphic is currently on the ES\INET Interface\INET Graphics folder, the user should create an INET Interface\INET Graphics Folder on the AS Copy the Graphic on the ES Paste the Graphic on the AS Clean up any bindings.  Any I/NET objects that were re-named after the initial conversion may need to be manually re-bound. Links between graphics may also need to be re-bound.

Issue Multiple issues caused by changing the link after discovering devices. Duplicate entries of MCU devices under a sub LAN interface Deleting duplicate MCUs causes MCU devices to be removed from I/NET Environment Automation Server integrated to I/NET Cause Changing the link address of the I/NET Interface should not be done after devices are discovered. If you must change the link address, do so before you have added devices to the I/NET interface. Resolution Option 1 -  Remove all controllers from the I/NET interface. Change the link to the correct setting Re-discover the devices Option 2 - Determine whether the AS or the I/NET controller has the correct information. (This will require I/NET software) If the AS is more correct, perform a download to the controller if the I/NET controller is more correct, perform an upload to the AS

Issue A building has come under new ownership and wants to have the license ownership changed Environment I/NET 2.4x Cause I/NET CD Keys are referenced by site and Company name. When a specific building comes under new ownership, they new owner may wish to change the software license to their name. Resolution For Sites using I/NET 2.31 or older: These sites must purchase an upgrade to the I/NET system and ask for a name change as part of the upgrade.   For Sites using a current License Key: Open I/NET and select Help>About Take a screen capture of this screen Email this screen capture as an attachment to expert.services@schneider-electric.com Please include any information you have about the owner name or address the site may be registered as. Note: Please note that you will be billed for this transaction.

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. Issue After upgrade of Building Operation and / or I/NET, I/NET alarms and events have stopped updating within WorkStation. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.4x Integration with Enterprise Server EcoStruxure Building Operation 1.8 and above Cause Within the I/NET Seven SQL database table [InetDb].[dbo].[Events].[EventId], the EventId has not incremented correctly, so there is a missing EventId (causes unknown). Because of this missing EventId Building Operation waits at this missing ID to appear before updating its own event.db database. Since this ID will never show, no events will ever be passed through to Building Operation and effectively stops any I/NET events appearing within Building Operation WorkStation This EventId is seen in a registry entry called NspAmtEventId under the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CSI - Control Systems International\I/Net 2000\Configurations Resolution Current workaround is to manually edit this registry key NspAmtEventId value to: A value above the highest [InetDb].[dbo].[Events].[EventId].value - if the past events are not required. OR Increment its value by 1 if all past values are required to be retained. i.e. If NspAmtEventId = 82237682 typically only needs to be changed to 82237683 to correct this issue. If not then you should check the [InetDb].[dbo].[Events].[EventId].value After editing this registry value the Enterprise Server service needs to be restarted, after which events will then start to be processed by Building Operation. It should be noted if you use option 2 above that there will be some time for all this data to be updated within Building Operation and there may be some bogus (old) alarms appear, which should be taken into consideration before implementing this resolution.

Issue How is a subnet defined? Environment Refer to "TCP/IP Network Administration" by Craig Hunt, O’Reilly & Associates, Inc. Cause Sectioning network communication by subnets. Resolution A subnet is defined by applying a bit mask (subnet mask) to the IP address. If a bit is on in the mask, that equivalent bit in the address is interpreted as a network bit. If a bit in the mask is off, the bit belongs to the host part of the address. The subnet is only known locally.